Sebastian Krzyszkowiak @dos@librem.one

@qcoolka Epiphany, ewentualnie Firefox gdy coś nie działa.

@qcoolka Firefox, bo wciąż nie ma innej.

@pecet Też nie umiałem, ale nie zraziło mnie to gdy potrzebowałem i już coś tam nawet umim.

@PabloveSky Odnoszę wrażenie, że ostatnimi czasy "komedią" określa się wszystko, co ma w sobie choć jedną scenę z potencjałem na podniesienie kącików ust.

@alaraajavamma @mrakmm Neither Stevia nor Squeekboard work on GNOME Shell - it doesn't implement the required interfaces.

@gryzor @bart @don_atoms @marcprux @fdroidorg Weird, somehow I've been successfully making and receiving phone calls with GNU/Linux on various devices for the last 17 years... 🤔

@zak There's no such requirement. What you probably mean is that plymouth requires a keyboard, but you don't have to use plymouth for decryption passphrase and there are several on-screen keyboard implementations out there that can be used instead.

@agowa338 > It is quite reasonable to expect it to "not be that simple" especially when it existed for 5 years by now.

There are so many things I have worked on in mobile GNU/Linux (cameras included) that weren't done for several years that turned out to be just a case of "nobody has looked deep enough at it yet" that it's generally safe to assume you'll be able to do *something*, and even if not then figuring out why it's not the case is still a valuable outcome 😛

@agowa338 That's why I'm talking about hacking on existing ports so much. It gives tangible results right away while operating in the same knowledge space.

@agowa338 But there's no equation there yet. Your job is to come up with 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