Re: RPI 4B Roadmap

Yeah, at the time you make something even partially working with zero documentation in a free time some new and better chip shows show up and the whole work is wasted and this time gets shorter and shorter :D Its good to make something like this once or twice, but after some years you just want to

Re: RPI 4B Roadmap

No response from #infra@slack, I just sent request to dev@community.apache mailing list maybe someone can reply over there :-) https://lists.apache.org/thread/n9y5vrvjm23npwgbr45f7zq5ys5l8dok We should also know the official stance from Broadcom and RPI Foundation :-) Thanks :-) Tomek On Thu, A

Re: RPI 4B Roadmap

Thank you for the insights everyone! I reached out to the RPi foundation this morning. I tried to reach out to Broadcom but every single form on their website that I tried gave me a submission error, so I'm not sure I'll have any luck there. They don't seem very open-source focused. My primary mo

Re: RPI 4B Roadmap

Hi, If I recall correctly, Eben Upton who founded raspi is an ex broadcom employee? So either broadcom did the ports to these Pi SoCs, or raspi did it based on privileged broadcom private docs. https://en.wikipedia.org/wiki/Eben_Upton He is a former technical director and ASIC

Re: RPI 4B Roadmap

Hardware register layouts, bit meanings, and constants are facts about the hardware, not a creative expression by Linux developers. So you can look at Linux code to reverse-engineer and understand how the hardware works, even if you don't release your code under the GPL. But of course if you can lo