Thank you for the insights Alan! That makes sense. I will look at the BSD code further.
Matteo On Thu, Aug 28, 2025, 3:23 PM Alan C. Assis <acas...@gmail.com> wrote: > Hi Matteo, > > I think for WiFi/BLE the driver will be straightforward after we get SDIO > working because RPi uses the same Broadcom chip (BCM43455) that is already > supported on NuttX. > > Fun fact is that WiFi driver was created by Cypress after they bought the > Broadcom WiFi IoT division ( > > https://investors.broadcom.com/news-releases/news-release-details/cypress-acquire-broadcoms-wireless-internet-things-business > ). > Probably some big company asked for NuttX support for that WiFi chip and > Cypress did it and then we found their code and integrated it into the > mainline. > > The RaspberryPi company/foundation normally does the Linux port, so they > don't need to release any secret documentation from Broadcom. > > So we need to make NuttX more widespread first to get this same level of > benefits :-) > > It means that probably we will need to do reverse engineering to get these > other drivers working. > > We cannot look at the Linux source code, because it is GPL license, but we > can look at the FreeBSD code: https://wiki.freebsd.org/arm/Raspberry%20Pi > > BR, > > Alan > > On Thu, Aug 28, 2025 at 3:45 PM Matteo Golin <matteo.go...@gmail.com> > wrote: > > > Hi Tomek, > > > > Thanks so much! I actually hadn't thought of that, maybe we could ask for > > help from the foundation. Do you know who's the best point of contact for > > that? > > > > I know Linux must have received the datasheets to make Raspberry Pi OS. > No > > offence to NuttX, but Linux is pretty popular in comparison. If Broadcom > or > > Raspberry Pi would release us some information that would be an immense > > help. I suspect there was some kind of deal with the Linux group but I > have > > no idea. I believe even QNX didn't have access to the datasheets and > rather > > just reverse engineered the Linux drivers. > > > > Matteo > > > > On Thu, Aug 28, 2025, 12:42 PM Tomek CEDRO <to...@cedro.info> wrote: > > > > > On Tue, Aug 26, 2025 at 10:05 PM Matteo Golin <matteo.go...@gmail.com> > > > wrote: > > > > I2C still needs some work unfortunately. However, I agree with you > > > > generally. Personally, I think HDMI, networking (including WiFi and > > BLE) > > > > and some kind of interaction with storage (eMMC or SD card) are the > > most > > > > important. Unfortunately, those are likely going to be the most > > difficult > > > > because of the lack of documentation on the peripherals. It is > > definitely > > > > not an impossible task, but it will be challenging. Hence my request > > for > > > > creating the new project roadmap, so maybe some discoveries can be > > > > documented there and more eyes can get on the RPi implementation. > > > > > > The lack of documentation is a real pain, and known issue for years in > > > many areas, but some vendors are especially famous for that. > > > > > > Considering someone wants to create Open-Source drivers for free and > > > bring customers to the vendor. > > > > > > Maybe we could ask Apache Foundation for help in obtaining required > > > datasheets? :-) > > > > > > -- > > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > > > > >
