Sebastian Krzyszkowiak @dos@librem.one

@agowa338 That said, it's not like it's some kind of black magic only to be known by insiders either. If you play with microcontrollers, can write and debug a I2C driver, set up clocks, find your way in the device tree and hack your phone's kernel and/or u-boot on an existing port, you should already be able to do plenty of useful work on a brand new port just on your own.

@agowa338 My impression would be that knowing the fundamentals individually is just required for this kind of tasks. Sure, you could probably get away without it on some subset of devices that are similar enough to what's already supported, but otherwise you'll either end up outsourcing what's actually hard about it to people you'll be asking for help, or you won't really do much.

@agowa338 I really have no better idea than "observe what's missing and try to fill the gaps, then repeat". What needs to be done will be very different across devices, and you'll have to rely on having wide enough background knowledge to connect the dots.

Pretty much all existing ports, including Librem 5 and PinePhone, still have plenty of low hanging fruits to deal with. That's what you'd start with to get to know the stack. Also: browse the commits, especially those beyond your grasp *yet*.

@agowa338 But the answer is still: it depends. What's the existing software support for the SoC and peripherals? How similar is it to already supported ones? How does the boot process look like? What resources you have available to base your research on? This all varies greatly device-to-device and if there was a guide it would have been already done.

If I were to write a guide, it would be: start with small steps on existing ports, observe others working, and you'll get there eventually.

@agowa338 I don't think there can ever be an effective guide like this. The first step is always "get to know your particular hardware well", and that's what determines what and how will have to be done next.

@oaj @arek Tramwaje i pociągi, przyciągną dodatkowe grono odbiorców.

@pavel Still same thing. Even accidentally recorded on the stock kernel without my camera patches 😜

the guitars are so tiny next to these giants #shotonlibrem5

🎶🎸🎤🎵 #shotonlibrem5

@ati1 I'm using PureOS (Byzantium and Crimson). Pure Maps works and has always worked just fine with Phosh.

@arek Ale jak to dwa telefony??? 🤨

@ati1 Well, Pure Maps has guided me from a train station to my accommodation today with no troubles 😉

@ati1 It hasn't been true for years, but only short clips were feasible until recently. You can browse #shotonlibrem5, I've posted quite a few videos with sound over the years there 😜

@pavel I have a stash too 😄 But to be frank I don't really use it anymore; I haven't needed a backup for my Librem 5 for a good while now, I'm just used to carrying it around I guess.

@etam Yeah, these touch screens can age this way. The one on the photo had developed a similar issue, but interestingly it got better after a while. BTW. Touch input still works fine after whatever happened in my pocket today!

😟

#shotonlibrem5

@74 @pluszysta @marventh @T_Wezmyr Ale KDE 10 lat temu potrafiło w kontrast...