Pine64 should re-evaluate their community priorities

Re:Pine64 should re-evaluate their community priorities by matheusmoreira on Thursday January 20, 2022 @10:42AM (#30010255)

> Implementing and upstreaming kernel drivers, u-Boot support, etc

I agree that this is important and I totally want to contribute but the truth is I don't have the knowledge to do this. Not yet at least. How does one learn how to do this?

I've written a small user space driver for some laptop USB stuff. I reverse engineered the manufacturer's proprietary applications and drivers and made a Linux program that talks to the hardware the same way. Is this the correct approach here?

[ Parent | on HN ]

Re:Pine64 should re-evaluate their community priorities by Mystlix on Thursday January 20, 2022 @11:50AM (#30011360)

>How does one learn how to do this?

It's not something you can learn in a fortnight. You first have to learn C and Assembly for the architecture you're using, then you need to study how different OSs on different hardware manage to make themselves boot and then you need to use this knowledge to study the SoC's documentation and implement the stuff there. If documentation were perfect maybe you'd only need to know how to program and simply follow the specification, but in these cases experience with a large number of cases is a must to navigate the environment.

[ Parent | on HN ]

Re:Pine64 should re-evaluate their community priorities by matheusmoreira on Friday January 21, 2022 @02:22PM (#30028658)

Thanks for the pointers.

[ Parent | on HN ]

Re:Pine64 should re-evaluate their community priorities by zozbot234 on Thursday January 20, 2022 @12:01PM (#30011535)

The postmarketOS wiki has some nice guides on how to work on hardware enablement for a mobile device - including mainline kernel support.

[ Parent | on HN ]

Re:Pine64 should re-evaluate their community priorities by matheusmoreira on Friday January 21, 2022 @02:22PM (#30028652)

I will read it.

[ Parent | on HN ]