You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Matteo Golin <ma...@gmail.com> on 2025/11/05 21:48:58 UTC

Re: RPI 4B Roadmap

Hi all,

Despite a relatively small bug with transfer size limits, the RPi4B microSD
card support is basically done. This is largely in part to how simple it is
on NuttX to write a lower-half SDIO implementation and have things just
work, which is incredible :)

I now (ambitiously) want to set my eyes on graphics. It turns out that
rendering with a framebuffer is actually quite easy, but very CPU
intensive. I'm going to need to figure out how to get at the GPU properly. *My
question is: *is anyone familiar with examples on how to implement the
necessary "lower-half" for the NuttX graphics library? I.e. what
functions/drivers I would need to get written to allow the basic windowing
display manager & LVGL to work on the HDMI outputs of the Pi? I have
briefly read the docs about the window manager and saw that there is a
framebuffer char driver that can be implemented, but I'm not sure how well
that scales to decent graphics. I suppose this is relatively uncharted
territory on an RTOS designed mainly with LCDs in mind as the only graphics
(?). If anyone has implemented graphics support for a device before and can
let me know a few source files to look at, that would be great!

My main goal is essentially to get decently fast graphics going, since once
that's done and some USB HID device support is set up, I can port DOOM to
NuttX :)

Thanks,
Matteo

On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
wrote:

> Thanks Tomek! That would be a good resource.
>
> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
>
>> OpenBSD 7.8 has been just released and it has official support for rPI
>> 5 with all sorts of peripherals.. maybe this is the new source to look
>> for drivers code? :-)
>>
>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
>>
>> https://cvsweb.openbsd.org/src/
>>
>> Have a good day :-)
>> Tomek
>>
>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
>> wrote:
>> >
>> > Thanks Alan! Maybe I will reach out to Arasan, could have more luck than
>> > with Broadcom, but I doubt it.
>> >
>> > I'll take a look at these documents!
>> >
>> > Thanks again,
>> > Matteo
>> >
>> > On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com> wrote:
>> >
>> > > Hi Matteo,
>> > >
>> > > Please that a look:
>> > > https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
>> > >
>> > > There is an option to Download (request) the Datasheet from that
>> page, but
>> > > you can access it directly here:
>> > >
>> > >
>> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
>> > >
>> > > This document is more about the IP core details, but could give you
>> more
>> > > understanding about internal block of the SDIO controller (its FIFO,
>> > > initialization diagram, etc)
>> > >
>> > > You can also try to find the original
>> > > SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
>> Raspberry
>> > > documentation.
>> > >
>> > > BR,
>> > >
>> > > Alan
>> > >
>> > >
>> > >
>> > > On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <matteo.golin@gmail.com
>> >
>> > > wrote:
>> > >
>> > > > Hi Alan,
>> > > >
>> > > > Thank you for the tips! Yes, SDIO looks pretty involved compared to
>> SPI
>> > > or
>> > > > I2C. I'll try reading the specification like you suggested.
>> > > >
>> > > > The BCM2711 datasheet doesn't document it at all, however the EMMC
>> > > > interface is supposedly the exact same from the BCM2835 and the
>> registers
>> > > > there are at least documented. All I know is that it is using an
>> > > interface
>> > > > by Arasan. I'm not as familiar with NuttX, but if this at all looks
>> like
>> > > > something that's already been supported, please let me know. In the
>> > > > meantime, I'll look through the SDIO implementations to check:
>> > > >
>> > >
>> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
>> > > > (page 65)
>> > > >
>> > > > Thanks again!
>> > > > Matteo
>> > > >
>> > > > On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
>> wrote:
>> > > >
>> > > > > HI Matteo,
>> > > > >
>> > > > > I implemented the SDIO support for LPC43 some years ago and what
>> helped
>> > > > me
>> > > > > most was reading the SD/MMC specification, the LPC43 reference
>> manual
>> > > and
>> > > > > enabling the NuttX SD/MMC debug messages.
>> > > > >
>> > > > > There are many details to take care of: clock enable for the
>> > > controller,
>> > > > > interrupts, pins configuration, etc.
>> > > > >
>> > > > > Unfortunately, the BCM2711 doc is not good. You can start
>> verifying the
>> > > > > registers, maybe it is based on some SD/MMC core IP already
>> supported
>> > > by
>> > > > > NuttX.
>> > > > >
>> > > > > BR,
>> > > > >
>> > > > > Alan
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
>> matteo.golin@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi everyone,
>> > > > > >
>> > > > > > Now that I2C has been tackled, I am moving on to SDIO
>> interfaces so
>> > > the
>> > > > > SD
>> > > > > > card can be interacted with from NuttX.
>> > > > > >
>> > > > > > The NuttX SDIO documentation is a little bare, and I'm not the
>> most
>> > > > > > familiar with SDIO. Does anyone have any recommendations for
>> > > > > > implementations to look at (besides the STM32 one that is
>> linked in
>> > > the
>> > > > > > docs), resources to read (any blog posts from when you ported
>> SDIO)
>> > > or
>> > > > > > advice in general? It would be much appreciated.
>> > > > > >
>> > > > > > Thank you,
>> > > > > > Matteo
>> > > > > >
>> > > > > > On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
>> matteo.golin@gmail.com>
>> > > > > wrote:
>> > > > > >
>> > > > > > > Got another response from my earlier request to Raspberry Pi
>> > > through
>> > > > > > their
>> > > > > > > website:
>> > > > > > >
>> > > > > > > Hi Matteo
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >> Thanks for getting in touch. We don't actually have any more
>> > > > > > >> documentation that we can release on this. My usual
>> recommendation
>> > > > is
>> > > > > > for
>> > > > > > >> SW people to take a look at the Linux drivers to get a closer
>> > > > > > understanding
>> > > > > > >> of how the HW works. Not ideal, but the best I can offer.
>> > > > > > >
>> > > > > > >
>> > > > > > > So I guess everyone is telling us the same thing!
>> > > > > > >
>> > > > > > >
>> > > > > > > On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <to...@cedro.info>
>> > > wrote:
>> > > > > > >
>> > > > > > >> Sure! Public now :-)
>> > > > > > >> Tomek
>> > > > > > >>
>> > > > > > >> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
>> > > matteo.golin@gmail.com
>> > > > >
>> > > > > > >> wrote:
>> > > > > > >> >
>> > > > > > >> > I have populated the RPi 4B project with some starting
>> issues to
>> > > > > > tackle
>> > > > > > >> for
>> > > > > > >> > the 4B implementation. I see that the project is marked as
>> > > > private;
>> > > > > is
>> > > > > > >> > there any way to make it visible to potential contributors
>> just
>> > > > > > visiting
>> > > > > > >> > the GitHub page? I think if they can see a list of issues
>> in one
>> > > > > place
>> > > > > > >> when
>> > > > > > >> > they go to the page it might help.
>> > > > > > >> >
>> > > > > > >> > Thanks,
>> > > > > > >> > Matteo
>> > > > > > >> >
>> > > > > > >> > On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
>> tomek@cedro.info>
>> > > > > wrote:
>> > > > > > >> >
>> > > > > > >> > > Thank you Linguini, good luck and have fun! :-)
>> > > > > > >> > > Tomek
>> > > > > > >> > >
>> > > > > > >> > > On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
>> > > > > matteo.golin@gmail.com
>> > > > > > >
>> > > > > > >> > > wrote:
>> > > > > > >> > > >
>> > > > > > >> > > > To update the community, we've been told by Gordon
>> that the
>> > > Pi
>> > > > > > >> Foundation
>> > > > > > >> > > > doesn't have any documentation for the chip beyond
>> what was
>> > > > > > written
>> > > > > > >> in
>> > > > > > >> > > the
>> > > > > > >> > > > peripheral datasheet. Broadcom themselves has written
>> the
>> > > > Linux
>> > > > > > >> drivers
>> > > > > > >> > > and
>> > > > > > >> > > > Raspberry Pi has only made some slight bug fixes, etc.
>> We've
>> > > > > been
>> > > > > > >> > > suggested
>> > > > > > >> > > > to read the source to discover undocumented
>> > > > > > registers/configuration
>> > > > > > >> > > options.
>> > > > > > >> > > >
>> > > > > > >> > > > I plan to still continue with the port until the
>> feature set
>> > > > on
>> > > > > > >> NuttX is
>> > > > > > >> > > > equal or greater to what is available on QNX. I at
>> least
>> > > want
>> > > > to
>> > > > > > get
>> > > > > > >> > > > Ethernet and some graphics running after the base
>> peripheral
>> > > > set
>> > > > > > >> (I2C,
>> > > > > > >> > > SPI,
>> > > > > > >> > > > UART) are supported.
>> > > > > > >> > > >
>> > > > > > >> > > > Matteo
>> > > > > > >> > > >
>> > > > > > >> > > > On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
>> > > > > > >> matteo.golin@gmail.com>
>> > > > > > >> > > wrote:
>> > > > > > >> > > >
>> > > > > > >> > > > > Very interesting Sebastian. I got that impression
>> from
>> > > > > Broadcom
>> > > > > > >> when I
>> > > > > > >> > > was
>> > > > > > >> > > > > initially trying to port NuttX to the Pi. The
>> inability to
>> > > > > > submit
>> > > > > > >> > > forms on
>> > > > > > >> > > > > their website seems like it might be by design...
>> > > > > > >> > > > >
>> > > > > > >> > > > > I'm hopeful the Raspberry Pi Foundation will have
>> > > something
>> > > > > more
>> > > > > > >> for
>> > > > > > >> > > us to
>> > > > > > >> > > > > work with, they seem more positive to FOSS.
>> Otherwise I
>> > > will
>> > > > > > still
>> > > > > > >> > > continue
>> > > > > > >> > > > > with reverse engineering until at least the point
>> where
>> > > the
>> > > > > > >> > > functionality
>> > > > > > >> > > > > driver-wise is on par with QNX.
>> > > > > > >> > > > >
>> > > > > > >> > > > > On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
>> > > > tomek@cedro.info>
>> > > > > > >> wrote:
>> > > > > > >> > > > >
>> > > > > > >> > > > >> James Dougherty contacted us with Gordon
>> Hollingworth
>> > > from
>> > > > > > >> Raspberry
>> > > > > > >> > > > >> Pi Foundation recently :-) We are waiting for
>> response
>> > > :-)
>> > > > I
>> > > > > > >> really
>> > > > > > >> > > > >> hope we can get some sort of documentation and/or
>> code
>> > > > > samples
>> > > > > > to
>> > > > > > >> > > > >> write high quality NuttX port for the big
>> raspberries :-)
>> > > > > > >> > > > >>
>> > > > > > >> > > > >> Open-Source matters even more in this crazy world.
>> Thanks
>> > > > for
>> > > > > > >> > > > >> interesting article Sebastien! Personally I think we
>> > > should
>> > > > > > >> focus only
>> > > > > > >> > > > >> on vendors that support Open-Source. What is the
>> reason
>> > > for
>> > > > > > >> bumping
>> > > > > > >> > > > >> sales for companies that in the end can sue you for
>> > > > > reversing?
>> > > > > > :D
>> > > > > > >> > > > >>
>> > > > > > >> > > > >> Have a good day folks :-)
>> > > > > > >> > > > >> Tomek
>> > > > > > >> > > > >>
>> > > > > > >> > > > >>
>> > > > > > >> > > > >>
>> > > > > > >> > > > >> On Sun, Aug 31, 2025 at 10:15 AM Sebastien Lorquet <
>> > > > > > >> > > sebastien@lorquet.fr>
>> > > > > > >> > > > >> wrote:
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > Hello,
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > I just found this interesting document:
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >>
>> > > > > > >> > >
>> > > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> > >
>> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > In a summary, if you expect anything cool from
>> > > broadcom:
>> > > > > > dont.
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > go go go reverse engineering!
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > Sebastien
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> >
>> > > > > > >> > > > >> > On 8/29/25 15:37, Tomek CEDRO wrote:
>> > > > > > >> > > > >> > > 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
>> > > > > > >> tomek@cedro.info>
>> > > > > > >> > > wrote:
>> > > > > > >> > > > >> > >> I just asked question at #asfinfra / slack,
>> maybe
>> > > > > someone
>> > > > > > >> can
>> > > > > > >> > > help
>> > > > > > >> > > > >> > >> there or recommend someone who can, waiting for
>> > > > response
>> > > > > > :-)
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >> For a good start you can contact Broadcom and
>> > > > > RaspberryPi
>> > > > > > >> > > Foundation,
>> > > > > > >> > > > >> > >> introduce yourself as Apache NuttX RTOS
>> developer
>> > > that
>> > > > > > want
>> > > > > > >> to
>> > > > > > >> > > port
>> > > > > > >> > > > >> > >> NuttX to rPI boards, and just ask if
>> DataSheets are
>> > > > > > >> available
>> > > > > > >> > > :-) We
>> > > > > > >> > > > >> > >> will know then first hand if this is possible
>> or are
>> > > > > there
>> > > > > > >> any
>> > > > > > >> > > > >> > >> problems / requirements :-)
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >> You can ask for 4B and probably Zero-2W SoC
>> > > > > documentation
>> > > > > > >> these
>> > > > > > >> > > seems
>> > > > > > >> > > > >> > >> most popular nowadays :-)
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >> Thanks :-)
>> > > > > > >> > > > >> > >> Tomek
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin <
>> > > > > > >> > > matteo.golin@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 <
>> > > > > > >> tomek@cedro.info>
>> > > > > > >> > > > >> wrote:
>> > > > > > >> > > > >> > >>>
>> > > > > > >> > > > >> > >>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
>> Golin <
>> > > > > > >> > > > >> matteo.golin@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
>> > > > > > >> > > > >> > >>>>
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >>
>> > > > > > >> > > > >> > >> --
>> > > > > > >> > > > >> > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>> > > > > > >> > > > >> > >
>> > > > > > >> > > > >> > >
>> > > > > > >> > > > >>
>> > > > > > >> > > > >>
>> > > > > > >> > > > >>
>> > > > > > >> > > > >> --
>> > > > > > >> > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>> > > > > > >> > > > >>
>> > > > > > >> > > > >
>> > > > > > >> > >
>> > > > > > >> > >
>> > > > > > >> > >
>> > > > > > >> > > --
>> > > > > > >> > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>> > > > > > >> > >
>> > > > > > >>
>> > > > > > >>
>> > > > > > >>
>> > > > > > >> --
>> > > > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>> > > > > > >>
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>>
>>
>>
>> --
>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>
>

Re: RPI 4B Roadmap

Posted by Matteo Golin <ma...@gmail.com>.
I agree Tomek!

Tim, I have a similar question. The frame-buffer driver (according to the
docs) provides a way for NuttX to bypass the kernel and directly manipulate
a frame-buffer. LVGL demos and other apps (like the fb example) appear to
be built on top of this frame-buffer driver. However, and my understanding
may be flawed, there are other graphics implementations for the NuttX
graphics subsystem (
https://nuttx.apache.org/docs/latest/components/nxgraphics/index.html). It
looks like the part a developer would implement for their hardware is the
NXGLIB bit (?) The API is described here:
https://nuttx.apache.org/docs/latest/components/nxgraphics/nxgl.html

Probably for DOOM I will write the implementation to use the frame-buffer
driver, since that seems pretty widely supported for NuttX graphics-capable
devices. I think it also meshes well with the version of DOOM I plan to
use: https://github.com/ozkl/doomgeneric

I used this to get DOOM ported to QNX back when I worked there. It has its
own RAM framebuffer that it does all the rendering to, and I would just
have to copy it to the device framebuffer (which I imagine boils down to a
single memcpy). The only problem I see with it is that it's GPL2 licensed.
I think that there is probably nobody who will use it in a production NuttX
application, more of a hobbyist curiosity, so perhaps that's fine anyways.
Otherwise I can try porting fbDOOM directly once I get the proof-of-concept
working, which doesn't appear to have a license and is made for framebuffer
devices as well. doomgeneric ran decently fast on the Pi 4B back at QNX (I
never noticed speed issues) so it probably doesn't need anything fancy to
work. Maybe it would benefit from DMA and that's it.

Matteo

On Sat, Nov 8, 2025 at 1:52 PM Tim Hardisty <ti...@gmail.com> wrote:

> Dipping in and out here as I’m supposed to be on holiday lol. If the
> framebuffer is the low level interface to the hardware (?) what would be
> the right NuttX/portable graphics intermediate language?
>
> Regards,
>
> Tim.
>
> > On 8 Nov 2025, at 19:28, Tomek CEDRO <to...@cedro.info> wrote:
> >
> > We also need to create BAD APPLE on NuttX as our ultimate multimedia
> > portability benchmark :D :D
> >
> > Some examples:
> > https://www.youtube.com/watch?v=nNC6aTSKiwk
> > https://www.youtube.com/watch?v=MEmF7eNj5U8
> > https://www.youtube.com/watch?v=cd5iEeIe7L0
> > https://www.youtube.com/watch?v=4kdtiOyJgtc
> > https://www.youtube.com/watch?v=R6myIbJpUWo
> > https://www.youtube.com/shorts/ObM7cnKjjY8
> > https://www.youtube.com/watch?v=B9TrOxXer4E
> > https://www.youtube.com/watch?v=xazooShtoTM
> > https://www.youtube.com/watch?v=5NXSMdUH_Cg
> > https://www.youtube.com/watch?v=i0NjDNyZfbY
> > https://www.youtube.com/watch?v=dx76YPgZviE
> >
> > And many many many more :-)
> > https://www.youtube.com/results?search_query=bad+apple+hardware
> >
> > Tomek
> >
> >> On Sat, Nov 8, 2025 at 5:16 PM Matteo Golin <ma...@gmail.com>
> wrote:
> >>
> >> That's very cool! A wolfenstein engine on NuttX is pretty interesting. I
> >> figure having a couple games on NuttX could attract some curiosity from
> >> hobbyists, and there's no better choice than games from the era of
> clever,
> >> low-resource rendering and physics. DOOM has also become somewhat of a
> >> "trend" to port to low-resource devices (not the the Pi4B meets that
> >> description). I've seen people run it on disposable vapes, microwaves
> and
> >> even fancy pregnancy tests.
> >>
> >> Matteo
> >>
> >>> On Sat, Nov 8, 2025 at 9:16 AM Tim Hardisty <ti...@gmail.com>
> wrote:
> >>>
> >>> Or was it a dos emulator; don’t remember!
> >>>
> >>>
> >>>> On 8 Nov 2025, at 15:03, Tim Hardisty <ti...@gmail.com>
> wrote:
> >>>>
> >>>> Doom was the first and last “full graphics” I played I think. Doom
> >>> feats after hours in the 1990’s maybe?
> >>>>
> >>>> Bring back Commander Keen lol.
> >>>>
> >>>> (Yes, have played it some times with Win3 emulators!)
> >>>>
> >>>> Regards,
> >>>>
> >>>> Tim.
> >>>>
> >>>>> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
> >>>>>
> >>>>>   *
> >>>>> Thanks again everyone for your help so far! One step closer to DOOM
> on
> >>>>>
> >>>>> NuttX :)
> >>>>>
> >>>>> Back in the old days when games were pure software, I enjoyed writing
> >>> games for NuttX.  I have wolfenstein-like engine and an experimental 3D
> >>> ray-casting engine.  These used to run on NuttX.  The latter was once a
> >>> part of the apps/ repository but I removed it when I donated NuttX to
> >>> Apache (since I didn't intend to donate that [art).  But I suppose it
> is
> >>> still in the GIT history.
> >>>>>
> >>>>> UNRELATED:  When NuttX was donated, there were a lot of files in the
> >>> repository that should not have been released and were removed in this
> >>> way.  Many other files with different licenses were present at the
> time of
> >>> release and these had to be sanitized, to make them Apache correct
> (thanks
> >>> almost entirely to Alin Jerpelea).  When we talk about NuttX being
> Apache 2
> >>> copyrighted by the ASF, we really only the git repository from a
> certain
> >>> point forward
> >>>>>
> >>>>> Prior to that, checkouts from the repository are BSD licensed and
> >>> copyrighted by me.
> >>>>>
> >>>>> I also used to run the public 2-D Wolfenstein-like screen saver on
> >>> NuttX.  It worked fine mostly out of the box.
> >>>>>
> >>>>> ________________________________
> >>>>> From: Matteo Golin <ma...@gmail.com>
> >>>>> Sent: Friday, November 7, 2025 9:31 PM
> >>>>> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> >>>>> Subject: Re: RPI 4B Roadmap
> >>>>>
> >>>>> I managed to get something working with the frame buffer interface,
> so
> >>>>> success so far! https://github.com/apache/nuttx/pull/17294
> >>>>>
> >>>>> Unfortunately, I encountered an issue trying to compile the LVGL demo
> >>> so it
> >>>>> hasn't been much more interesting than some test rectangles so far.
> >>>>> https://github.com/apache/nuttx-apps/issues/3208
> >>>>>
> >>>>> The frame-buffer driver was actually really simple to get working
> after
> >>>>> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for
> >>> the
> >>>>> easy-to-implement driver)! I will probably go back and document the
> bit
> >>> of
> >>>>> the frame buffer lower-half that I understand, since a little bit of
> >>>>> developer documentation for how to write a lower-half and what's
> exactly
> >>>>> needed to get running would be useful. There's also no docs for the
> >>>>> framebuffer example application, which I plan to fix shortly. It
> would
> >>> be
> >>>>> good to know what the output should look like so I'm not scratching
> my
> >>> head
> >>>>> wondering if I got it right or not :)
> >>>>>
> >>>>> Thanks again everyone for your help so far! One step closer to DOOM
> on
> >>>>> NuttX :)
> >>>>>
> >>>>> Matteo
> >>>>>
> >>>>>>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info>
> wrote:
> >>>>>>
> >>>>>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <
> matteo.golin@gmail.com>
> >>>>>>> wrote:
> >>>>>>> 1) I am actually familiar with the rpi4-osdev project. In part 5,
> the
> >>>>>>> author uses the framebuffer approach for graphics:
> >>>>>>>
> >>>
> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> >>>>>>> This is actually a really simple approach to implement, which is
> why I
> >>>>>>> imagine it wouldn't be difficult to integrate with NuttX's frame
> >>> buffer
> >>>>>>> method of graphics. The main problem for me is that it's very
> slow. I
> >>>>>> want
> >>>>>>> to figure out how to leverage the actual GPU so that graphics can
> be
> >>>>>> faster
> >>>>>>> and more complex. I have not started looking extensively into that
> >>> yet,
> >>>>>> but
> >>>>>>> was mainly wondering how that approach fits into NuttX's graphics
> >>> system.
> >>>>>>
> >>>>>> From the long years on FreeBSD desktop where nvidia is the only
> vendor
> >>>>>> providing native high quality GPU drivers it seems good to have
> >>>>>> "generic" framebuffer driver that will work on any hardware in the
> >>>>>> first place and then GPU specific drivers with hardware acceleration
> >>>>>> where available. This allows not only having graphics on anything,
> but
> >>>>>> more importantly a fallback when GPU drivers fail / buggy /
> >>>>>> unavailable. Anything here means not only Xorg (and similar) but
> also
> >>>>>> raw console that can launch framebuffer applications or a mouse
> >>>>>> pointer that can copy-paste in the raw console! :-) Console woks on
> >>>>>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works
> on
> >>>>>> top of the framebuffer (when launched it goes to place of
> /dev/ttyv8).
> >>>>>> This is modular and versatile design that allows text mode console
> on
> >>>>>> video display, graphical applications in raw video console, and Xorg
> >>>>>> or similar.
> >>>>>>
> >>>>>> There are two framebuffer drivers on FreeBSD:
> >>>>>> 1. VESA (old / bios machines):
> >>>>>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
> >>>>>> 2. SCFB (new / usefi machines):
> >>>>>> https://man.freebsd.org/cgi/man.cgi?query=scfb
> >>>>>>
> >>>>>> Therer are two console drivers on FreeBSD:
> >>>>>> 1. SYSCONS/SC (old / bios machines):
> >>>>>> https://man.freebsd.org/cgi/man.cgi?query=syscons
> >>>>>> 2. VT (new / uefi machines):
> >>> https://man.freebsd.org/cgi/man.cgi?query=vt
> >>>>>>
> >>>>>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
> >>>>>> works). It seems work-in-progress but works for years already. The
> >>>>>> only problem I saw so far is the console colors packed into two bit
> >>>>>> field (afair) that may need structure changes to get dedicated 8..24
> >>>>>> bit bit field to get more colors that will be breaking change thus
> it
> >>>>>> may be good to think ahead and use this wider field if we want to do
> >>>>>> something similar in NuttX :-)
> >>>>>>
> >>>>>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
> >>>>>>
> >>>>>> Hope this helps a bit or gives some reference point :-)
> >>>>>>
> >>>>>> On Linux ~20 years ago it was also possible to draw on raw video
> >>>>>> framebuffer using DirectFB (now version 2) even with no Xorg, see
> >>>>>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS
> approach is
> >>>>>> a moving target and kind of PITA because FreeBSD followed that path
> to
> >>>>>> have GPU drivers compatible with Linux for easier porting and this
> >>>>>> only brings problems because things change constantly and are pain
> to
> >>>>>> maintain / use thus I would recommend to avoid this path :-(
> >>>>>>
> >>>>>> I guess we care most about this design / approach where we have
> >>>>>> FrameBuffer that allows drawing directly (i.e. LVGL), having
> console,
> >>>>>> or Xorg or similar (there is example Xorg compatible server in
> >>>>>> NuttX!!) :-)
> >>>>>>
> >>>>>> --
> >>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>
> >>>
> >
> >
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: RPI 4B Roadmap

Posted by Matteo Golin <ma...@gmail.com>.
Hello everyone,

I'm trying to tackle DMA support for the Pi next. I found a "standard"
upper-half in `nuttx/dma/dma.h` that seems like it is what I need to
implement. However, that code is used nowhere in the entire kernel except
for the 16550 UART driver. Everything else seems to roll its own
implementation of a DMA driver. To make matters worse, the dma.h
implementation is not documented! Does anyone have an idea of a good way I
can approach DMA control? This would be very beneficial for a bunch of
peripherals (like the framebuffer and SDIO support), but I'm tempted to put
it on the back burner for now until I have some clarity about the
implementation details.

Best,
Matteo

On Sat, Nov 8, 2025 at 4:20 PM Tomek CEDRO <to...@cedro.info> wrote:

> On Sat, Nov 8, 2025 at 7:52 PM Tim Hardisty <ti...@gmail.com>
> wrote:
> > Dipping in and out here as I’m supposed to be on holiday lol. If the
> framebuffer is the low level interface to the hardware (?) what would be
> the right NuttX/portable graphics intermediate language?
>
> Well free time is a good time to do some interesting work indeed :D
>
> On top of video framebuffer and probably libinput (or similar) various
> libraries can run providing what is needed:
> 1. LVGL to implement user app, maybe even our default console terminal.
> 2. SDL2 to provide multiplatform portability to amazing amount of
> existing multimedia applications, video players, games, emulators,
> etc.
>
> I think SDL2 is most important because almost all existing
> applications can work on top of that and these could be just
> cross-compiled to NuttX in place of BSD or Linux :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: RPI 4B Roadmap

Posted by Tomek CEDRO <to...@cedro.info>.
On Sat, Nov 8, 2025 at 7:52 PM Tim Hardisty <ti...@gmail.com> wrote:
> Dipping in and out here as I’m supposed to be on holiday lol. If the framebuffer is the low level interface to the hardware (?) what would be the right NuttX/portable graphics intermediate language?

Well free time is a good time to do some interesting work indeed :D

On top of video framebuffer and probably libinput (or similar) various
libraries can run providing what is needed:
1. LVGL to implement user app, maybe even our default console terminal.
2. SDL2 to provide multiplatform portability to amazing amount of
existing multimedia applications, video players, games, emulators,
etc.

I think SDL2 is most important because almost all existing
applications can work on top of that and these could be just
cross-compiled to NuttX in place of BSD or Linux :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: RPI 4B Roadmap

Posted by Tim Hardisty <ti...@gmail.com>.
Dipping in and out here as I’m supposed to be on holiday lol. If the framebuffer is the low level interface to the hardware (?) what would be the right NuttX/portable graphics intermediate language?

Regards,

Tim.

> On 8 Nov 2025, at 19:28, Tomek CEDRO <to...@cedro.info> wrote:
> 
> We also need to create BAD APPLE on NuttX as our ultimate multimedia
> portability benchmark :D :D
> 
> Some examples:
> https://www.youtube.com/watch?v=nNC6aTSKiwk
> https://www.youtube.com/watch?v=MEmF7eNj5U8
> https://www.youtube.com/watch?v=cd5iEeIe7L0
> https://www.youtube.com/watch?v=4kdtiOyJgtc
> https://www.youtube.com/watch?v=R6myIbJpUWo
> https://www.youtube.com/shorts/ObM7cnKjjY8
> https://www.youtube.com/watch?v=B9TrOxXer4E
> https://www.youtube.com/watch?v=xazooShtoTM
> https://www.youtube.com/watch?v=5NXSMdUH_Cg
> https://www.youtube.com/watch?v=i0NjDNyZfbY
> https://www.youtube.com/watch?v=dx76YPgZviE
> 
> And many many many more :-)
> https://www.youtube.com/results?search_query=bad+apple+hardware
> 
> Tomek
> 
>> On Sat, Nov 8, 2025 at 5:16 PM Matteo Golin <ma...@gmail.com> wrote:
>> 
>> That's very cool! A wolfenstein engine on NuttX is pretty interesting. I
>> figure having a couple games on NuttX could attract some curiosity from
>> hobbyists, and there's no better choice than games from the era of clever,
>> low-resource rendering and physics. DOOM has also become somewhat of a
>> "trend" to port to low-resource devices (not the the Pi4B meets that
>> description). I've seen people run it on disposable vapes, microwaves and
>> even fancy pregnancy tests.
>> 
>> Matteo
>> 
>>> On Sat, Nov 8, 2025 at 9:16 AM Tim Hardisty <ti...@gmail.com> wrote:
>>> 
>>> Or was it a dos emulator; don’t remember!
>>> 
>>> 
>>>> On 8 Nov 2025, at 15:03, Tim Hardisty <ti...@gmail.com> wrote:
>>>> 
>>>> Doom was the first and last “full graphics” I played I think. Doom
>>> feats after hours in the 1990’s maybe?
>>>> 
>>>> Bring back Commander Keen lol.
>>>> 
>>>> (Yes, have played it some times with Win3 emulators!)
>>>> 
>>>> Regards,
>>>> 
>>>> Tim.
>>>> 
>>>>> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
>>>>> 
>>>>>   *
>>>>> Thanks again everyone for your help so far! One step closer to DOOM on
>>>>> 
>>>>> NuttX :)
>>>>> 
>>>>> Back in the old days when games were pure software, I enjoyed writing
>>> games for NuttX.  I have wolfenstein-like engine and an experimental 3D
>>> ray-casting engine.  These used to run on NuttX.  The latter was once a
>>> part of the apps/ repository but I removed it when I donated NuttX to
>>> Apache (since I didn't intend to donate that [art).  But I suppose it is
>>> still in the GIT history.
>>>>> 
>>>>> UNRELATED:  When NuttX was donated, there were a lot of files in the
>>> repository that should not have been released and were removed in this
>>> way.  Many other files with different licenses were present at the time of
>>> release and these had to be sanitized, to make them Apache correct (thanks
>>> almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2
>>> copyrighted by the ASF, we really only the git repository from a certain
>>> point forward
>>>>> 
>>>>> Prior to that, checkouts from the repository are BSD licensed and
>>> copyrighted by me.
>>>>> 
>>>>> I also used to run the public 2-D Wolfenstein-like screen saver on
>>> NuttX.  It worked fine mostly out of the box.
>>>>> 
>>>>> ________________________________
>>>>> From: Matteo Golin <ma...@gmail.com>
>>>>> Sent: Friday, November 7, 2025 9:31 PM
>>>>> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
>>>>> Subject: Re: RPI 4B Roadmap
>>>>> 
>>>>> I managed to get something working with the frame buffer interface, so
>>>>> success so far! https://github.com/apache/nuttx/pull/17294
>>>>> 
>>>>> Unfortunately, I encountered an issue trying to compile the LVGL demo
>>> so it
>>>>> hasn't been much more interesting than some test rectangles so far.
>>>>> https://github.com/apache/nuttx-apps/issues/3208
>>>>> 
>>>>> The frame-buffer driver was actually really simple to get working after
>>>>> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for
>>> the
>>>>> easy-to-implement driver)! I will probably go back and document the bit
>>> of
>>>>> the frame buffer lower-half that I understand, since a little bit of
>>>>> developer documentation for how to write a lower-half and what's exactly
>>>>> needed to get running would be useful. There's also no docs for the
>>>>> framebuffer example application, which I plan to fix shortly. It would
>>> be
>>>>> good to know what the output should look like so I'm not scratching my
>>> head
>>>>> wondering if I got it right or not :)
>>>>> 
>>>>> Thanks again everyone for your help so far! One step closer to DOOM on
>>>>> NuttX :)
>>>>> 
>>>>> Matteo
>>>>> 
>>>>>>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:
>>>>>> 
>>>>>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
>>>>>>> wrote:
>>>>>>> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
>>>>>>> author uses the framebuffer approach for graphics:
>>>>>>> 
>>> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
>>>>>>> This is actually a really simple approach to implement, which is why I
>>>>>>> imagine it wouldn't be difficult to integrate with NuttX's frame
>>> buffer
>>>>>>> method of graphics. The main problem for me is that it's very slow. I
>>>>>> want
>>>>>>> to figure out how to leverage the actual GPU so that graphics can be
>>>>>> faster
>>>>>>> and more complex. I have not started looking extensively into that
>>> yet,
>>>>>> but
>>>>>>> was mainly wondering how that approach fits into NuttX's graphics
>>> system.
>>>>>> 
>>>>>> From the long years on FreeBSD desktop where nvidia is the only vendor
>>>>>> providing native high quality GPU drivers it seems good to have
>>>>>> "generic" framebuffer driver that will work on any hardware in the
>>>>>> first place and then GPU specific drivers with hardware acceleration
>>>>>> where available. This allows not only having graphics on anything, but
>>>>>> more importantly a fallback when GPU drivers fail / buggy /
>>>>>> unavailable. Anything here means not only Xorg (and similar) but also
>>>>>> raw console that can launch framebuffer applications or a mouse
>>>>>> pointer that can copy-paste in the raw console! :-) Console woks on
>>>>>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
>>>>>> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
>>>>>> This is modular and versatile design that allows text mode console on
>>>>>> video display, graphical applications in raw video console, and Xorg
>>>>>> or similar.
>>>>>> 
>>>>>> There are two framebuffer drivers on FreeBSD:
>>>>>> 1. VESA (old / bios machines):
>>>>>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
>>>>>> 2. SCFB (new / usefi machines):
>>>>>> https://man.freebsd.org/cgi/man.cgi?query=scfb
>>>>>> 
>>>>>> Therer are two console drivers on FreeBSD:
>>>>>> 1. SYSCONS/SC (old / bios machines):
>>>>>> https://man.freebsd.org/cgi/man.cgi?query=syscons
>>>>>> 2. VT (new / uefi machines):
>>> https://man.freebsd.org/cgi/man.cgi?query=vt
>>>>>> 
>>>>>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
>>>>>> works). It seems work-in-progress but works for years already. The
>>>>>> only problem I saw so far is the console colors packed into two bit
>>>>>> field (afair) that may need structure changes to get dedicated 8..24
>>>>>> bit bit field to get more colors that will be breaking change thus it
>>>>>> may be good to think ahead and use this wider field if we want to do
>>>>>> something similar in NuttX :-)
>>>>>> 
>>>>>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
>>>>>> 
>>>>>> Hope this helps a bit or gives some reference point :-)
>>>>>> 
>>>>>> On Linux ~20 years ago it was also possible to draw on raw video
>>>>>> framebuffer using DirectFB (now version 2) even with no Xorg, see
>>>>>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
>>>>>> a moving target and kind of PITA because FreeBSD followed that path to
>>>>>> have GPU drivers compatible with Linux for easier porting and this
>>>>>> only brings problems because things change constantly and are pain to
>>>>>> maintain / use thus I would recommend to avoid this path :-(
>>>>>> 
>>>>>> I guess we care most about this design / approach where we have
>>>>>> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
>>>>>> or Xorg or similar (there is example Xorg compatible server in
>>>>>> NuttX!!) :-)
>>>>>> 
>>>>>> --
>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>> 
>>> 
> 
> 
> 
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: RPI 4B Roadmap

Posted by Tomek CEDRO <to...@cedro.info>.
We also need to create BAD APPLE on NuttX as our ultimate multimedia
portability benchmark :D :D

Some examples:
https://www.youtube.com/watch?v=nNC6aTSKiwk
https://www.youtube.com/watch?v=MEmF7eNj5U8
https://www.youtube.com/watch?v=cd5iEeIe7L0
https://www.youtube.com/watch?v=4kdtiOyJgtc
https://www.youtube.com/watch?v=R6myIbJpUWo
https://www.youtube.com/shorts/ObM7cnKjjY8
https://www.youtube.com/watch?v=B9TrOxXer4E
https://www.youtube.com/watch?v=xazooShtoTM
https://www.youtube.com/watch?v=5NXSMdUH_Cg
https://www.youtube.com/watch?v=i0NjDNyZfbY
https://www.youtube.com/watch?v=dx76YPgZviE

And many many many more :-)
https://www.youtube.com/results?search_query=bad+apple+hardware

Tomek

On Sat, Nov 8, 2025 at 5:16 PM Matteo Golin <ma...@gmail.com> wrote:
>
> That's very cool! A wolfenstein engine on NuttX is pretty interesting. I
> figure having a couple games on NuttX could attract some curiosity from
> hobbyists, and there's no better choice than games from the era of clever,
> low-resource rendering and physics. DOOM has also become somewhat of a
> "trend" to port to low-resource devices (not the the Pi4B meets that
> description). I've seen people run it on disposable vapes, microwaves and
> even fancy pregnancy tests.
>
> Matteo
>
> On Sat, Nov 8, 2025 at 9:16 AM Tim Hardisty <ti...@gmail.com> wrote:
>
> > Or was it a dos emulator; don’t remember!
> >
> >
> > > On 8 Nov 2025, at 15:03, Tim Hardisty <ti...@gmail.com> wrote:
> > >
> > > Doom was the first and last “full graphics” I played I think. Doom
> > feats after hours in the 1990’s maybe?
> > >
> > > Bring back Commander Keen lol.
> > >
> > > (Yes, have played it some times with Win3 emulators!)
> > >
> > > Regards,
> > >
> > > Tim.
> > >
> > >> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
> > >>
> > >>   *
> > >> Thanks again everyone for your help so far! One step closer to DOOM on
> > >>
> > >> NuttX :)
> > >>
> > >> Back in the old days when games were pure software, I enjoyed writing
> > games for NuttX.  I have wolfenstein-like engine and an experimental 3D
> > ray-casting engine.  These used to run on NuttX.  The latter was once a
> > part of the apps/ repository but I removed it when I donated NuttX to
> > Apache (since I didn't intend to donate that [art).  But I suppose it is
> > still in the GIT history.
> > >>
> > >> UNRELATED:  When NuttX was donated, there were a lot of files in the
> > repository that should not have been released and were removed in this
> > way.  Many other files with different licenses were present at the time of
> > release and these had to be sanitized, to make them Apache correct (thanks
> > almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2
> > copyrighted by the ASF, we really only the git repository from a certain
> > point forward
> > >>
> > >> Prior to that, checkouts from the repository are BSD licensed and
> > copyrighted by me.
> > >>
> > >> I also used to run the public 2-D Wolfenstein-like screen saver on
> > NuttX.  It worked fine mostly out of the box.
> > >>
> > >> ________________________________
> > >> From: Matteo Golin <ma...@gmail.com>
> > >> Sent: Friday, November 7, 2025 9:31 PM
> > >> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> > >> Subject: Re: RPI 4B Roadmap
> > >>
> > >> I managed to get something working with the frame buffer interface, so
> > >> success so far! https://github.com/apache/nuttx/pull/17294
> > >>
> > >> Unfortunately, I encountered an issue trying to compile the LVGL demo
> > so it
> > >> hasn't been much more interesting than some test rectangles so far.
> > >> https://github.com/apache/nuttx-apps/issues/3208
> > >>
> > >> The frame-buffer driver was actually really simple to get working after
> > >> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for
> > the
> > >> easy-to-implement driver)! I will probably go back and document the bit
> > of
> > >> the frame buffer lower-half that I understand, since a little bit of
> > >> developer documentation for how to write a lower-half and what's exactly
> > >> needed to get running would be useful. There's also no docs for the
> > >> framebuffer example application, which I plan to fix shortly. It would
> > be
> > >> good to know what the output should look like so I'm not scratching my
> > head
> > >> wondering if I got it right or not :)
> > >>
> > >> Thanks again everyone for your help so far! One step closer to DOOM on
> > >> NuttX :)
> > >>
> > >> Matteo
> > >>
> > >>>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:
> > >>>
> > >>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
> > >>>> wrote:
> > >>>> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
> > >>>> author uses the framebuffer approach for graphics:
> > >>>>
> > https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> > >>>> This is actually a really simple approach to implement, which is why I
> > >>>> imagine it wouldn't be difficult to integrate with NuttX's frame
> > buffer
> > >>>> method of graphics. The main problem for me is that it's very slow. I
> > >>> want
> > >>>> to figure out how to leverage the actual GPU so that graphics can be
> > >>> faster
> > >>>> and more complex. I have not started looking extensively into that
> > yet,
> > >>> but
> > >>>> was mainly wondering how that approach fits into NuttX's graphics
> > system.
> > >>>
> > >>> From the long years on FreeBSD desktop where nvidia is the only vendor
> > >>> providing native high quality GPU drivers it seems good to have
> > >>> "generic" framebuffer driver that will work on any hardware in the
> > >>> first place and then GPU specific drivers with hardware acceleration
> > >>> where available. This allows not only having graphics on anything, but
> > >>> more importantly a fallback when GPU drivers fail / buggy /
> > >>> unavailable. Anything here means not only Xorg (and similar) but also
> > >>> raw console that can launch framebuffer applications or a mouse
> > >>> pointer that can copy-paste in the raw console! :-) Console woks on
> > >>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
> > >>> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
> > >>> This is modular and versatile design that allows text mode console on
> > >>> video display, graphical applications in raw video console, and Xorg
> > >>> or similar.
> > >>>
> > >>> There are two framebuffer drivers on FreeBSD:
> > >>> 1. VESA (old / bios machines):
> > >>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
> > >>> 2. SCFB (new / usefi machines):
> > >>> https://man.freebsd.org/cgi/man.cgi?query=scfb
> > >>>
> > >>> Therer are two console drivers on FreeBSD:
> > >>> 1. SYSCONS/SC (old / bios machines):
> > >>> https://man.freebsd.org/cgi/man.cgi?query=syscons
> > >>> 2. VT (new / uefi machines):
> > https://man.freebsd.org/cgi/man.cgi?query=vt
> > >>>
> > >>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
> > >>> works). It seems work-in-progress but works for years already. The
> > >>> only problem I saw so far is the console colors packed into two bit
> > >>> field (afair) that may need structure changes to get dedicated 8..24
> > >>> bit bit field to get more colors that will be breaking change thus it
> > >>> may be good to think ahead and use this wider field if we want to do
> > >>> something similar in NuttX :-)
> > >>>
> > >>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
> > >>>
> > >>> Hope this helps a bit or gives some reference point :-)
> > >>>
> > >>> On Linux ~20 years ago it was also possible to draw on raw video
> > >>> framebuffer using DirectFB (now version 2) even with no Xorg, see
> > >>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
> > >>> a moving target and kind of PITA because FreeBSD followed that path to
> > >>> have GPU drivers compatible with Linux for easier porting and this
> > >>> only brings problems because things change constantly and are pain to
> > >>> maintain / use thus I would recommend to avoid this path :-(
> > >>>
> > >>> I guess we care most about this design / approach where we have
> > >>> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
> > >>> or Xorg or similar (there is example Xorg compatible server in
> > >>> NuttX!!) :-)
> > >>>
> > >>> --
> > >>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> > >>>
> >



-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: RPI 4B Roadmap

Posted by Matteo Golin <ma...@gmail.com>.
That's very cool! A wolfenstein engine on NuttX is pretty interesting. I
figure having a couple games on NuttX could attract some curiosity from
hobbyists, and there's no better choice than games from the era of clever,
low-resource rendering and physics. DOOM has also become somewhat of a
"trend" to port to low-resource devices (not the the Pi4B meets that
description). I've seen people run it on disposable vapes, microwaves and
even fancy pregnancy tests.

Matteo

On Sat, Nov 8, 2025 at 9:16 AM Tim Hardisty <ti...@gmail.com> wrote:

> Or was it a dos emulator; don’t remember!
>
>
> > On 8 Nov 2025, at 15:03, Tim Hardisty <ti...@gmail.com> wrote:
> >
> > Doom was the first and last “full graphics” I played I think. Doom
> feats after hours in the 1990’s maybe?
> >
> > Bring back Commander Keen lol.
> >
> > (Yes, have played it some times with Win3 emulators!)
> >
> > Regards,
> >
> > Tim.
> >
> >> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
> >>
> >>   *
> >> Thanks again everyone for your help so far! One step closer to DOOM on
> >>
> >> NuttX :)
> >>
> >> Back in the old days when games were pure software, I enjoyed writing
> games for NuttX.  I have wolfenstein-like engine and an experimental 3D
> ray-casting engine.  These used to run on NuttX.  The latter was once a
> part of the apps/ repository but I removed it when I donated NuttX to
> Apache (since I didn't intend to donate that [art).  But I suppose it is
> still in the GIT history.
> >>
> >> UNRELATED:  When NuttX was donated, there were a lot of files in the
> repository that should not have been released and were removed in this
> way.  Many other files with different licenses were present at the time of
> release and these had to be sanitized, to make them Apache correct (thanks
> almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2
> copyrighted by the ASF, we really only the git repository from a certain
> point forward
> >>
> >> Prior to that, checkouts from the repository are BSD licensed and
> copyrighted by me.
> >>
> >> I also used to run the public 2-D Wolfenstein-like screen saver on
> NuttX.  It worked fine mostly out of the box.
> >>
> >> ________________________________
> >> From: Matteo Golin <ma...@gmail.com>
> >> Sent: Friday, November 7, 2025 9:31 PM
> >> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> >> Subject: Re: RPI 4B Roadmap
> >>
> >> I managed to get something working with the frame buffer interface, so
> >> success so far! https://github.com/apache/nuttx/pull/17294
> >>
> >> Unfortunately, I encountered an issue trying to compile the LVGL demo
> so it
> >> hasn't been much more interesting than some test rectangles so far.
> >> https://github.com/apache/nuttx-apps/issues/3208
> >>
> >> The frame-buffer driver was actually really simple to get working after
> >> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for
> the
> >> easy-to-implement driver)! I will probably go back and document the bit
> of
> >> the frame buffer lower-half that I understand, since a little bit of
> >> developer documentation for how to write a lower-half and what's exactly
> >> needed to get running would be useful. There's also no docs for the
> >> framebuffer example application, which I plan to fix shortly. It would
> be
> >> good to know what the output should look like so I'm not scratching my
> head
> >> wondering if I got it right or not :)
> >>
> >> Thanks again everyone for your help so far! One step closer to DOOM on
> >> NuttX :)
> >>
> >> Matteo
> >>
> >>>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:
> >>>
> >>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
> >>>> wrote:
> >>>> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
> >>>> author uses the framebuffer approach for graphics:
> >>>>
> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> >>>> This is actually a really simple approach to implement, which is why I
> >>>> imagine it wouldn't be difficult to integrate with NuttX's frame
> buffer
> >>>> method of graphics. The main problem for me is that it's very slow. I
> >>> want
> >>>> to figure out how to leverage the actual GPU so that graphics can be
> >>> faster
> >>>> and more complex. I have not started looking extensively into that
> yet,
> >>> but
> >>>> was mainly wondering how that approach fits into NuttX's graphics
> system.
> >>>
> >>> From the long years on FreeBSD desktop where nvidia is the only vendor
> >>> providing native high quality GPU drivers it seems good to have
> >>> "generic" framebuffer driver that will work on any hardware in the
> >>> first place and then GPU specific drivers with hardware acceleration
> >>> where available. This allows not only having graphics on anything, but
> >>> more importantly a fallback when GPU drivers fail / buggy /
> >>> unavailable. Anything here means not only Xorg (and similar) but also
> >>> raw console that can launch framebuffer applications or a mouse
> >>> pointer that can copy-paste in the raw console! :-) Console woks on
> >>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
> >>> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
> >>> This is modular and versatile design that allows text mode console on
> >>> video display, graphical applications in raw video console, and Xorg
> >>> or similar.
> >>>
> >>> There are two framebuffer drivers on FreeBSD:
> >>> 1. VESA (old / bios machines):
> >>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
> >>> 2. SCFB (new / usefi machines):
> >>> https://man.freebsd.org/cgi/man.cgi?query=scfb
> >>>
> >>> Therer are two console drivers on FreeBSD:
> >>> 1. SYSCONS/SC (old / bios machines):
> >>> https://man.freebsd.org/cgi/man.cgi?query=syscons
> >>> 2. VT (new / uefi machines):
> https://man.freebsd.org/cgi/man.cgi?query=vt
> >>>
> >>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
> >>> works). It seems work-in-progress but works for years already. The
> >>> only problem I saw so far is the console colors packed into two bit
> >>> field (afair) that may need structure changes to get dedicated 8..24
> >>> bit bit field to get more colors that will be breaking change thus it
> >>> may be good to think ahead and use this wider field if we want to do
> >>> something similar in NuttX :-)
> >>>
> >>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
> >>>
> >>> Hope this helps a bit or gives some reference point :-)
> >>>
> >>> On Linux ~20 years ago it was also possible to draw on raw video
> >>> framebuffer using DirectFB (now version 2) even with no Xorg, see
> >>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
> >>> a moving target and kind of PITA because FreeBSD followed that path to
> >>> have GPU drivers compatible with Linux for easier porting and this
> >>> only brings problems because things change constantly and are pain to
> >>> maintain / use thus I would recommend to avoid this path :-(
> >>>
> >>> I guess we care most about this design / approach where we have
> >>> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
> >>> or Xorg or similar (there is example Xorg compatible server in
> >>> NuttX!!) :-)
> >>>
> >>> --
> >>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>
>

Re: RPI 4B Roadmap

Posted by Tim Hardisty <ti...@gmail.com>.
Or was it a dos emulator; don’t remember!


> On 8 Nov 2025, at 15:03, Tim Hardisty <ti...@gmail.com> wrote:
> 
> Doom was the first and last “full graphics” I played I think. Doom feats after hours in the 1990’s maybe?
> 
> Bring back Commander Keen lol.
> 
> (Yes, have played it some times with Win3 emulators!)
> 
> Regards,
> 
> Tim.
> 
>> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
>> 
>>   *
>> Thanks again everyone for your help so far! One step closer to DOOM on
>> 
>> NuttX :)
>> 
>> Back in the old days when games were pure software, I enjoyed writing games for NuttX.  I have wolfenstein-like engine and an experimental 3D ray-casting engine.  These used to run on NuttX.  The latter was once a part of the apps/ repository but I removed it when I donated NuttX to Apache (since I didn't intend to donate that [art).  But I suppose it is still in the GIT history.
>> 
>> UNRELATED:  When NuttX was donated, there were a lot of files in the repository that should not have been released and were removed in this way.  Many other files with different licenses were present at the time of release and these had to be sanitized, to make them Apache correct (thanks almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2 copyrighted by the ASF, we really only the git repository from a certain point forward
>> 
>> Prior to that, checkouts from the repository are BSD licensed and copyrighted by me.
>> 
>> I also used to run the public 2-D Wolfenstein-like screen saver on NuttX.  It worked fine mostly out of the box.
>> 
>> ________________________________
>> From: Matteo Golin <ma...@gmail.com>
>> Sent: Friday, November 7, 2025 9:31 PM
>> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
>> Subject: Re: RPI 4B Roadmap
>> 
>> I managed to get something working with the frame buffer interface, so
>> success so far! https://github.com/apache/nuttx/pull/17294
>> 
>> Unfortunately, I encountered an issue trying to compile the LVGL demo so it
>> hasn't been much more interesting than some test rectangles so far.
>> https://github.com/apache/nuttx-apps/issues/3208
>> 
>> The frame-buffer driver was actually really simple to get working after
>> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for the
>> easy-to-implement driver)! I will probably go back and document the bit of
>> the frame buffer lower-half that I understand, since a little bit of
>> developer documentation for how to write a lower-half and what's exactly
>> needed to get running would be useful. There's also no docs for the
>> framebuffer example application, which I plan to fix shortly. It would be
>> good to know what the output should look like so I'm not scratching my head
>> wondering if I got it right or not :)
>> 
>> Thanks again everyone for your help so far! One step closer to DOOM on
>> NuttX :)
>> 
>> Matteo
>> 
>>>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:
>>> 
>>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
>>>> wrote:
>>>> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
>>>> author uses the framebuffer approach for graphics:
>>>> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
>>>> This is actually a really simple approach to implement, which is why I
>>>> imagine it wouldn't be difficult to integrate with NuttX's frame buffer
>>>> method of graphics. The main problem for me is that it's very slow. I
>>> want
>>>> to figure out how to leverage the actual GPU so that graphics can be
>>> faster
>>>> and more complex. I have not started looking extensively into that yet,
>>> but
>>>> was mainly wondering how that approach fits into NuttX's graphics system.
>>> 
>>> From the long years on FreeBSD desktop where nvidia is the only vendor
>>> providing native high quality GPU drivers it seems good to have
>>> "generic" framebuffer driver that will work on any hardware in the
>>> first place and then GPU specific drivers with hardware acceleration
>>> where available. This allows not only having graphics on anything, but
>>> more importantly a fallback when GPU drivers fail / buggy /
>>> unavailable. Anything here means not only Xorg (and similar) but also
>>> raw console that can launch framebuffer applications or a mouse
>>> pointer that can copy-paste in the raw console! :-) Console woks on
>>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
>>> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
>>> This is modular and versatile design that allows text mode console on
>>> video display, graphical applications in raw video console, and Xorg
>>> or similar.
>>> 
>>> There are two framebuffer drivers on FreeBSD:
>>> 1. VESA (old / bios machines):
>>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
>>> 2. SCFB (new / usefi machines):
>>> https://man.freebsd.org/cgi/man.cgi?query=scfb
>>> 
>>> Therer are two console drivers on FreeBSD:
>>> 1. SYSCONS/SC (old / bios machines):
>>> https://man.freebsd.org/cgi/man.cgi?query=syscons
>>> 2. VT (new / uefi machines): https://man.freebsd.org/cgi/man.cgi?query=vt
>>> 
>>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
>>> works). It seems work-in-progress but works for years already. The
>>> only problem I saw so far is the console colors packed into two bit
>>> field (afair) that may need structure changes to get dedicated 8..24
>>> bit bit field to get more colors that will be breaking change thus it
>>> may be good to think ahead and use this wider field if we want to do
>>> something similar in NuttX :-)
>>> 
>>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
>>> 
>>> Hope this helps a bit or gives some reference point :-)
>>> 
>>> On Linux ~20 years ago it was also possible to draw on raw video
>>> framebuffer using DirectFB (now version 2) even with no Xorg, see
>>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
>>> a moving target and kind of PITA because FreeBSD followed that path to
>>> have GPU drivers compatible with Linux for easier porting and this
>>> only brings problems because things change constantly and are pain to
>>> maintain / use thus I would recommend to avoid this path :-(
>>> 
>>> I guess we care most about this design / approach where we have
>>> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
>>> or Xorg or similar (there is example Xorg compatible server in
>>> NuttX!!) :-)
>>> 
>>> --
>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>> 

Re: RPI 4B Roadmap

Posted by Tim Hardisty <ti...@gmail.com>.
Doom was the first and last “full graphics” I played I think. Doom feats after hours in the 1990’s maybe?

Bring back Commander Keen lol.

(Yes, have played it some times with Win3 emulators!)

Regards,

Tim.

> On 8 Nov 2025, at 13:20, Gregory Nutt <sp...@gmail.com> wrote:
> 
>   *
> Thanks again everyone for your help so far! One step closer to DOOM on
> 
> NuttX :)
> 
> Back in the old days when games were pure software, I enjoyed writing games for NuttX.  I have wolfenstein-like engine and an experimental 3D ray-casting engine.  These used to run on NuttX.  The latter was once a part of the apps/ repository but I removed it when I donated NuttX to Apache (since I didn't intend to donate that [art).  But I suppose it is still in the GIT history.
> 
> UNRELATED:  When NuttX was donated, there were a lot of files in the repository that should not have been released and were removed in this way.  Many other files with different licenses were present at the time of release and these had to be sanitized, to make them Apache correct (thanks almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2 copyrighted by the ASF, we really only the git repository from a certain point forward
> 
> Prior to that, checkouts from the repository are BSD licensed and copyrighted by me.
> 
> I also used to run the public 2-D Wolfenstein-like screen saver on NuttX.  It worked fine mostly out of the box.
> 
> ________________________________
> From: Matteo Golin <ma...@gmail.com>
> Sent: Friday, November 7, 2025 9:31 PM
> To: dev@nuttx.apache.org <de...@nuttx.apache.org>
> Subject: Re: RPI 4B Roadmap
> 
> I managed to get something working with the frame buffer interface, so
> success so far! https://github.com/apache/nuttx/pull/17294
> 
> Unfortunately, I encountered an issue trying to compile the LVGL demo so it
> hasn't been much more interesting than some test rectangles so far.
> https://github.com/apache/nuttx-apps/issues/3208
> 
> The frame-buffer driver was actually really simple to get working after
> looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for the
> easy-to-implement driver)! I will probably go back and document the bit of
> the frame buffer lower-half that I understand, since a little bit of
> developer documentation for how to write a lower-half and what's exactly
> needed to get running would be useful. There's also no docs for the
> framebuffer example application, which I plan to fix shortly. It would be
> good to know what the output should look like so I'm not scratching my head
> wondering if I got it right or not :)
> 
> Thanks again everyone for your help so far! One step closer to DOOM on
> NuttX :)
> 
> Matteo
> 
>> On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:
>> 
>>> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
>>> wrote:
>>> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
>>> author uses the framebuffer approach for graphics:
>>> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
>>> This is actually a really simple approach to implement, which is why I
>>> imagine it wouldn't be difficult to integrate with NuttX's frame buffer
>>> method of graphics. The main problem for me is that it's very slow. I
>> want
>>> to figure out how to leverage the actual GPU so that graphics can be
>> faster
>>> and more complex. I have not started looking extensively into that yet,
>> but
>>> was mainly wondering how that approach fits into NuttX's graphics system.
>> 
>> From the long years on FreeBSD desktop where nvidia is the only vendor
>> providing native high quality GPU drivers it seems good to have
>> "generic" framebuffer driver that will work on any hardware in the
>> first place and then GPU specific drivers with hardware acceleration
>> where available. This allows not only having graphics on anything, but
>> more importantly a fallback when GPU drivers fail / buggy /
>> unavailable. Anything here means not only Xorg (and similar) but also
>> raw console that can launch framebuffer applications or a mouse
>> pointer that can copy-paste in the raw console! :-) Console woks on
>> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
>> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
>> This is modular and versatile design that allows text mode console on
>> video display, graphical applications in raw video console, and Xorg
>> or similar.
>> 
>> There are two framebuffer drivers on FreeBSD:
>> 1. VESA (old / bios machines):
>> https://man.freebsd.org/cgi/man.cgi?query=vesa.
>> 2. SCFB (new / usefi machines):
>> https://man.freebsd.org/cgi/man.cgi?query=scfb
>> 
>> Therer are two console drivers on FreeBSD:
>> 1. SYSCONS/SC (old / bios machines):
>> https://man.freebsd.org/cgi/man.cgi?query=syscons
>> 2. VT (new / uefi machines): https://man.freebsd.org/cgi/man.cgi?query=vt
>> 
>> SCFB / VT works also on embedded systems like rPI (over HDMI if that
>> works). It seems work-in-progress but works for years already. The
>> only problem I saw so far is the console colors packed into two bit
>> field (afair) that may need structure changes to get dedicated 8..24
>> bit bit field to get more colors that will be breaking change thus it
>> may be good to think ahead and use this wider field if we want to do
>> something similar in NuttX :-)
>> 
>> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
>> 
>> Hope this helps a bit or gives some reference point :-)
>> 
>> On Linux ~20 years ago it was also possible to draw on raw video
>> framebuffer using DirectFB (now version 2) even with no Xorg, see
>> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
>> a moving target and kind of PITA because FreeBSD followed that path to
>> have GPU drivers compatible with Linux for easier porting and this
>> only brings problems because things change constantly and are pain to
>> maintain / use thus I would recommend to avoid this path :-(
>> 
>> I guess we care most about this design / approach where we have
>> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
>> or Xorg or similar (there is example Xorg compatible server in
>> NuttX!!) :-)
>> 
>> --
>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>> 

Re: RPI 4B Roadmap

Posted by Gregory Nutt <sp...@gmail.com>.
  *
Thanks again everyone for your help so far! One step closer to DOOM on

NuttX :)

Back in the old days when games were pure software, I enjoyed writing games for NuttX.  I have wolfenstein-like engine and an experimental 3D ray-casting engine.  These used to run on NuttX.  The latter was once a part of the apps/ repository but I removed it when I donated NuttX to Apache (since I didn't intend to donate that [art).  But I suppose it is still in the GIT history.

UNRELATED:  When NuttX was donated, there were a lot of files in the repository that should not have been released and were removed in this way.  Many other files with different licenses were present at the time of release and these had to be sanitized, to make them Apache correct (thanks almost entirely to Alin Jerpelea).  When we talk about NuttX being Apache 2 copyrighted by the ASF, we really only the git repository from a certain point forward

Prior to that, checkouts from the repository are BSD licensed and copyrighted by me.

I also used to run the public 2-D Wolfenstein-like screen saver on NuttX.  It worked fine mostly out of the box.

________________________________
From: Matteo Golin <ma...@gmail.com>
Sent: Friday, November 7, 2025 9:31 PM
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: RPI 4B Roadmap

I managed to get something working with the frame buffer interface, so
success so far! https://github.com/apache/nuttx/pull/17294

Unfortunately, I encountered an issue trying to compile the LVGL demo so it
hasn't been much more interesting than some test rectangles so far.
https://github.com/apache/nuttx-apps/issues/3208

The frame-buffer driver was actually really simple to get working after
looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for the
easy-to-implement driver)! I will probably go back and document the bit of
the frame buffer lower-half that I understand, since a little bit of
developer documentation for how to write a lower-half and what's exactly
needed to get running would be useful. There's also no docs for the
framebuffer example application, which I plan to fix shortly. It would be
good to know what the output should look like so I'm not scratching my head
wondering if I got it right or not :)

Thanks again everyone for your help so far! One step closer to DOOM on
NuttX :)

Matteo

On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:

> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
> wrote:
> > 1) I am actually familiar with the rpi4-osdev project. In part 5, the
> > author uses the framebuffer approach for graphics:
> > https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> > This is actually a really simple approach to implement, which is why I
> > imagine it wouldn't be difficult to integrate with NuttX's frame buffer
> > method of graphics. The main problem for me is that it's very slow. I
> want
> > to figure out how to leverage the actual GPU so that graphics can be
> faster
> > and more complex. I have not started looking extensively into that yet,
> but
> > was mainly wondering how that approach fits into NuttX's graphics system.
>
> From the long years on FreeBSD desktop where nvidia is the only vendor
> providing native high quality GPU drivers it seems good to have
> "generic" framebuffer driver that will work on any hardware in the
> first place and then GPU specific drivers with hardware acceleration
> where available. This allows not only having graphics on anything, but
> more importantly a fallback when GPU drivers fail / buggy /
> unavailable. Anything here means not only Xorg (and similar) but also
> raw console that can launch framebuffer applications or a mouse
> pointer that can copy-paste in the raw console! :-) Console woks on
> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
> This is modular and versatile design that allows text mode console on
> video display, graphical applications in raw video console, and Xorg
> or similar.
>
> There are two framebuffer drivers on FreeBSD:
> 1. VESA (old / bios machines):
> https://man.freebsd.org/cgi/man.cgi?query=vesa.
> 2. SCFB (new / usefi machines):
> https://man.freebsd.org/cgi/man.cgi?query=scfb
>
> Therer are two console drivers on FreeBSD:
> 1. SYSCONS/SC (old / bios machines):
> https://man.freebsd.org/cgi/man.cgi?query=syscons
> 2. VT (new / uefi machines): https://man.freebsd.org/cgi/man.cgi?query=vt
>
> SCFB / VT works also on embedded systems like rPI (over HDMI if that
> works). It seems work-in-progress but works for years already. The
> only problem I saw so far is the console colors packed into two bit
> field (afair) that may need structure changes to get dedicated 8..24
> bit bit field to get more colors that will be breaking change thus it
> may be good to think ahead and use this wider field if we want to do
> something similar in NuttX :-)
>
> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
>
> Hope this helps a bit or gives some reference point :-)
>
> On Linux ~20 years ago it was also possible to draw on raw video
> framebuffer using DirectFB (now version 2) even with no Xorg, see
> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
> a moving target and kind of PITA because FreeBSD followed that path to
> have GPU drivers compatible with Linux for easier porting and this
> only brings problems because things change constantly and are pain to
> maintain / use thus I would recommend to avoid this path :-(
>
> I guess we care most about this design / approach where we have
> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
> or Xorg or similar (there is example Xorg compatible server in
> NuttX!!) :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: RPI 4B Roadmap

Posted by Matteo Golin <ma...@gmail.com>.
I managed to get something working with the frame buffer interface, so
success so far! https://github.com/apache/nuttx/pull/17294

Unfortunately, I encountered an issue trying to compile the LVGL demo so it
hasn't been much more interesting than some test rectangles so far.
https://github.com/apache/nuttx-apps/issues/3208

The frame-buffer driver was actually really simple to get working after
looking at Lup's blogs, so thank you for the tip Tomek (and Greg, for the
easy-to-implement driver)! I will probably go back and document the bit of
the frame buffer lower-half that I understand, since a little bit of
developer documentation for how to write a lower-half and what's exactly
needed to get running would be useful. There's also no docs for the
framebuffer example application, which I plan to fix shortly. It would be
good to know what the output should look like so I'm not scratching my head
wondering if I got it right or not :)

Thanks again everyone for your help so far! One step closer to DOOM on
NuttX :)

Matteo

On Thu, Nov 6, 2025 at 2:37 PM Tomek CEDRO <to...@cedro.info> wrote:

> On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com>
> wrote:
> > 1) I am actually familiar with the rpi4-osdev project. In part 5, the
> > author uses the framebuffer approach for graphics:
> > https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> > This is actually a really simple approach to implement, which is why I
> > imagine it wouldn't be difficult to integrate with NuttX's frame buffer
> > method of graphics. The main problem for me is that it's very slow. I
> want
> > to figure out how to leverage the actual GPU so that graphics can be
> faster
> > and more complex. I have not started looking extensively into that yet,
> but
> > was mainly wondering how that approach fits into NuttX's graphics system.
>
> From the long years on FreeBSD desktop where nvidia is the only vendor
> providing native high quality GPU drivers it seems good to have
> "generic" framebuffer driver that will work on any hardware in the
> first place and then GPU specific drivers with hardware acceleration
> where available. This allows not only having graphics on anything, but
> more importantly a fallback when GPU drivers fail / buggy /
> unavailable. Anything here means not only Xorg (and similar) but also
> raw console that can launch framebuffer applications or a mouse
> pointer that can copy-paste in the raw console! :-) Console woks on
> top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
> top of the framebuffer (when launched it goes to place of /dev/ttyv8).
> This is modular and versatile design that allows text mode console on
> video display, graphical applications in raw video console, and Xorg
> or similar.
>
> There are two framebuffer drivers on FreeBSD:
> 1. VESA (old / bios machines):
> https://man.freebsd.org/cgi/man.cgi?query=vesa.
> 2. SCFB (new / usefi machines):
> https://man.freebsd.org/cgi/man.cgi?query=scfb
>
> Therer are two console drivers on FreeBSD:
> 1. SYSCONS/SC (old / bios machines):
> https://man.freebsd.org/cgi/man.cgi?query=syscons
> 2. VT (new / uefi machines): https://man.freebsd.org/cgi/man.cgi?query=vt
>
> SCFB / VT works also on embedded systems like rPI (over HDMI if that
> works). It seems work-in-progress but works for years already. The
> only problem I saw so far is the console colors packed into two bit
> field (afair) that may need structure changes to get dedicated 8..24
> bit bit field to get more colors that will be breaking change thus it
> may be good to think ahead and use this wider field if we want to do
> something similar in NuttX :-)
>
> Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons
>
> Hope this helps a bit or gives some reference point :-)
>
> On Linux ~20 years ago it was also possible to draw on raw video
> framebuffer using DirectFB (now version 2) even with no Xorg, see
> https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
> a moving target and kind of PITA because FreeBSD followed that path to
> have GPU drivers compatible with Linux for easier porting and this
> only brings problems because things change constantly and are pain to
> maintain / use thus I would recommend to avoid this path :-(
>
> I guess we care most about this design / approach where we have
> FrameBuffer that allows drawing directly (i.e. LVGL), having console,
> or Xorg or similar (there is example Xorg compatible server in
> NuttX!!) :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: RPI 4B Roadmap

Posted by Tomek CEDRO <to...@cedro.info>.
On Thu, Nov 6, 2025 at 5:53 PM Matteo Golin <ma...@gmail.com> wrote:
> 1) I am actually familiar with the rpi4-osdev project. In part 5, the
> author uses the framebuffer approach for graphics:
> https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
> This is actually a really simple approach to implement, which is why I
> imagine it wouldn't be difficult to integrate with NuttX's frame buffer
> method of graphics. The main problem for me is that it's very slow. I want
> to figure out how to leverage the actual GPU so that graphics can be faster
> and more complex. I have not started looking extensively into that yet, but
> was mainly wondering how that approach fits into NuttX's graphics system.

From the long years on FreeBSD desktop where nvidia is the only vendor
providing native high quality GPU drivers it seems good to have
"generic" framebuffer driver that will work on any hardware in the
first place and then GPU specific drivers with hardware acceleration
where available. This allows not only having graphics on anything, but
more importantly a fallback when GPU drivers fail / buggy /
unavailable. Anything here means not only Xorg (and similar) but also
raw console that can launch framebuffer applications or a mouse
pointer that can copy-paste in the raw console! :-) Console woks on
top of the video framebuffer (i.e. /dev/ttyv0..7), Xorg also works on
top of the framebuffer (when launched it goes to place of /dev/ttyv8).
This is modular and versatile design that allows text mode console on
video display, graphical applications in raw video console, and Xorg
or similar.

There are two framebuffer drivers on FreeBSD:
1. VESA (old / bios machines): https://man.freebsd.org/cgi/man.cgi?query=vesa.
2. SCFB (new / usefi machines): https://man.freebsd.org/cgi/man.cgi?query=scfb

Therer are two console drivers on FreeBSD:
1. SYSCONS/SC (old / bios machines):
https://man.freebsd.org/cgi/man.cgi?query=syscons
2. VT (new / uefi machines): https://man.freebsd.org/cgi/man.cgi?query=vt

SCFB / VT works also on embedded systems like rPI (over HDMI if that
works). It seems work-in-progress but works for years already. The
only problem I saw so far is the console colors packed into two bit
field (afair) that may need structure changes to get dedicated 8..24
bit bit field to get more colors that will be breaking change thus it
may be good to think ahead and use this wider field if we want to do
something similar in NuttX :-)

Here is newcons / vt wiki: https://wiki.freebsd.org/Newcons

Hope this helps a bit or gives some reference point :-)

On Linux ~20 years ago it was also possible to draw on raw video
framebuffer using DirectFB (now version 2) even with no Xorg, see
https://en.wikipedia.org/wiki/DirectFB :-) Current DRM/KMS approach is
a moving target and kind of PITA because FreeBSD followed that path to
have GPU drivers compatible with Linux for easier porting and this
only brings problems because things change constantly and are pain to
maintain / use thus I would recommend to avoid this path :-(

I guess we care most about this design / approach where we have
FrameBuffer that allows drawing directly (i.e. LVGL), having console,
or Xorg or similar (there is example Xorg compatible server in
NuttX!!) :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: RPI 4B Roadmap

Posted by Matteo Golin <ma...@gmail.com>.
Hello everyone,

Thank you for the responses of support! I will try to address them
one-by-one.

1) I am actually familiar with the rpi4-osdev project. In part 5, the
author uses the framebuffer approach for graphics:
https://github.com/babbleberry/rpi4-osdev/tree/master/part5-framebuffer.
This is actually a really simple approach to implement, which is why I
imagine it wouldn't be difficult to integrate with NuttX's frame buffer
method of graphics. The main problem for me is that it's very slow. I want
to figure out how to leverage the actual GPU so that graphics can be faster
and more complex. I have not started looking extensively into that yet, but
was mainly wondering how that approach fits into NuttX's graphics system.

2) I will look through Lup's blog! I'd imagine the Pinephone has one of the
more complex graphics outputs of what's on NuttX. Thanks for the tip!

3) I was kind of afraid that the existing NuttX support is limited to
framebuffers/low complexity graphics in its current state. It is an RTOS
after all, and runs mainly on low-resource systems. It seems that is the
case from some of the responses here.

I may spend some time reading Lup's blog and the framebuffer documentation
for NuttX. I'm starting to think that a simple framebuffer driver would be
a good initial approach to this as a proof-of-concept.

Thanks again everyone,
Matteo

On Thu, Nov 6, 2025 at 6:15 AM Tim Hardisty <ti...@gmail.com> wrote:

> Just some semi-random thoughts to throw in here.
>
> I use a SAMA5D27 with a 164MHz main clock and with an 800x480 lcd using
> ARGB8888 with lvgl via NuttX framebuffer and complex gauge graphics I get
> <10 bps.
>
> Only just started my investigation into this but I think the NuttX + lvgl
> FB approach is flawed as it uses 2 full frame render buffers and then
> copies one to the framebuffer when ready. Only takes 3 ms but it is
> inefficient and would be better done by the NuttX/arch driver flipping DMA
> buffers.
>
> Might be other things at play but I’m not yet sure if the FB will handle
> advanced lvgl graphics as it is at the moment.
>
> Regards,
>
> Tim.
>
> > On 5 Nov 2025, at 22:49, Matteo Golin <ma...@gmail.com> wrote:
> >
> > Hi all,
> >
> > Despite a relatively small bug with transfer size limits, the RPi4B
> microSD
> > card support is basically done. This is largely in part to how simple it
> is
> > on NuttX to write a lower-half SDIO implementation and have things just
> > work, which is incredible :)
> >
> > I now (ambitiously) want to set my eyes on graphics. It turns out that
> > rendering with a framebuffer is actually quite easy, but very CPU
> > intensive. I'm going to need to figure out how to get at the GPU
> properly. *My
> > question is: *is anyone familiar with examples on how to implement the
> > necessary "lower-half" for the NuttX graphics library? I.e. what
> > functions/drivers I would need to get written to allow the basic
> windowing
> > display manager & LVGL to work on the HDMI outputs of the Pi? I have
> > briefly read the docs about the window manager and saw that there is a
> > framebuffer char driver that can be implemented, but I'm not sure how
> well
> > that scales to decent graphics. I suppose this is relatively uncharted
> > territory on an RTOS designed mainly with LCDs in mind as the only
> graphics
> > (?). If anyone has implemented graphics support for a device before and
> can
> > let me know a few source files to look at, that would be great!
> >
> > My main goal is essentially to get decently fast graphics going, since
> once
> > that's done and some USB HID device support is set up, I can port DOOM to
> > NuttX :)
> >
> > Thanks,
> > Matteo
> >
> >> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
> >> wrote:
> >>
> >> Thanks Tomek! That would be a good resource.
> >>
> >>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
> >>>
> >>> OpenBSD 7.8 has been just released and it has official support for rPI
> >>> 5 with all sorts of peripherals.. maybe this is the new source to look
> >>> for drivers code? :-)
> >>>
> >>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
> >>>
> >>> https://cvsweb.openbsd.org/src/
> >>>
> >>> Have a good day :-)
> >>> Tomek
> >>>
> >>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
> >>> wrote:
> >>>>
> >>>> Thanks Alan! Maybe I will reach out to Arasan, could have more luck
> than
> >>>> with Broadcom, but I doubt it.
> >>>>
> >>>> I'll take a look at these documents!
> >>>>
> >>>> Thanks again,
> >>>> Matteo
> >>>>
> >>>> On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com>
> wrote:
> >>>>
> >>>>> Hi Matteo,
> >>>>>
> >>>>> Please that a look:
> >>>>> https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
> >>>>>
> >>>>> There is an option to Download (request) the Datasheet from that
> >>> page, but
> >>>>> you can access it directly here:
> >>>>>
> >>>>>
> >>>
> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
> >>>>>
> >>>>> This document is more about the IP core details, but could give you
> >>> more
> >>>>> understanding about internal block of the SDIO controller (its FIFO,
> >>>>> initialization diagram, etc)
> >>>>>
> >>>>> You can also try to find the original
> >>>>> SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
> >>> Raspberry
> >>>>> documentation.
> >>>>>
> >>>>> BR,
> >>>>>
> >>>>> Alan
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <
> matteo.golin@gmail.com
> >>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi Alan,
> >>>>>>
> >>>>>> Thank you for the tips! Yes, SDIO looks pretty involved compared to
> >>> SPI
> >>>>> or
> >>>>>> I2C. I'll try reading the specification like you suggested.
> >>>>>>
> >>>>>> The BCM2711 datasheet doesn't document it at all, however the EMMC
> >>>>>> interface is supposedly the exact same from the BCM2835 and the
> >>> registers
> >>>>>> there are at least documented. All I know is that it is using an
> >>>>> interface
> >>>>>> by Arasan. I'm not as familiar with NuttX, but if this at all looks
> >>> like
> >>>>>> something that's already been supported, please let me know. In the
> >>>>>> meantime, I'll look through the SDIO implementations to check:
> >>>>>>
> >>>>>
> >>>
> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
> >>>>>> (page 65)
> >>>>>>
> >>>>>> Thanks again!
> >>>>>> Matteo
> >>>>>>
> >>>>>> On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
> >>> wrote:
> >>>>>>
> >>>>>>> HI Matteo,
> >>>>>>>
> >>>>>>> I implemented the SDIO support for LPC43 some years ago and what
> >>> helped
> >>>>>> me
> >>>>>>> most was reading the SD/MMC specification, the LPC43 reference
> >>> manual
> >>>>> and
> >>>>>>> enabling the NuttX SD/MMC debug messages.
> >>>>>>>
> >>>>>>> There are many details to take care of: clock enable for the
> >>>>> controller,
> >>>>>>> interrupts, pins configuration, etc.
> >>>>>>>
> >>>>>>> Unfortunately, the BCM2711 doc is not good. You can start
> >>> verifying the
> >>>>>>> registers, maybe it is based on some SD/MMC core IP already
> >>> supported
> >>>>> by
> >>>>>>> NuttX.
> >>>>>>>
> >>>>>>> BR,
> >>>>>>>
> >>>>>>> Alan
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
> >>> matteo.golin@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi everyone,
> >>>>>>>>
> >>>>>>>> Now that I2C has been tackled, I am moving on to SDIO
> >>> interfaces so
> >>>>> the
> >>>>>>> SD
> >>>>>>>> card can be interacted with from NuttX.
> >>>>>>>>
> >>>>>>>> The NuttX SDIO documentation is a little bare, and I'm not the
> >>> most
> >>>>>>>> familiar with SDIO. Does anyone have any recommendations for
> >>>>>>>> implementations to look at (besides the STM32 one that is
> >>> linked in
> >>>>> the
> >>>>>>>> docs), resources to read (any blog posts from when you ported
> >>> SDIO)
> >>>>> or
> >>>>>>>> advice in general? It would be much appreciated.
> >>>>>>>>
> >>>>>>>> Thank you,
> >>>>>>>> Matteo
> >>>>>>>>
> >>>>>>>> On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
> >>> matteo.golin@gmail.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Got another response from my earlier request to Raspberry Pi
> >>>>> through
> >>>>>>>> their
> >>>>>>>>> website:
> >>>>>>>>>
> >>>>>>>>> Hi Matteo
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Thanks for getting in touch. We don't actually have any more
> >>>>>>>>>> documentation that we can release on this. My usual
> >>> recommendation
> >>>>>> is
> >>>>>>>> for
> >>>>>>>>>> SW people to take a look at the Linux drivers to get a closer
> >>>>>>>> understanding
> >>>>>>>>>> of how the HW works. Not ideal, but the best I can offer.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> So I guess everyone is telling us the same thing!
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <to...@cedro.info>
> >>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Sure! Public now :-)
> >>>>>>>>>> Tomek
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
> >>>>> matteo.golin@gmail.com
> >>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>> I have populated the RPi 4B project with some starting
> >>> issues to
> >>>>>>>> tackle
> >>>>>>>>>> for
> >>>>>>>>>>> the 4B implementation. I see that the project is marked as
> >>>>>> private;
> >>>>>>> is
> >>>>>>>>>>> there any way to make it visible to potential contributors
> >>> just
> >>>>>>>> visiting
> >>>>>>>>>>> the GitHub page? I think if they can see a list of issues
> >>> in one
> >>>>>>> place
> >>>>>>>>>> when
> >>>>>>>>>>> they go to the page it might help.
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Matteo
> >>>>>>>>>>>
> >>>>>>>>>>> On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
> >>> tomek@cedro.info>
> >>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Thank you Linguini, good luck and have fun! :-)
> >>>>>>>>>>>> Tomek
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
> >>>>>>> matteo.golin@gmail.com
> >>>>>>>>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To update the community, we've been told by Gordon
> >>> that the
> >>>>> Pi
> >>>>>>>>>> Foundation
> >>>>>>>>>>>>> doesn't have any documentation for the chip beyond
> >>> what was
> >>>>>>>> written
> >>>>>>>>>> in
> >>>>>>>>>>>> the
> >>>>>>>>>>>>> peripheral datasheet. Broadcom themselves has written
> >>> the
> >>>>>> Linux
> >>>>>>>>>> drivers
> >>>>>>>>>>>> and
> >>>>>>>>>>>>> Raspberry Pi has only made some slight bug fixes, etc.
> >>> We've
> >>>>>>> been
> >>>>>>>>>>>> suggested
> >>>>>>>>>>>>> to read the source to discover undocumented
> >>>>>>>> registers/configuration
> >>>>>>>>>>>> options.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I plan to still continue with the port until the
> >>> feature set
> >>>>>> on
> >>>>>>>>>> NuttX is
> >>>>>>>>>>>>> equal or greater to what is available on QNX. I at
> >>> least
> >>>>> want
> >>>>>> to
> >>>>>>>> get
> >>>>>>>>>>>>> Ethernet and some graphics running after the base
> >>> peripheral
> >>>>>> set
> >>>>>>>>>> (I2C,
> >>>>>>>>>>>> SPI,
> >>>>>>>>>>>>> UART) are supported.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Matteo
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
> >>>>>>>>>> matteo.golin@gmail.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Very interesting Sebastian. I got that impression
> >>> from
> >>>>>>> Broadcom
> >>>>>>>>>> when I
> >>>>>>>>>>>> was
> >>>>>>>>>>>>>> initially trying to port NuttX to the Pi. The
> >>> inability to
> >>>>>>>> submit
> >>>>>>>>>>>> forms on
> >>>>>>>>>>>>>> their website seems like it might be by design...
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm hopeful the Raspberry Pi Foundation will have
> >>>>> something
> >>>>>>> more
> >>>>>>>>>> for
> >>>>>>>>>>>> us to
> >>>>>>>>>>>>>> work with, they seem more positive to FOSS.
> >>> Otherwise I
> >>>>> will
> >>>>>>>> still
> >>>>>>>>>>>> continue
> >>>>>>>>>>>>>> with reverse engineering until at least the point
> >>> where
> >>>>> the
> >>>>>>>>>>>> functionality
> >>>>>>>>>>>>>> driver-wise is on par with QNX.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
> >>>>>> tomek@cedro.info>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> James Dougherty contacted us with Gordon
> >>> Hollingworth
> >>>>> from
> >>>>>>>>>> Raspberry
> >>>>>>>>>>>>>>> Pi Foundation recently :-) We are waiting for
> >>> response
> >>>>> :-)
> >>>>>> I
> >>>>>>>>>> really
> >>>>>>>>>>>>>>> hope we can get some sort of documentation and/or
> >>> code
> >>>>>>> samples
> >>>>>>>> to
> >>>>>>>>>>>>>>> write high quality NuttX port for the big
> >>> raspberries :-)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Open-Source matters even more in this crazy world.
> >>> Thanks
> >>>>>> for
> >>>>>>>>>>>>>>> interesting article Sebastien! Personally I think we
> >>>>> should
> >>>>>>>>>> focus only
> >>>>>>>>>>>>>>> on vendors that support Open-Source. What is the
> >>> reason
> >>>>> for
> >>>>>>>>>> bumping
> >>>>>>>>>>>>>>> sales for companies that in the end can sue you for
> >>>>>>> reversing?
> >>>>>>>> :D
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Have a good day folks :-)
> >>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 10:15 AM Sebastien Lorquet <
> >>>>>>>>>>>> sebastien@lorquet.fr>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I just found this interesting document:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> In a summary, if you expect anything cool from
> >>>>> broadcom:
> >>>>>>>> dont.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> go go go reverse engineering!
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Sebastien
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On 8/29/25 15:37, Tomek CEDRO wrote:
> >>>>>>>>>>>>>>>>> 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
> >>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>> I just asked question at #asfinfra / slack,
> >>> maybe
> >>>>>>> someone
> >>>>>>>>>> can
> >>>>>>>>>>>> help
> >>>>>>>>>>>>>>>>>> there or recommend someone who can, waiting for
> >>>>>> response
> >>>>>>>> :-)
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> For a good start you can contact Broadcom and
> >>>>>>> RaspberryPi
> >>>>>>>>>>>> Foundation,
> >>>>>>>>>>>>>>>>>> introduce yourself as Apache NuttX RTOS
> >>> developer
> >>>>> that
> >>>>>>>> want
> >>>>>>>>>> to
> >>>>>>>>>>>> port
> >>>>>>>>>>>>>>>>>> NuttX to rPI boards, and just ask if
> >>> DataSheets are
> >>>>>>>>>> available
> >>>>>>>>>>>> :-) We
> >>>>>>>>>>>>>>>>>> will know then first hand if this is possible
> >>> or are
> >>>>>>> there
> >>>>>>>>>> any
> >>>>>>>>>>>>>>>>>> problems / requirements :-)
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> You can ask for 4B and probably Zero-2W SoC
> >>>>>>> documentation
> >>>>>>>>>> these
> >>>>>>>>>>>> seems
> >>>>>>>>>>>>>>>>>> most popular nowadays :-)
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Thanks :-)
> >>>>>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin <
> >>>>>>>>>>>> matteo.golin@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 <
> >>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
> >>> Golin <
> >>>>>>>>>>>>>>> matteo.golin@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
> >>>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>>
> >>>
> >>> --
> >>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>
> >>
>

Re: RPI 4B Roadmap

Posted by Tim Hardisty <ti...@gmail.com>.
Just some semi-random thoughts to throw in here.

I use a SAMA5D27 with a 164MHz main clock and with an 800x480 lcd using ARGB8888 with lvgl via NuttX framebuffer and complex gauge graphics I get  <10 bps.

Only just started my investigation into this but I think the NuttX + lvgl FB approach is flawed as it uses 2 full frame render buffers and then copies one to the framebuffer when ready. Only takes 3 ms but it is inefficient and would be better done by the NuttX/arch driver flipping DMA buffers.

Might be other things at play but I’m not yet sure if the FB will handle advanced lvgl graphics as it is at the moment.

Regards,

Tim.

> On 5 Nov 2025, at 22:49, Matteo Golin <ma...@gmail.com> wrote:
> 
> Hi all,
> 
> Despite a relatively small bug with transfer size limits, the RPi4B microSD
> card support is basically done. This is largely in part to how simple it is
> on NuttX to write a lower-half SDIO implementation and have things just
> work, which is incredible :)
> 
> I now (ambitiously) want to set my eyes on graphics. It turns out that
> rendering with a framebuffer is actually quite easy, but very CPU
> intensive. I'm going to need to figure out how to get at the GPU properly. *My
> question is: *is anyone familiar with examples on how to implement the
> necessary "lower-half" for the NuttX graphics library? I.e. what
> functions/drivers I would need to get written to allow the basic windowing
> display manager & LVGL to work on the HDMI outputs of the Pi? I have
> briefly read the docs about the window manager and saw that there is a
> framebuffer char driver that can be implemented, but I'm not sure how well
> that scales to decent graphics. I suppose this is relatively uncharted
> territory on an RTOS designed mainly with LCDs in mind as the only graphics
> (?). If anyone has implemented graphics support for a device before and can
> let me know a few source files to look at, that would be great!
> 
> My main goal is essentially to get decently fast graphics going, since once
> that's done and some USB HID device support is set up, I can port DOOM to
> NuttX :)
> 
> Thanks,
> Matteo
> 
>> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
>> wrote:
>> 
>> Thanks Tomek! That would be a good resource.
>> 
>>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
>>> 
>>> OpenBSD 7.8 has been just released and it has official support for rPI
>>> 5 with all sorts of peripherals.. maybe this is the new source to look
>>> for drivers code? :-)
>>> 
>>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
>>> 
>>> https://cvsweb.openbsd.org/src/
>>> 
>>> Have a good day :-)
>>> Tomek
>>> 
>>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
>>> wrote:
>>>> 
>>>> Thanks Alan! Maybe I will reach out to Arasan, could have more luck than
>>>> with Broadcom, but I doubt it.
>>>> 
>>>> I'll take a look at these documents!
>>>> 
>>>> Thanks again,
>>>> Matteo
>>>> 
>>>> On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com> wrote:
>>>> 
>>>>> Hi Matteo,
>>>>> 
>>>>> Please that a look:
>>>>> https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
>>>>> 
>>>>> There is an option to Download (request) the Datasheet from that
>>> page, but
>>>>> you can access it directly here:
>>>>> 
>>>>> 
>>> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
>>>>> 
>>>>> This document is more about the IP core details, but could give you
>>> more
>>>>> understanding about internal block of the SDIO controller (its FIFO,
>>>>> initialization diagram, etc)
>>>>> 
>>>>> You can also try to find the original
>>>>> SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
>>> Raspberry
>>>>> documentation.
>>>>> 
>>>>> BR,
>>>>> 
>>>>> Alan
>>>>> 
>>>>> 
>>>>> 
>>>>> On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <matteo.golin@gmail.com
>>>> 
>>>>> wrote:
>>>>> 
>>>>>> Hi Alan,
>>>>>> 
>>>>>> Thank you for the tips! Yes, SDIO looks pretty involved compared to
>>> SPI
>>>>> or
>>>>>> I2C. I'll try reading the specification like you suggested.
>>>>>> 
>>>>>> The BCM2711 datasheet doesn't document it at all, however the EMMC
>>>>>> interface is supposedly the exact same from the BCM2835 and the
>>> registers
>>>>>> there are at least documented. All I know is that it is using an
>>>>> interface
>>>>>> by Arasan. I'm not as familiar with NuttX, but if this at all looks
>>> like
>>>>>> something that's already been supported, please let me know. In the
>>>>>> meantime, I'll look through the SDIO implementations to check:
>>>>>> 
>>>>> 
>>> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
>>>>>> (page 65)
>>>>>> 
>>>>>> Thanks again!
>>>>>> Matteo
>>>>>> 
>>>>>> On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
>>> wrote:
>>>>>> 
>>>>>>> HI Matteo,
>>>>>>> 
>>>>>>> I implemented the SDIO support for LPC43 some years ago and what
>>> helped
>>>>>> me
>>>>>>> most was reading the SD/MMC specification, the LPC43 reference
>>> manual
>>>>> and
>>>>>>> enabling the NuttX SD/MMC debug messages.
>>>>>>> 
>>>>>>> There are many details to take care of: clock enable for the
>>>>> controller,
>>>>>>> interrupts, pins configuration, etc.
>>>>>>> 
>>>>>>> Unfortunately, the BCM2711 doc is not good. You can start
>>> verifying the
>>>>>>> registers, maybe it is based on some SD/MMC core IP already
>>> supported
>>>>> by
>>>>>>> NuttX.
>>>>>>> 
>>>>>>> BR,
>>>>>>> 
>>>>>>> Alan
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
>>> matteo.golin@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Hi everyone,
>>>>>>>> 
>>>>>>>> Now that I2C has been tackled, I am moving on to SDIO
>>> interfaces so
>>>>> the
>>>>>>> SD
>>>>>>>> card can be interacted with from NuttX.
>>>>>>>> 
>>>>>>>> The NuttX SDIO documentation is a little bare, and I'm not the
>>> most
>>>>>>>> familiar with SDIO. Does anyone have any recommendations for
>>>>>>>> implementations to look at (besides the STM32 one that is
>>> linked in
>>>>> the
>>>>>>>> docs), resources to read (any blog posts from when you ported
>>> SDIO)
>>>>> or
>>>>>>>> advice in general? It would be much appreciated.
>>>>>>>> 
>>>>>>>> Thank you,
>>>>>>>> Matteo
>>>>>>>> 
>>>>>>>> On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
>>> matteo.golin@gmail.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Got another response from my earlier request to Raspberry Pi
>>>>> through
>>>>>>>> their
>>>>>>>>> website:
>>>>>>>>> 
>>>>>>>>> Hi Matteo
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Thanks for getting in touch. We don't actually have any more
>>>>>>>>>> documentation that we can release on this. My usual
>>> recommendation
>>>>>> is
>>>>>>>> for
>>>>>>>>>> SW people to take a look at the Linux drivers to get a closer
>>>>>>>> understanding
>>>>>>>>>> of how the HW works. Not ideal, but the best I can offer.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> So I guess everyone is telling us the same thing!
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <to...@cedro.info>
>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Sure! Public now :-)
>>>>>>>>>> Tomek
>>>>>>>>>> 
>>>>>>>>>> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
>>>>> matteo.golin@gmail.com
>>>>>>> 
>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I have populated the RPi 4B project with some starting
>>> issues to
>>>>>>>> tackle
>>>>>>>>>> for
>>>>>>>>>>> the 4B implementation. I see that the project is marked as
>>>>>> private;
>>>>>>> is
>>>>>>>>>>> there any way to make it visible to potential contributors
>>> just
>>>>>>>> visiting
>>>>>>>>>>> the GitHub page? I think if they can see a list of issues
>>> in one
>>>>>>> place
>>>>>>>>>> when
>>>>>>>>>>> they go to the page it might help.
>>>>>>>>>>> 
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Matteo
>>>>>>>>>>> 
>>>>>>>>>>> On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
>>> tomek@cedro.info>
>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> Thank you Linguini, good luck and have fun! :-)
>>>>>>>>>>>> Tomek
>>>>>>>>>>>> 
>>>>>>>>>>>> On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
>>>>>>> matteo.golin@gmail.com
>>>>>>>>> 
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> To update the community, we've been told by Gordon
>>> that the
>>>>> Pi
>>>>>>>>>> Foundation
>>>>>>>>>>>>> doesn't have any documentation for the chip beyond
>>> what was
>>>>>>>> written
>>>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>>> peripheral datasheet. Broadcom themselves has written
>>> the
>>>>>> Linux
>>>>>>>>>> drivers
>>>>>>>>>>>> and
>>>>>>>>>>>>> Raspberry Pi has only made some slight bug fixes, etc.
>>> We've
>>>>>>> been
>>>>>>>>>>>> suggested
>>>>>>>>>>>>> to read the source to discover undocumented
>>>>>>>> registers/configuration
>>>>>>>>>>>> options.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I plan to still continue with the port until the
>>> feature set
>>>>>> on
>>>>>>>>>> NuttX is
>>>>>>>>>>>>> equal or greater to what is available on QNX. I at
>>> least
>>>>> want
>>>>>> to
>>>>>>>> get
>>>>>>>>>>>>> Ethernet and some graphics running after the base
>>> peripheral
>>>>>> set
>>>>>>>>>> (I2C,
>>>>>>>>>>>> SPI,
>>>>>>>>>>>>> UART) are supported.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Matteo
>>>>>>>>>>>>> 
>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
>>>>>>>>>> matteo.golin@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Very interesting Sebastian. I got that impression
>>> from
>>>>>>> Broadcom
>>>>>>>>>> when I
>>>>>>>>>>>> was
>>>>>>>>>>>>>> initially trying to port NuttX to the Pi. The
>>> inability to
>>>>>>>> submit
>>>>>>>>>>>> forms on
>>>>>>>>>>>>>> their website seems like it might be by design...
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I'm hopeful the Raspberry Pi Foundation will have
>>>>> something
>>>>>>> more
>>>>>>>>>> for
>>>>>>>>>>>> us to
>>>>>>>>>>>>>> work with, they seem more positive to FOSS.
>>> Otherwise I
>>>>> will
>>>>>>>> still
>>>>>>>>>>>> continue
>>>>>>>>>>>>>> with reverse engineering until at least the point
>>> where
>>>>> the
>>>>>>>>>>>> functionality
>>>>>>>>>>>>>> driver-wise is on par with QNX.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
>>>>>> tomek@cedro.info>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> James Dougherty contacted us with Gordon
>>> Hollingworth
>>>>> from
>>>>>>>>>> Raspberry
>>>>>>>>>>>>>>> Pi Foundation recently :-) We are waiting for
>>> response
>>>>> :-)
>>>>>> I
>>>>>>>>>> really
>>>>>>>>>>>>>>> hope we can get some sort of documentation and/or
>>> code
>>>>>>> samples
>>>>>>>> to
>>>>>>>>>>>>>>> write high quality NuttX port for the big
>>> raspberries :-)
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Open-Source matters even more in this crazy world.
>>> Thanks
>>>>>> for
>>>>>>>>>>>>>>> interesting article Sebastien! Personally I think we
>>>>> should
>>>>>>>>>> focus only
>>>>>>>>>>>>>>> on vendors that support Open-Source. What is the
>>> reason
>>>>> for
>>>>>>>>>> bumping
>>>>>>>>>>>>>>> sales for companies that in the end can sue you for
>>>>>>> reversing?
>>>>>>>> :D
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Have a good day folks :-)
>>>>>>>>>>>>>>> Tomek
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 10:15 AM Sebastien Lorquet <
>>>>>>>>>>>> sebastien@lorquet.fr>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I just found this interesting document:
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> In a summary, if you expect anything cool from
>>>>> broadcom:
>>>>>>>> dont.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> go go go reverse engineering!
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Sebastien
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> On 8/29/25 15:37, Tomek CEDRO wrote:
>>>>>>>>>>>>>>>>> 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
>>>>>>>>>> tomek@cedro.info>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>> I just asked question at #asfinfra / slack,
>>> maybe
>>>>>>> someone
>>>>>>>>>> can
>>>>>>>>>>>> help
>>>>>>>>>>>>>>>>>> there or recommend someone who can, waiting for
>>>>>> response
>>>>>>>> :-)
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> For a good start you can contact Broadcom and
>>>>>>> RaspberryPi
>>>>>>>>>>>> Foundation,
>>>>>>>>>>>>>>>>>> introduce yourself as Apache NuttX RTOS
>>> developer
>>>>> that
>>>>>>>> want
>>>>>>>>>> to
>>>>>>>>>>>> port
>>>>>>>>>>>>>>>>>> NuttX to rPI boards, and just ask if
>>> DataSheets are
>>>>>>>>>> available
>>>>>>>>>>>> :-) We
>>>>>>>>>>>>>>>>>> will know then first hand if this is possible
>>> or are
>>>>>>> there
>>>>>>>>>> any
>>>>>>>>>>>>>>>>>> problems / requirements :-)
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> You can ask for 4B and probably Zero-2W SoC
>>>>>>> documentation
>>>>>>>>>> these
>>>>>>>>>>>> seems
>>>>>>>>>>>>>>>>>> most popular nowadays :-)
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Thanks :-)
>>>>>>>>>>>>>>>>>> Tomek
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin <
>>>>>>>>>>>> matteo.golin@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 <
>>>>>>>>>> tomek@cedro.info>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
>>> Golin <
>>>>>>>>>>>>>>> matteo.golin@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
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> --
>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> --
>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>>> 
>>> --
>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>> 
>> 

Re: RPI 4B Roadmap

Posted by Gregory Nutt <sp...@gmail.com>.
I haven't looked at that change.  In order to use LVGL in a windowed system, I think you need to have a RAM-backed frame buffer driver so that each window can be updated independently.  That is no a difficult job, RAM-backed window framebuffers are already supported.
________________________________
From: Xiang Xiao <xi...@gmail.com>
Sent: Wednesday, November 5, 2025 9:19 PM
To: dev@nuttx.apache.org <de...@nuttx.apache.org>
Subject: Re: RPI 4B Roadmap

LVGL supports multiple instances with
https://github.com/lvgl/lvgl/issues/4358.
So, the windowing system can reuse LVGL as a widget library inside a window
just like NxWidget,
 but has more user-friendly touch expression.

On Thu, Nov 6, 2025 at 10:28 AM Gregory Nutt <sp...@gmail.com> wrote:

> The most critical thing is the architecture of the graphics subsystem,
> not any particular framebuffer driver.  We should discuss and settle on
> a clean, modular architecture before getting ahead of ourselves.
>
> A simple 2D graphics system can be implemented with only a framebuffer
> driver and, say, LVGL.  If that is all you want to accomplish, then all
> that you need is the framebuffer driver.
>
> But a full 3D windowing solution requires more.  The NuttX graphics
> logic is essentially such a windowing solution.  2D solutions simply
> bypass the graphics subsystem.
>
> Drawing capabiliry is limited and LVGL does a better job at that.
> Having LVGL drawing into multiple windows would be one good, rather
> simple, solution.  I ported a drawing package that I named NxWidgets.  I
> supports drawing into multiple windows but still has issues to be resolved.
>
> On 11/5/25 19:01, Tomek CEDRO wrote:
> > Lup Yuen LEE ported NuttX to Pine64 Phone and he made the LCD and
> > framebuffer driver with NuttX console and some touchscreen keyboard! You
> > may be looking for something like that right? :-)
> >
> > Lup documents everything very well on his blog :-)
> >
> > https://lupyuen.org/
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >
> > On Wed, Nov 5, 2025, 22:49 Matteo Golin <ma...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> Despite a relatively small bug with transfer size limits, the RPi4B
> microSD
> >> card support is basically done. This is largely in part to how simple
> it is
> >> on NuttX to write a lower-half SDIO implementation and have things just
> >> work, which is incredible :)
> >>
> >> I now (ambitiously) want to set my eyes on graphics. It turns out that
> >> rendering with a framebuffer is actually quite easy, but very CPU
> >> intensive. I'm going to need to figure out how to get at the GPU
> properly.
> >> *My
> >> question is: *is anyone familiar with examples on how to implement the
> >> necessary "lower-half" for the NuttX graphics library? I.e. what
> >> functions/drivers I would need to get written to allow the basic
> windowing
> >> display manager & LVGL to work on the HDMI outputs of the Pi? I have
> >> briefly read the docs about the window manager and saw that there is a
> >> framebuffer char driver that can be implemented, but I'm not sure how
> well
> >> that scales to decent graphics. I suppose this is relatively uncharted
> >> territory on an RTOS designed mainly with LCDs in mind as the only
> graphics
> >> (?). If anyone has implemented graphics support for a device before and
> can
> >> let me know a few source files to look at, that would be great!
> >>
> >> My main goal is essentially to get decently fast graphics going, since
> once
> >> that's done and some USB HID device support is set up, I can port DOOM
> to
> >> NuttX :)
> >>
> >> Thanks,
> >> Matteo
> >>
> >> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
> >> wrote:
> >>
> >>> Thanks Tomek! That would be a good resource.
> >>>
> >>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
> >>>
> >>>> OpenBSD 7.8 has been just released and it has official support for rPI
> >>>> 5 with all sorts of peripherals.. maybe this is the new source to look
> >>>> for drivers code? :-)
> >>>>
> >>>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
> >>>>
> >>>> https://cvsweb.openbsd.org/src/
> >>>>
> >>>> Have a good day :-)
> >>>> Tomek
> >>>>
> >>>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
> >>>> wrote:
> >>>>> Thanks Alan! Maybe I will reach out to Arasan, could have more luck
> >> than
> >>>>> with Broadcom, but I doubt it.
> >>>>>
> >>>>> I'll take a look at these documents!
> >>>>>
> >>>>> Thanks again,
> >>>>> Matteo
> >>>>>
> >>>>> On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com>
> >> wrote:
> >>>>>> Hi Matteo,
> >>>>>>
> >>>>>> Please that a look:
> >>>>>> https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
> >>>>>>
> >>>>>> There is an option to Download (request) the Datasheet from that
> >>>> page, but
> >>>>>> you can access it directly here:
> >>>>>>
> >>>>>>
> >>
> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
> >>>>>> This document is more about the IP core details, but could give you
> >>>> more
> >>>>>> understanding about internal block of the SDIO controller (its FIFO,
> >>>>>> initialization diagram, etc)
> >>>>>>
> >>>>>> You can also try to find the original
> >>>>>> SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
> >>>> Raspberry
> >>>>>> documentation.
> >>>>>>
> >>>>>> BR,
> >>>>>>
> >>>>>> Alan
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <
> >> matteo.golin@gmail.com
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Hi Alan,
> >>>>>>>
> >>>>>>> Thank you for the tips! Yes, SDIO looks pretty involved compared
> >> to
> >>>> SPI
> >>>>>> or
> >>>>>>> I2C. I'll try reading the specification like you suggested.
> >>>>>>>
> >>>>>>> The BCM2711 datasheet doesn't document it at all, however the EMMC
> >>>>>>> interface is supposedly the exact same from the BCM2835 and the
> >>>> registers
> >>>>>>> there are at least documented. All I know is that it is using an
> >>>>>> interface
> >>>>>>> by Arasan. I'm not as familiar with NuttX, but if this at all
> >> looks
> >>>> like
> >>>>>>> something that's already been supported, please let me know. In
> >> the
> >>>>>>> meantime, I'll look through the SDIO implementations to check:
> >>>>>>>
> >>
> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
> >>>>>>> (page 65)
> >>>>>>>
> >>>>>>> Thanks again!
> >>>>>>> Matteo
> >>>>>>>
> >>>>>>> On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
> >>>> wrote:
> >>>>>>>> HI Matteo,
> >>>>>>>>
> >>>>>>>> I implemented the SDIO support for LPC43 some years ago and what
> >>>> helped
> >>>>>>> me
> >>>>>>>> most was reading the SD/MMC specification, the LPC43 reference
> >>>> manual
> >>>>>> and
> >>>>>>>> enabling the NuttX SD/MMC debug messages.
> >>>>>>>>
> >>>>>>>> There are many details to take care of: clock enable for the
> >>>>>> controller,
> >>>>>>>> interrupts, pins configuration, etc.
> >>>>>>>>
> >>>>>>>> Unfortunately, the BCM2711 doc is not good. You can start
> >>>> verifying the
> >>>>>>>> registers, maybe it is based on some SD/MMC core IP already
> >>>> supported
> >>>>>> by
> >>>>>>>> NuttX.
> >>>>>>>>
> >>>>>>>> BR,
> >>>>>>>>
> >>>>>>>> Alan
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
> >>>> matteo.golin@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi everyone,
> >>>>>>>>>
> >>>>>>>>> Now that I2C has been tackled, I am moving on to SDIO
> >>>> interfaces so
> >>>>>> the
> >>>>>>>> SD
> >>>>>>>>> card can be interacted with from NuttX.
> >>>>>>>>>
> >>>>>>>>> The NuttX SDIO documentation is a little bare, and I'm not the
> >>>> most
> >>>>>>>>> familiar with SDIO. Does anyone have any recommendations for
> >>>>>>>>> implementations to look at (besides the STM32 one that is
> >>>> linked in
> >>>>>> the
> >>>>>>>>> docs), resources to read (any blog posts from when you ported
> >>>> SDIO)
> >>>>>> or
> >>>>>>>>> advice in general? It would be much appreciated.
> >>>>>>>>>
> >>>>>>>>> Thank you,
> >>>>>>>>> Matteo
> >>>>>>>>>
> >>>>>>>>> On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
> >>>> matteo.golin@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>> Got another response from my earlier request to Raspberry Pi
> >>>>>> through
> >>>>>>>>> their
> >>>>>>>>>> website:
> >>>>>>>>>>
> >>>>>>>>>> Hi Matteo
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Thanks for getting in touch. We don't actually have any
> >> more
> >>>>>>>>>>> documentation that we can release on this. My usual
> >>>> recommendation
> >>>>>>> is
> >>>>>>>>> for
> >>>>>>>>>>> SW people to take a look at the Linux drivers to get a
> >> closer
> >>>>>>>>> understanding
> >>>>>>>>>>> of how the HW works. Not ideal, but the best I can offer.
> >>>>>>>>>>
> >>>>>>>>>> So I guess everyone is telling us the same thing!
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <
> >> tomek@cedro.info>
> >>>>>> wrote:
> >>>>>>>>>>> Sure! Public now :-)
> >>>>>>>>>>> Tomek
> >>>>>>>>>>>
> >>>>>>>>>>> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
> >>>>>> matteo.golin@gmail.com
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>> I have populated the RPi 4B project with some starting
> >>>> issues to
> >>>>>>>>> tackle
> >>>>>>>>>>> for
> >>>>>>>>>>>> the 4B implementation. I see that the project is marked
> >> as
> >>>>>>> private;
> >>>>>>>> is
> >>>>>>>>>>>> there any way to make it visible to potential
> >> contributors
> >>>> just
> >>>>>>>>> visiting
> >>>>>>>>>>>> the GitHub page? I think if they can see a list of issues
> >>>> in one
> >>>>>>>> place
> >>>>>>>>>>> when
> >>>>>>>>>>>> they go to the page it might help.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Matteo
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
> >>>> tomek@cedro.info>
> >>>>>>>> wrote:
> >>>>>>>>>>>>> Thank you Linguini, good luck and have fun! :-)
> >>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
> >>>>>>>> matteo.golin@gmail.com
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>> To update the community, we've been told by Gordon
> >>>> that the
> >>>>>> Pi
> >>>>>>>>>>> Foundation
> >>>>>>>>>>>>>> doesn't have any documentation for the chip beyond
> >>>> what was
> >>>>>>>>> written
> >>>>>>>>>>> in
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>> peripheral datasheet. Broadcom themselves has written
> >>>> the
> >>>>>>> Linux
> >>>>>>>>>>> drivers
> >>>>>>>>>>>>> and
> >>>>>>>>>>>>>> Raspberry Pi has only made some slight bug fixes,
> >> etc.
> >>>> We've
> >>>>>>>> been
> >>>>>>>>>>>>> suggested
> >>>>>>>>>>>>>> to read the source to discover undocumented
> >>>>>>>>> registers/configuration
> >>>>>>>>>>>>> options.
> >>>>>>>>>>>>>> I plan to still continue with the port until the
> >>>> feature set
> >>>>>>> on
> >>>>>>>>>>> NuttX is
> >>>>>>>>>>>>>> equal or greater to what is available on QNX. I at
> >>>> least
> >>>>>> want
> >>>>>>> to
> >>>>>>>>> get
> >>>>>>>>>>>>>> Ethernet and some graphics running after the base
> >>>> peripheral
> >>>>>>> set
> >>>>>>>>>>> (I2C,
> >>>>>>>>>>>>> SPI,
> >>>>>>>>>>>>>> UART) are supported.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Matteo
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
> >>>>>>>>>>> matteo.golin@gmail.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>> Very interesting Sebastian. I got that impression
> >>>> from
> >>>>>>>> Broadcom
> >>>>>>>>>>> when I
> >>>>>>>>>>>>> was
> >>>>>>>>>>>>>>> initially trying to port NuttX to the Pi. The
> >>>> inability to
> >>>>>>>>> submit
> >>>>>>>>>>>>> forms on
> >>>>>>>>>>>>>>> their website seems like it might be by design...
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I'm hopeful the Raspberry Pi Foundation will have
> >>>>>> something
> >>>>>>>> more
> >>>>>>>>>>> for
> >>>>>>>>>>>>> us to
> >>>>>>>>>>>>>>> work with, they seem more positive to FOSS.
> >>>> Otherwise I
> >>>>>> will
> >>>>>>>>> still
> >>>>>>>>>>>>> continue
> >>>>>>>>>>>>>>> with reverse engineering until at least the point
> >>>> where
> >>>>>> the
> >>>>>>>>>>>>> functionality
> >>>>>>>>>>>>>>> driver-wise is on par with QNX.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
> >>>>>>> tomek@cedro.info>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>> James Dougherty contacted us with Gordon
> >>>> Hollingworth
> >>>>>> from
> >>>>>>>>>>> Raspberry
> >>>>>>>>>>>>>>>> Pi Foundation recently :-) We are waiting for
> >>>> response
> >>>>>> :-)
> >>>>>>> I
> >>>>>>>>>>> really
> >>>>>>>>>>>>>>>> hope we can get some sort of documentation and/or
> >>>> code
> >>>>>>>> samples
> >>>>>>>>> to
> >>>>>>>>>>>>>>>> write high quality NuttX port for the big
> >>>> raspberries :-)
> >>>>>>>>>>>>>>>> Open-Source matters even more in this crazy world.
> >>>> Thanks
> >>>>>>> for
> >>>>>>>>>>>>>>>> interesting article Sebastien! Personally I think
> >> we
> >>>>>> should
> >>>>>>>>>>> focus only
> >>>>>>>>>>>>>>>> on vendors that support Open-Source. What is the
> >>>> reason
> >>>>>> for
> >>>>>>>>>>> bumping
> >>>>>>>>>>>>>>>> sales for companies that in the end can sue you
> >> for
> >>>>>>>> reversing?
> >>>>>>>>> :D
> >>>>>>>>>>>>>>>> Have a good day folks :-)
> >>>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 10:15 AM Sebastien
> >> Lorquet <
> >>>>>>>>>>>>> sebastien@lorquet.fr>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I just found this interesting document:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>
> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
> >>>>>>>>>>>>>>>>> In a summary, if you expect anything cool from
> >>>>>> broadcom:
> >>>>>>>>> dont.
> >>>>>>>>>>>>>>>>> go go go reverse engineering!
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sebastien
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On 8/29/25 15:37, Tomek CEDRO wrote:
> >>>>>>>>>>>>>>>>>> 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
> >>>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>> I just asked question at #asfinfra / slack,
> >>>> maybe
> >>>>>>>> someone
> >>>>>>>>>>> can
> >>>>>>>>>>>>> help
> >>>>>>>>>>>>>>>>>>> there or recommend someone who can, waiting
> >> for
> >>>>>>> response
> >>>>>>>>> :-)
> >>>>>>>>>>>>>>>>>>> For a good start you can contact Broadcom and
> >>>>>>>> RaspberryPi
> >>>>>>>>>>>>> Foundation,
> >>>>>>>>>>>>>>>>>>> introduce yourself as Apache NuttX RTOS
> >>>> developer
> >>>>>> that
> >>>>>>>>> want
> >>>>>>>>>>> to
> >>>>>>>>>>>>> port
> >>>>>>>>>>>>>>>>>>> NuttX to rPI boards, and just ask if
> >>>> DataSheets are
> >>>>>>>>>>> available
> >>>>>>>>>>>>> :-) We
> >>>>>>>>>>>>>>>>>>> will know then first hand if this is possible
> >>>> or are
> >>>>>>>> there
> >>>>>>>>>>> any
> >>>>>>>>>>>>>>>>>>> problems / requirements :-)
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> You can ask for 4B and probably Zero-2W SoC
> >>>>>>>> documentation
> >>>>>>>>>>> these
> >>>>>>>>>>>>> seems
> >>>>>>>>>>>>>>>>>>> most popular nowadays :-)
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thanks :-)
> >>>>>>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin
> >> <
> >>>>>>>>>>>>> matteo.golin@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 <
> >>>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
> >>>> Golin <
> >>>>>>>>>>>>>>>> matteo.golin@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
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>
> >>>>
> >>>>
> >>>> --
> >>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>
>

Re: RPI 4B Roadmap

Posted by Xiang Xiao <xi...@gmail.com>.
LVGL supports multiple instances with
https://github.com/lvgl/lvgl/issues/4358.
So, the windowing system can reuse LVGL as a widget library inside a window
just like NxWidget,
 but has more user-friendly touch expression.

On Thu, Nov 6, 2025 at 10:28 AM Gregory Nutt <sp...@gmail.com> wrote:

> The most critical thing is the architecture of the graphics subsystem,
> not any particular framebuffer driver.  We should discuss and settle on
> a clean, modular architecture before getting ahead of ourselves.
>
> A simple 2D graphics system can be implemented with only a framebuffer
> driver and, say, LVGL.  If that is all you want to accomplish, then all
> that you need is the framebuffer driver.
>
> But a full 3D windowing solution requires more.  The NuttX graphics
> logic is essentially such a windowing solution.  2D solutions simply
> bypass the graphics subsystem.
>
> Drawing capabiliry is limited and LVGL does a better job at that.
> Having LVGL drawing into multiple windows would be one good, rather
> simple, solution.  I ported a drawing package that I named NxWidgets.  I
> supports drawing into multiple windows but still has issues to be resolved.
>
> On 11/5/25 19:01, Tomek CEDRO wrote:
> > Lup Yuen LEE ported NuttX to Pine64 Phone and he made the LCD and
> > framebuffer driver with NuttX console and some touchscreen keyboard! You
> > may be looking for something like that right? :-)
> >
> > Lup documents everything very well on his blog :-)
> >
> > https://lupyuen.org/
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >
> > On Wed, Nov 5, 2025, 22:49 Matteo Golin <ma...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> Despite a relatively small bug with transfer size limits, the RPi4B
> microSD
> >> card support is basically done. This is largely in part to how simple
> it is
> >> on NuttX to write a lower-half SDIO implementation and have things just
> >> work, which is incredible :)
> >>
> >> I now (ambitiously) want to set my eyes on graphics. It turns out that
> >> rendering with a framebuffer is actually quite easy, but very CPU
> >> intensive. I'm going to need to figure out how to get at the GPU
> properly.
> >> *My
> >> question is: *is anyone familiar with examples on how to implement the
> >> necessary "lower-half" for the NuttX graphics library? I.e. what
> >> functions/drivers I would need to get written to allow the basic
> windowing
> >> display manager & LVGL to work on the HDMI outputs of the Pi? I have
> >> briefly read the docs about the window manager and saw that there is a
> >> framebuffer char driver that can be implemented, but I'm not sure how
> well
> >> that scales to decent graphics. I suppose this is relatively uncharted
> >> territory on an RTOS designed mainly with LCDs in mind as the only
> graphics
> >> (?). If anyone has implemented graphics support for a device before and
> can
> >> let me know a few source files to look at, that would be great!
> >>
> >> My main goal is essentially to get decently fast graphics going, since
> once
> >> that's done and some USB HID device support is set up, I can port DOOM
> to
> >> NuttX :)
> >>
> >> Thanks,
> >> Matteo
> >>
> >> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
> >> wrote:
> >>
> >>> Thanks Tomek! That would be a good resource.
> >>>
> >>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
> >>>
> >>>> OpenBSD 7.8 has been just released and it has official support for rPI
> >>>> 5 with all sorts of peripherals.. maybe this is the new source to look
> >>>> for drivers code? :-)
> >>>>
> >>>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
> >>>>
> >>>> https://cvsweb.openbsd.org/src/
> >>>>
> >>>> Have a good day :-)
> >>>> Tomek
> >>>>
> >>>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
> >>>> wrote:
> >>>>> Thanks Alan! Maybe I will reach out to Arasan, could have more luck
> >> than
> >>>>> with Broadcom, but I doubt it.
> >>>>>
> >>>>> I'll take a look at these documents!
> >>>>>
> >>>>> Thanks again,
> >>>>> Matteo
> >>>>>
> >>>>> On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com>
> >> wrote:
> >>>>>> Hi Matteo,
> >>>>>>
> >>>>>> Please that a look:
> >>>>>> https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
> >>>>>>
> >>>>>> There is an option to Download (request) the Datasheet from that
> >>>> page, but
> >>>>>> you can access it directly here:
> >>>>>>
> >>>>>>
> >>
> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
> >>>>>> This document is more about the IP core details, but could give you
> >>>> more
> >>>>>> understanding about internal block of the SDIO controller (its FIFO,
> >>>>>> initialization diagram, etc)
> >>>>>>
> >>>>>> You can also try to find the original
> >>>>>> SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
> >>>> Raspberry
> >>>>>> documentation.
> >>>>>>
> >>>>>> BR,
> >>>>>>
> >>>>>> Alan
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <
> >> matteo.golin@gmail.com
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Hi Alan,
> >>>>>>>
> >>>>>>> Thank you for the tips! Yes, SDIO looks pretty involved compared
> >> to
> >>>> SPI
> >>>>>> or
> >>>>>>> I2C. I'll try reading the specification like you suggested.
> >>>>>>>
> >>>>>>> The BCM2711 datasheet doesn't document it at all, however the EMMC
> >>>>>>> interface is supposedly the exact same from the BCM2835 and the
> >>>> registers
> >>>>>>> there are at least documented. All I know is that it is using an
> >>>>>> interface
> >>>>>>> by Arasan. I'm not as familiar with NuttX, but if this at all
> >> looks
> >>>> like
> >>>>>>> something that's already been supported, please let me know. In
> >> the
> >>>>>>> meantime, I'll look through the SDIO implementations to check:
> >>>>>>>
> >>
> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
> >>>>>>> (page 65)
> >>>>>>>
> >>>>>>> Thanks again!
> >>>>>>> Matteo
> >>>>>>>
> >>>>>>> On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
> >>>> wrote:
> >>>>>>>> HI Matteo,
> >>>>>>>>
> >>>>>>>> I implemented the SDIO support for LPC43 some years ago and what
> >>>> helped
> >>>>>>> me
> >>>>>>>> most was reading the SD/MMC specification, the LPC43 reference
> >>>> manual
> >>>>>> and
> >>>>>>>> enabling the NuttX SD/MMC debug messages.
> >>>>>>>>
> >>>>>>>> There are many details to take care of: clock enable for the
> >>>>>> controller,
> >>>>>>>> interrupts, pins configuration, etc.
> >>>>>>>>
> >>>>>>>> Unfortunately, the BCM2711 doc is not good. You can start
> >>>> verifying the
> >>>>>>>> registers, maybe it is based on some SD/MMC core IP already
> >>>> supported
> >>>>>> by
> >>>>>>>> NuttX.
> >>>>>>>>
> >>>>>>>> BR,
> >>>>>>>>
> >>>>>>>> Alan
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
> >>>> matteo.golin@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi everyone,
> >>>>>>>>>
> >>>>>>>>> Now that I2C has been tackled, I am moving on to SDIO
> >>>> interfaces so
> >>>>>> the
> >>>>>>>> SD
> >>>>>>>>> card can be interacted with from NuttX.
> >>>>>>>>>
> >>>>>>>>> The NuttX SDIO documentation is a little bare, and I'm not the
> >>>> most
> >>>>>>>>> familiar with SDIO. Does anyone have any recommendations for
> >>>>>>>>> implementations to look at (besides the STM32 one that is
> >>>> linked in
> >>>>>> the
> >>>>>>>>> docs), resources to read (any blog posts from when you ported
> >>>> SDIO)
> >>>>>> or
> >>>>>>>>> advice in general? It would be much appreciated.
> >>>>>>>>>
> >>>>>>>>> Thank you,
> >>>>>>>>> Matteo
> >>>>>>>>>
> >>>>>>>>> On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
> >>>> matteo.golin@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>> Got another response from my earlier request to Raspberry Pi
> >>>>>> through
> >>>>>>>>> their
> >>>>>>>>>> website:
> >>>>>>>>>>
> >>>>>>>>>> Hi Matteo
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> Thanks for getting in touch. We don't actually have any
> >> more
> >>>>>>>>>>> documentation that we can release on this. My usual
> >>>> recommendation
> >>>>>>> is
> >>>>>>>>> for
> >>>>>>>>>>> SW people to take a look at the Linux drivers to get a
> >> closer
> >>>>>>>>> understanding
> >>>>>>>>>>> of how the HW works. Not ideal, but the best I can offer.
> >>>>>>>>>>
> >>>>>>>>>> So I guess everyone is telling us the same thing!
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <
> >> tomek@cedro.info>
> >>>>>> wrote:
> >>>>>>>>>>> Sure! Public now :-)
> >>>>>>>>>>> Tomek
> >>>>>>>>>>>
> >>>>>>>>>>> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
> >>>>>> matteo.golin@gmail.com
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>> I have populated the RPi 4B project with some starting
> >>>> issues to
> >>>>>>>>> tackle
> >>>>>>>>>>> for
> >>>>>>>>>>>> the 4B implementation. I see that the project is marked
> >> as
> >>>>>>> private;
> >>>>>>>> is
> >>>>>>>>>>>> there any way to make it visible to potential
> >> contributors
> >>>> just
> >>>>>>>>> visiting
> >>>>>>>>>>>> the GitHub page? I think if they can see a list of issues
> >>>> in one
> >>>>>>>> place
> >>>>>>>>>>> when
> >>>>>>>>>>>> they go to the page it might help.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>> Matteo
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
> >>>> tomek@cedro.info>
> >>>>>>>> wrote:
> >>>>>>>>>>>>> Thank you Linguini, good luck and have fun! :-)
> >>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
> >>>>>>>> matteo.golin@gmail.com
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>> To update the community, we've been told by Gordon
> >>>> that the
> >>>>>> Pi
> >>>>>>>>>>> Foundation
> >>>>>>>>>>>>>> doesn't have any documentation for the chip beyond
> >>>> what was
> >>>>>>>>> written
> >>>>>>>>>>> in
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>> peripheral datasheet. Broadcom themselves has written
> >>>> the
> >>>>>>> Linux
> >>>>>>>>>>> drivers
> >>>>>>>>>>>>> and
> >>>>>>>>>>>>>> Raspberry Pi has only made some slight bug fixes,
> >> etc.
> >>>> We've
> >>>>>>>> been
> >>>>>>>>>>>>> suggested
> >>>>>>>>>>>>>> to read the source to discover undocumented
> >>>>>>>>> registers/configuration
> >>>>>>>>>>>>> options.
> >>>>>>>>>>>>>> I plan to still continue with the port until the
> >>>> feature set
> >>>>>>> on
> >>>>>>>>>>> NuttX is
> >>>>>>>>>>>>>> equal or greater to what is available on QNX. I at
> >>>> least
> >>>>>> want
> >>>>>>> to
> >>>>>>>>> get
> >>>>>>>>>>>>>> Ethernet and some graphics running after the base
> >>>> peripheral
> >>>>>>> set
> >>>>>>>>>>> (I2C,
> >>>>>>>>>>>>> SPI,
> >>>>>>>>>>>>>> UART) are supported.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Matteo
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
> >>>>>>>>>>> matteo.golin@gmail.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>> Very interesting Sebastian. I got that impression
> >>>> from
> >>>>>>>> Broadcom
> >>>>>>>>>>> when I
> >>>>>>>>>>>>> was
> >>>>>>>>>>>>>>> initially trying to port NuttX to the Pi. The
> >>>> inability to
> >>>>>>>>> submit
> >>>>>>>>>>>>> forms on
> >>>>>>>>>>>>>>> their website seems like it might be by design...
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I'm hopeful the Raspberry Pi Foundation will have
> >>>>>> something
> >>>>>>>> more
> >>>>>>>>>>> for
> >>>>>>>>>>>>> us to
> >>>>>>>>>>>>>>> work with, they seem more positive to FOSS.
> >>>> Otherwise I
> >>>>>> will
> >>>>>>>>> still
> >>>>>>>>>>>>> continue
> >>>>>>>>>>>>>>> with reverse engineering until at least the point
> >>>> where
> >>>>>> the
> >>>>>>>>>>>>> functionality
> >>>>>>>>>>>>>>> driver-wise is on par with QNX.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
> >>>>>>> tomek@cedro.info>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>> James Dougherty contacted us with Gordon
> >>>> Hollingworth
> >>>>>> from
> >>>>>>>>>>> Raspberry
> >>>>>>>>>>>>>>>> Pi Foundation recently :-) We are waiting for
> >>>> response
> >>>>>> :-)
> >>>>>>> I
> >>>>>>>>>>> really
> >>>>>>>>>>>>>>>> hope we can get some sort of documentation and/or
> >>>> code
> >>>>>>>> samples
> >>>>>>>>> to
> >>>>>>>>>>>>>>>> write high quality NuttX port for the big
> >>>> raspberries :-)
> >>>>>>>>>>>>>>>> Open-Source matters even more in this crazy world.
> >>>> Thanks
> >>>>>>> for
> >>>>>>>>>>>>>>>> interesting article Sebastien! Personally I think
> >> we
> >>>>>> should
> >>>>>>>>>>> focus only
> >>>>>>>>>>>>>>>> on vendors that support Open-Source. What is the
> >>>> reason
> >>>>>> for
> >>>>>>>>>>> bumping
> >>>>>>>>>>>>>>>> sales for companies that in the end can sue you
> >> for
> >>>>>>>> reversing?
> >>>>>>>>> :D
> >>>>>>>>>>>>>>>> Have a good day folks :-)
> >>>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 10:15 AM Sebastien
> >> Lorquet <
> >>>>>>>>>>>>> sebastien@lorquet.fr>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I just found this interesting document:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>
> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
> >>>>>>>>>>>>>>>>> In a summary, if you expect anything cool from
> >>>>>> broadcom:
> >>>>>>>>> dont.
> >>>>>>>>>>>>>>>>> go go go reverse engineering!
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Sebastien
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On 8/29/25 15:37, Tomek CEDRO wrote:
> >>>>>>>>>>>>>>>>>> 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
> >>>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>> I just asked question at #asfinfra / slack,
> >>>> maybe
> >>>>>>>> someone
> >>>>>>>>>>> can
> >>>>>>>>>>>>> help
> >>>>>>>>>>>>>>>>>>> there or recommend someone who can, waiting
> >> for
> >>>>>>> response
> >>>>>>>>> :-)
> >>>>>>>>>>>>>>>>>>> For a good start you can contact Broadcom and
> >>>>>>>> RaspberryPi
> >>>>>>>>>>>>> Foundation,
> >>>>>>>>>>>>>>>>>>> introduce yourself as Apache NuttX RTOS
> >>>> developer
> >>>>>> that
> >>>>>>>>> want
> >>>>>>>>>>> to
> >>>>>>>>>>>>> port
> >>>>>>>>>>>>>>>>>>> NuttX to rPI boards, and just ask if
> >>>> DataSheets are
> >>>>>>>>>>> available
> >>>>>>>>>>>>> :-) We
> >>>>>>>>>>>>>>>>>>> will know then first hand if this is possible
> >>>> or are
> >>>>>>>> there
> >>>>>>>>>>> any
> >>>>>>>>>>>>>>>>>>> problems / requirements :-)
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> You can ask for 4B and probably Zero-2W SoC
> >>>>>>>> documentation
> >>>>>>>>>>> these
> >>>>>>>>>>>>> seems
> >>>>>>>>>>>>>>>>>>> most popular nowadays :-)
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thanks :-)
> >>>>>>>>>>>>>>>>>>> Tomek
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin
> >> <
> >>>>>>>>>>>>> matteo.golin@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 <
> >>>>>>>>>>> tomek@cedro.info>
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
> >>>> Golin <
> >>>>>>>>>>>>>>>> matteo.golin@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
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>>>>>>>>
> >>>>
> >>>>
> >>>> --
> >>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>>>
>

Re: RPI 4B Roadmap

Posted by Gregory Nutt <sp...@gmail.com>.
The most critical thing is the architecture of the graphics subsystem, 
not any particular framebuffer driver.  We should discuss and settle on 
a clean, modular architecture before getting ahead of ourselves.

A simple 2D graphics system can be implemented with only a framebuffer 
driver and, say, LVGL.  If that is all you want to accomplish, then all 
that you need is the framebuffer driver.

But a full 3D windowing solution requires more.  The NuttX graphics 
logic is essentially such a windowing solution.  2D solutions simply 
bypass the graphics subsystem.

Drawing capabiliry is limited and LVGL does a better job at that.  
Having LVGL drawing into multiple windows would be one good, rather 
simple, solution.  I ported a drawing package that I named NxWidgets.  I 
supports drawing into multiple windows but still has issues to be resolved.

On 11/5/25 19:01, Tomek CEDRO wrote:
> Lup Yuen LEE ported NuttX to Pine64 Phone and he made the LCD and
> framebuffer driver with NuttX console and some touchscreen keyboard! You
> may be looking for something like that right? :-)
>
> Lup documents everything very well on his blog :-)
>
> https://lupyuen.org/
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>
> On Wed, Nov 5, 2025, 22:49 Matteo Golin <ma...@gmail.com> wrote:
>
>> Hi all,
>>
>> Despite a relatively small bug with transfer size limits, the RPi4B microSD
>> card support is basically done. This is largely in part to how simple it is
>> on NuttX to write a lower-half SDIO implementation and have things just
>> work, which is incredible :)
>>
>> I now (ambitiously) want to set my eyes on graphics. It turns out that
>> rendering with a framebuffer is actually quite easy, but very CPU
>> intensive. I'm going to need to figure out how to get at the GPU properly.
>> *My
>> question is: *is anyone familiar with examples on how to implement the
>> necessary "lower-half" for the NuttX graphics library? I.e. what
>> functions/drivers I would need to get written to allow the basic windowing
>> display manager & LVGL to work on the HDMI outputs of the Pi? I have
>> briefly read the docs about the window manager and saw that there is a
>> framebuffer char driver that can be implemented, but I'm not sure how well
>> that scales to decent graphics. I suppose this is relatively uncharted
>> territory on an RTOS designed mainly with LCDs in mind as the only graphics
>> (?). If anyone has implemented graphics support for a device before and can
>> let me know a few source files to look at, that would be great!
>>
>> My main goal is essentially to get decently fast graphics going, since once
>> that's done and some USB HID device support is set up, I can port DOOM to
>> NuttX :)
>>
>> Thanks,
>> Matteo
>>
>> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
>> wrote:
>>
>>> Thanks Tomek! That would be a good resource.
>>>
>>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
>>>
>>>> OpenBSD 7.8 has been just released and it has official support for rPI
>>>> 5 with all sorts of peripherals.. maybe this is the new source to look
>>>> for drivers code? :-)
>>>>
>>>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
>>>>
>>>> https://cvsweb.openbsd.org/src/
>>>>
>>>> Have a good day :-)
>>>> Tomek
>>>>
>>>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
>>>> wrote:
>>>>> Thanks Alan! Maybe I will reach out to Arasan, could have more luck
>> than
>>>>> with Broadcom, but I doubt it.
>>>>>
>>>>> I'll take a look at these documents!
>>>>>
>>>>> Thanks again,
>>>>> Matteo
>>>>>
>>>>> On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com>
>> wrote:
>>>>>> Hi Matteo,
>>>>>>
>>>>>> Please that a look:
>>>>>> https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
>>>>>>
>>>>>> There is an option to Download (request) the Datasheet from that
>>>> page, but
>>>>>> you can access it directly here:
>>>>>>
>>>>>>
>> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
>>>>>> This document is more about the IP core details, but could give you
>>>> more
>>>>>> understanding about internal block of the SDIO controller (its FIFO,
>>>>>> initialization diagram, etc)
>>>>>>
>>>>>> You can also try to find the original
>>>>>> SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
>>>> Raspberry
>>>>>> documentation.
>>>>>>
>>>>>> BR,
>>>>>>
>>>>>> Alan
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <
>> matteo.golin@gmail.com
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Alan,
>>>>>>>
>>>>>>> Thank you for the tips! Yes, SDIO looks pretty involved compared
>> to
>>>> SPI
>>>>>> or
>>>>>>> I2C. I'll try reading the specification like you suggested.
>>>>>>>
>>>>>>> The BCM2711 datasheet doesn't document it at all, however the EMMC
>>>>>>> interface is supposedly the exact same from the BCM2835 and the
>>>> registers
>>>>>>> there are at least documented. All I know is that it is using an
>>>>>> interface
>>>>>>> by Arasan. I'm not as familiar with NuttX, but if this at all
>> looks
>>>> like
>>>>>>> something that's already been supported, please let me know. In
>> the
>>>>>>> meantime, I'll look through the SDIO implementations to check:
>>>>>>>
>> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
>>>>>>> (page 65)
>>>>>>>
>>>>>>> Thanks again!
>>>>>>> Matteo
>>>>>>>
>>>>>>> On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
>>>> wrote:
>>>>>>>> HI Matteo,
>>>>>>>>
>>>>>>>> I implemented the SDIO support for LPC43 some years ago and what
>>>> helped
>>>>>>> me
>>>>>>>> most was reading the SD/MMC specification, the LPC43 reference
>>>> manual
>>>>>> and
>>>>>>>> enabling the NuttX SD/MMC debug messages.
>>>>>>>>
>>>>>>>> There are many details to take care of: clock enable for the
>>>>>> controller,
>>>>>>>> interrupts, pins configuration, etc.
>>>>>>>>
>>>>>>>> Unfortunately, the BCM2711 doc is not good. You can start
>>>> verifying the
>>>>>>>> registers, maybe it is based on some SD/MMC core IP already
>>>> supported
>>>>>> by
>>>>>>>> NuttX.
>>>>>>>>
>>>>>>>> BR,
>>>>>>>>
>>>>>>>> Alan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
>>>> matteo.golin@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi everyone,
>>>>>>>>>
>>>>>>>>> Now that I2C has been tackled, I am moving on to SDIO
>>>> interfaces so
>>>>>> the
>>>>>>>> SD
>>>>>>>>> card can be interacted with from NuttX.
>>>>>>>>>
>>>>>>>>> The NuttX SDIO documentation is a little bare, and I'm not the
>>>> most
>>>>>>>>> familiar with SDIO. Does anyone have any recommendations for
>>>>>>>>> implementations to look at (besides the STM32 one that is
>>>> linked in
>>>>>> the
>>>>>>>>> docs), resources to read (any blog posts from when you ported
>>>> SDIO)
>>>>>> or
>>>>>>>>> advice in general? It would be much appreciated.
>>>>>>>>>
>>>>>>>>> Thank you,
>>>>>>>>> Matteo
>>>>>>>>>
>>>>>>>>> On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
>>>> matteo.golin@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>> Got another response from my earlier request to Raspberry Pi
>>>>>> through
>>>>>>>>> their
>>>>>>>>>> website:
>>>>>>>>>>
>>>>>>>>>> Hi Matteo
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Thanks for getting in touch. We don't actually have any
>> more
>>>>>>>>>>> documentation that we can release on this. My usual
>>>> recommendation
>>>>>>> is
>>>>>>>>> for
>>>>>>>>>>> SW people to take a look at the Linux drivers to get a
>> closer
>>>>>>>>> understanding
>>>>>>>>>>> of how the HW works. Not ideal, but the best I can offer.
>>>>>>>>>>
>>>>>>>>>> So I guess everyone is telling us the same thing!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <
>> tomek@cedro.info>
>>>>>> wrote:
>>>>>>>>>>> Sure! Public now :-)
>>>>>>>>>>> Tomek
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
>>>>>> matteo.golin@gmail.com
>>>>>>>>>>> wrote:
>>>>>>>>>>>> I have populated the RPi 4B project with some starting
>>>> issues to
>>>>>>>>> tackle
>>>>>>>>>>> for
>>>>>>>>>>>> the 4B implementation. I see that the project is marked
>> as
>>>>>>> private;
>>>>>>>> is
>>>>>>>>>>>> there any way to make it visible to potential
>> contributors
>>>> just
>>>>>>>>> visiting
>>>>>>>>>>>> the GitHub page? I think if they can see a list of issues
>>>> in one
>>>>>>>> place
>>>>>>>>>>> when
>>>>>>>>>>>> they go to the page it might help.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Matteo
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
>>>> tomek@cedro.info>
>>>>>>>> wrote:
>>>>>>>>>>>>> Thank you Linguini, good luck and have fun! :-)
>>>>>>>>>>>>> Tomek
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
>>>>>>>> matteo.golin@gmail.com
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> To update the community, we've been told by Gordon
>>>> that the
>>>>>> Pi
>>>>>>>>>>> Foundation
>>>>>>>>>>>>>> doesn't have any documentation for the chip beyond
>>>> what was
>>>>>>>>> written
>>>>>>>>>>> in
>>>>>>>>>>>>> the
>>>>>>>>>>>>>> peripheral datasheet. Broadcom themselves has written
>>>> the
>>>>>>> Linux
>>>>>>>>>>> drivers
>>>>>>>>>>>>> and
>>>>>>>>>>>>>> Raspberry Pi has only made some slight bug fixes,
>> etc.
>>>> We've
>>>>>>>> been
>>>>>>>>>>>>> suggested
>>>>>>>>>>>>>> to read the source to discover undocumented
>>>>>>>>> registers/configuration
>>>>>>>>>>>>> options.
>>>>>>>>>>>>>> I plan to still continue with the port until the
>>>> feature set
>>>>>>> on
>>>>>>>>>>> NuttX is
>>>>>>>>>>>>>> equal or greater to what is available on QNX. I at
>>>> least
>>>>>> want
>>>>>>> to
>>>>>>>>> get
>>>>>>>>>>>>>> Ethernet and some graphics running after the base
>>>> peripheral
>>>>>>> set
>>>>>>>>>>> (I2C,
>>>>>>>>>>>>> SPI,
>>>>>>>>>>>>>> UART) are supported.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Matteo
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
>>>>>>>>>>> matteo.golin@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> Very interesting Sebastian. I got that impression
>>>> from
>>>>>>>> Broadcom
>>>>>>>>>>> when I
>>>>>>>>>>>>> was
>>>>>>>>>>>>>>> initially trying to port NuttX to the Pi. The
>>>> inability to
>>>>>>>>> submit
>>>>>>>>>>>>> forms on
>>>>>>>>>>>>>>> their website seems like it might be by design...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm hopeful the Raspberry Pi Foundation will have
>>>>>> something
>>>>>>>> more
>>>>>>>>>>> for
>>>>>>>>>>>>> us to
>>>>>>>>>>>>>>> work with, they seem more positive to FOSS.
>>>> Otherwise I
>>>>>> will
>>>>>>>>> still
>>>>>>>>>>>>> continue
>>>>>>>>>>>>>>> with reverse engineering until at least the point
>>>> where
>>>>>> the
>>>>>>>>>>>>> functionality
>>>>>>>>>>>>>>> driver-wise is on par with QNX.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
>>>>>>> tomek@cedro.info>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> James Dougherty contacted us with Gordon
>>>> Hollingworth
>>>>>> from
>>>>>>>>>>> Raspberry
>>>>>>>>>>>>>>>> Pi Foundation recently :-) We are waiting for
>>>> response
>>>>>> :-)
>>>>>>> I
>>>>>>>>>>> really
>>>>>>>>>>>>>>>> hope we can get some sort of documentation and/or
>>>> code
>>>>>>>> samples
>>>>>>>>> to
>>>>>>>>>>>>>>>> write high quality NuttX port for the big
>>>> raspberries :-)
>>>>>>>>>>>>>>>> Open-Source matters even more in this crazy world.
>>>> Thanks
>>>>>>> for
>>>>>>>>>>>>>>>> interesting article Sebastien! Personally I think
>> we
>>>>>> should
>>>>>>>>>>> focus only
>>>>>>>>>>>>>>>> on vendors that support Open-Source. What is the
>>>> reason
>>>>>> for
>>>>>>>>>>> bumping
>>>>>>>>>>>>>>>> sales for companies that in the end can sue you
>> for
>>>>>>>> reversing?
>>>>>>>>> :D
>>>>>>>>>>>>>>>> Have a good day folks :-)
>>>>>>>>>>>>>>>> Tomek
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Aug 31, 2025 at 10:15 AM Sebastien
>> Lorquet <
>>>>>>>>>>>>> sebastien@lorquet.fr>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I just found this interesting document:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
>>>>>>>>>>>>>>>>> In a summary, if you expect anything cool from
>>>>>> broadcom:
>>>>>>>>> dont.
>>>>>>>>>>>>>>>>> go go go reverse engineering!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Sebastien
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 8/29/25 15:37, Tomek CEDRO wrote:
>>>>>>>>>>>>>>>>>> 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
>>>>>>>>>>> tomek@cedro.info>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> I just asked question at #asfinfra / slack,
>>>> maybe
>>>>>>>> someone
>>>>>>>>>>> can
>>>>>>>>>>>>> help
>>>>>>>>>>>>>>>>>>> there or recommend someone who can, waiting
>> for
>>>>>>> response
>>>>>>>>> :-)
>>>>>>>>>>>>>>>>>>> For a good start you can contact Broadcom and
>>>>>>>> RaspberryPi
>>>>>>>>>>>>> Foundation,
>>>>>>>>>>>>>>>>>>> introduce yourself as Apache NuttX RTOS
>>>> developer
>>>>>> that
>>>>>>>>> want
>>>>>>>>>>> to
>>>>>>>>>>>>> port
>>>>>>>>>>>>>>>>>>> NuttX to rPI boards, and just ask if
>>>> DataSheets are
>>>>>>>>>>> available
>>>>>>>>>>>>> :-) We
>>>>>>>>>>>>>>>>>>> will know then first hand if this is possible
>>>> or are
>>>>>>>> there
>>>>>>>>>>> any
>>>>>>>>>>>>>>>>>>> problems / requirements :-)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> You can ask for 4B and probably Zero-2W SoC
>>>>>>>> documentation
>>>>>>>>>>> these
>>>>>>>>>>>>> seems
>>>>>>>>>>>>>>>>>>> most popular nowadays :-)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks :-)
>>>>>>>>>>>>>>>>>>> Tomek
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin
>> <
>>>>>>>>>>>>> matteo.golin@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 <
>>>>>>>>>>> tomek@cedro.info>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
>>>> Golin <
>>>>>>>>>>>>>>>> matteo.golin@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
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>>>>>>>>
>>>>
>>>>
>>>> --
>>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>>>>

Re: RPI 4B Roadmap

Posted by Tomek CEDRO <to...@cedro.info>.
Lup Yuen LEE ported NuttX to Pine64 Phone and he made the LCD and
framebuffer driver with NuttX console and some touchscreen keyboard! You
may be looking for something like that right? :-)

Lup documents everything very well on his blog :-)

https://lupyuen.org/

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

On Wed, Nov 5, 2025, 22:49 Matteo Golin <ma...@gmail.com> wrote:

> Hi all,
>
> Despite a relatively small bug with transfer size limits, the RPi4B microSD
> card support is basically done. This is largely in part to how simple it is
> on NuttX to write a lower-half SDIO implementation and have things just
> work, which is incredible :)
>
> I now (ambitiously) want to set my eyes on graphics. It turns out that
> rendering with a framebuffer is actually quite easy, but very CPU
> intensive. I'm going to need to figure out how to get at the GPU properly.
> *My
> question is: *is anyone familiar with examples on how to implement the
> necessary "lower-half" for the NuttX graphics library? I.e. what
> functions/drivers I would need to get written to allow the basic windowing
> display manager & LVGL to work on the HDMI outputs of the Pi? I have
> briefly read the docs about the window manager and saw that there is a
> framebuffer char driver that can be implemented, but I'm not sure how well
> that scales to decent graphics. I suppose this is relatively uncharted
> territory on an RTOS designed mainly with LCDs in mind as the only graphics
> (?). If anyone has implemented graphics support for a device before and can
> let me know a few source files to look at, that would be great!
>
> My main goal is essentially to get decently fast graphics going, since once
> that's done and some USB HID device support is set up, I can port DOOM to
> NuttX :)
>
> Thanks,
> Matteo
>
> On Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>
> wrote:
>
> > Thanks Tomek! That would be a good resource.
> >
> > On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:
> >
> >> OpenBSD 7.8 has been just released and it has official support for rPI
> >> 5 with all sorts of peripherals.. maybe this is the new source to look
> >> for drivers code? :-)
> >>
> >> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64
> >>
> >> https://cvsweb.openbsd.org/src/
> >>
> >> Have a good day :-)
> >> Tomek
> >>
> >> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>
> >> wrote:
> >> >
> >> > Thanks Alan! Maybe I will reach out to Arasan, could have more luck
> than
> >> > with Broadcom, but I doubt it.
> >> >
> >> > I'll take a look at these documents!
> >> >
> >> > Thanks again,
> >> > Matteo
> >> >
> >> > On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com>
> wrote:
> >> >
> >> > > Hi Matteo,
> >> > >
> >> > > Please that a look:
> >> > > https://www.arasan.com/products/sd-emmc/sdio-3-0-device/
> >> > >
> >> > > There is an option to Download (request) the Datasheet from that
> >> page, but
> >> > > you can access it directly here:
> >> > >
> >> > >
> >>
> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf
> >> > >
> >> > > This document is more about the IP core details, but could give you
> >> more
> >> > > understanding about internal block of the SDIO controller (its FIFO,
> >> > > initialization diagram, etc)
> >> > >
> >> > > You can also try to find the original
> >> > > SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in
> >> Raspberry
> >> > > documentation.
> >> > >
> >> > > BR,
> >> > >
> >> > > Alan
> >> > >
> >> > >
> >> > >
> >> > > On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <
> matteo.golin@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > Hi Alan,
> >> > > >
> >> > > > Thank you for the tips! Yes, SDIO looks pretty involved compared
> to
> >> SPI
> >> > > or
> >> > > > I2C. I'll try reading the specification like you suggested.
> >> > > >
> >> > > > The BCM2711 datasheet doesn't document it at all, however the EMMC
> >> > > > interface is supposedly the exact same from the BCM2835 and the
> >> registers
> >> > > > there are at least documented. All I know is that it is using an
> >> > > interface
> >> > > > by Arasan. I'm not as familiar with NuttX, but if this at all
> looks
> >> like
> >> > > > something that's already been supported, please let me know. In
> the
> >> > > > meantime, I'll look through the SDIO implementations to check:
> >> > > >
> >> > >
> >>
> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf
> >> > > > (page 65)
> >> > > >
> >> > > > Thanks again!
> >> > > > Matteo
> >> > > >
> >> > > > On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>
> >> wrote:
> >> > > >
> >> > > > > HI Matteo,
> >> > > > >
> >> > > > > I implemented the SDIO support for LPC43 some years ago and what
> >> helped
> >> > > > me
> >> > > > > most was reading the SD/MMC specification, the LPC43 reference
> >> manual
> >> > > and
> >> > > > > enabling the NuttX SD/MMC debug messages.
> >> > > > >
> >> > > > > There are many details to take care of: clock enable for the
> >> > > controller,
> >> > > > > interrupts, pins configuration, etc.
> >> > > > >
> >> > > > > Unfortunately, the BCM2711 doc is not good. You can start
> >> verifying the
> >> > > > > registers, maybe it is based on some SD/MMC core IP already
> >> supported
> >> > > by
> >> > > > > NuttX.
> >> > > > >
> >> > > > > BR,
> >> > > > >
> >> > > > > Alan
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <
> >> matteo.golin@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Hi everyone,
> >> > > > > >
> >> > > > > > Now that I2C has been tackled, I am moving on to SDIO
> >> interfaces so
> >> > > the
> >> > > > > SD
> >> > > > > > card can be interacted with from NuttX.
> >> > > > > >
> >> > > > > > The NuttX SDIO documentation is a little bare, and I'm not the
> >> most
> >> > > > > > familiar with SDIO. Does anyone have any recommendations for
> >> > > > > > implementations to look at (besides the STM32 one that is
> >> linked in
> >> > > the
> >> > > > > > docs), resources to read (any blog posts from when you ported
> >> SDIO)
> >> > > or
> >> > > > > > advice in general? It would be much appreciated.
> >> > > > > >
> >> > > > > > Thank you,
> >> > > > > > Matteo
> >> > > > > >
> >> > > > > > On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <
> >> matteo.golin@gmail.com>
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > > Got another response from my earlier request to Raspberry Pi
> >> > > through
> >> > > > > > their
> >> > > > > > > website:
> >> > > > > > >
> >> > > > > > > Hi Matteo
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >> Thanks for getting in touch. We don't actually have any
> more
> >> > > > > > >> documentation that we can release on this. My usual
> >> recommendation
> >> > > > is
> >> > > > > > for
> >> > > > > > >> SW people to take a look at the Linux drivers to get a
> closer
> >> > > > > > understanding
> >> > > > > > >> of how the HW works. Not ideal, but the best I can offer.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > So I guess everyone is telling us the same thing!
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <
> tomek@cedro.info>
> >> > > wrote:
> >> > > > > > >
> >> > > > > > >> Sure! Public now :-)
> >> > > > > > >> Tomek
> >> > > > > > >>
> >> > > > > > >> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <
> >> > > matteo.golin@gmail.com
> >> > > > >
> >> > > > > > >> wrote:
> >> > > > > > >> >
> >> > > > > > >> > I have populated the RPi 4B project with some starting
> >> issues to
> >> > > > > > tackle
> >> > > > > > >> for
> >> > > > > > >> > the 4B implementation. I see that the project is marked
> as
> >> > > > private;
> >> > > > > is
> >> > > > > > >> > there any way to make it visible to potential
> contributors
> >> just
> >> > > > > > visiting
> >> > > > > > >> > the GitHub page? I think if they can see a list of issues
> >> in one
> >> > > > > place
> >> > > > > > >> when
> >> > > > > > >> > they go to the page it might help.
> >> > > > > > >> >
> >> > > > > > >> > Thanks,
> >> > > > > > >> > Matteo
> >> > > > > > >> >
> >> > > > > > >> > On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <
> >> tomek@cedro.info>
> >> > > > > wrote:
> >> > > > > > >> >
> >> > > > > > >> > > Thank you Linguini, good luck and have fun! :-)
> >> > > > > > >> > > Tomek
> >> > > > > > >> > >
> >> > > > > > >> > > On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <
> >> > > > > matteo.golin@gmail.com
> >> > > > > > >
> >> > > > > > >> > > wrote:
> >> > > > > > >> > > >
> >> > > > > > >> > > > To update the community, we've been told by Gordon
> >> that the
> >> > > Pi
> >> > > > > > >> Foundation
> >> > > > > > >> > > > doesn't have any documentation for the chip beyond
> >> what was
> >> > > > > > written
> >> > > > > > >> in
> >> > > > > > >> > > the
> >> > > > > > >> > > > peripheral datasheet. Broadcom themselves has written
> >> the
> >> > > > Linux
> >> > > > > > >> drivers
> >> > > > > > >> > > and
> >> > > > > > >> > > > Raspberry Pi has only made some slight bug fixes,
> etc.
> >> We've
> >> > > > > been
> >> > > > > > >> > > suggested
> >> > > > > > >> > > > to read the source to discover undocumented
> >> > > > > > registers/configuration
> >> > > > > > >> > > options.
> >> > > > > > >> > > >
> >> > > > > > >> > > > I plan to still continue with the port until the
> >> feature set
> >> > > > on
> >> > > > > > >> NuttX is
> >> > > > > > >> > > > equal or greater to what is available on QNX. I at
> >> least
> >> > > want
> >> > > > to
> >> > > > > > get
> >> > > > > > >> > > > Ethernet and some graphics running after the base
> >> peripheral
> >> > > > set
> >> > > > > > >> (I2C,
> >> > > > > > >> > > SPI,
> >> > > > > > >> > > > UART) are supported.
> >> > > > > > >> > > >
> >> > > > > > >> > > > Matteo
> >> > > > > > >> > > >
> >> > > > > > >> > > > On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <
> >> > > > > > >> matteo.golin@gmail.com>
> >> > > > > > >> > > wrote:
> >> > > > > > >> > > >
> >> > > > > > >> > > > > Very interesting Sebastian. I got that impression
> >> from
> >> > > > > Broadcom
> >> > > > > > >> when I
> >> > > > > > >> > > was
> >> > > > > > >> > > > > initially trying to port NuttX to the Pi. The
> >> inability to
> >> > > > > > submit
> >> > > > > > >> > > forms on
> >> > > > > > >> > > > > their website seems like it might be by design...
> >> > > > > > >> > > > >
> >> > > > > > >> > > > > I'm hopeful the Raspberry Pi Foundation will have
> >> > > something
> >> > > > > more
> >> > > > > > >> for
> >> > > > > > >> > > us to
> >> > > > > > >> > > > > work with, they seem more positive to FOSS.
> >> Otherwise I
> >> > > will
> >> > > > > > still
> >> > > > > > >> > > continue
> >> > > > > > >> > > > > with reverse engineering until at least the point
> >> where
> >> > > the
> >> > > > > > >> > > functionality
> >> > > > > > >> > > > > driver-wise is on par with QNX.
> >> > > > > > >> > > > >
> >> > > > > > >> > > > > On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <
> >> > > > tomek@cedro.info>
> >> > > > > > >> wrote:
> >> > > > > > >> > > > >
> >> > > > > > >> > > > >> James Dougherty contacted us with Gordon
> >> Hollingworth
> >> > > from
> >> > > > > > >> Raspberry
> >> > > > > > >> > > > >> Pi Foundation recently :-) We are waiting for
> >> response
> >> > > :-)
> >> > > > I
> >> > > > > > >> really
> >> > > > > > >> > > > >> hope we can get some sort of documentation and/or
> >> code
> >> > > > > samples
> >> > > > > > to
> >> > > > > > >> > > > >> write high quality NuttX port for the big
> >> raspberries :-)
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >> Open-Source matters even more in this crazy world.
> >> Thanks
> >> > > > for
> >> > > > > > >> > > > >> interesting article Sebastien! Personally I think
> we
> >> > > should
> >> > > > > > >> focus only
> >> > > > > > >> > > > >> on vendors that support Open-Source. What is the
> >> reason
> >> > > for
> >> > > > > > >> bumping
> >> > > > > > >> > > > >> sales for companies that in the end can sue you
> for
> >> > > > > reversing?
> >> > > > > > :D
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >> Have a good day folks :-)
> >> > > > > > >> > > > >> Tomek
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >> On Sun, Aug 31, 2025 at 10:15 AM Sebastien
> Lorquet <
> >> > > > > > >> > > sebastien@lorquet.fr>
> >> > > > > > >> > > > >> wrote:
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > Hello,
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > I just found this interesting document:
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >>
> >> > > > > > >> > >
> >> > > > > > >>
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >>
> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > In a summary, if you expect anything cool from
> >> > > broadcom:
> >> > > > > > dont.
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > go go go reverse engineering!
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > Sebastien
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> >
> >> > > > > > >> > > > >> > On 8/29/25 15:37, Tomek CEDRO wrote:
> >> > > > > > >> > > > >> > > 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <
> >> > > > > > >> tomek@cedro.info>
> >> > > > > > >> > > wrote:
> >> > > > > > >> > > > >> > >> I just asked question at #asfinfra / slack,
> >> maybe
> >> > > > > someone
> >> > > > > > >> can
> >> > > > > > >> > > help
> >> > > > > > >> > > > >> > >> there or recommend someone who can, waiting
> for
> >> > > > response
> >> > > > > > :-)
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >> For a good start you can contact Broadcom and
> >> > > > > RaspberryPi
> >> > > > > > >> > > Foundation,
> >> > > > > > >> > > > >> > >> introduce yourself as Apache NuttX RTOS
> >> developer
> >> > > that
> >> > > > > > want
> >> > > > > > >> to
> >> > > > > > >> > > port
> >> > > > > > >> > > > >> > >> NuttX to rPI boards, and just ask if
> >> DataSheets are
> >> > > > > > >> available
> >> > > > > > >> > > :-) We
> >> > > > > > >> > > > >> > >> will know then first hand if this is possible
> >> or are
> >> > > > > there
> >> > > > > > >> any
> >> > > > > > >> > > > >> > >> problems / requirements :-)
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >> You can ask for 4B and probably Zero-2W SoC
> >> > > > > documentation
> >> > > > > > >> these
> >> > > > > > >> > > seems
> >> > > > > > >> > > > >> > >> most popular nowadays :-)
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >> Thanks :-)
> >> > > > > > >> > > > >> > >> Tomek
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin
> <
> >> > > > > > >> > > matteo.golin@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 <
> >> > > > > > >> tomek@cedro.info>
> >> > > > > > >> > > > >> wrote:
> >> > > > > > >> > > > >> > >>>
> >> > > > > > >> > > > >> > >>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo
> >> Golin <
> >> > > > > > >> > > > >> matteo.golin@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
> >> > > > > > >> > > > >> > >>>>
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >>
> >> > > > > > >> > > > >> > >> --
> >> > > > > > >> > > > >> > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >> > > > > > >> > > > >> > >
> >> > > > > > >> > > > >> > >
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >> --
> >> > > > > > >> > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >> > > > > > >> > > > >>
> >> > > > > > >> > > > >
> >> > > > > > >> > >
> >> > > > > > >> > >
> >> > > > > > >> > >
> >> > > > > > >> > > --
> >> > > > > > >> > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >> > > > > > >> > >
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >> --
> >> > > > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >> > > > > > >>
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >>
> >>
> >>
> >> --
> >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >>
> >
>

Re: RPI 4B Roadmap

Posted by Ian Fink <ia...@mac.com.INVALID>.
I am not sure if this will help with a lower-half of a NuttX driver, but this guy fooled around with bare metal programming on the RPi4 and had a graphics part of his dev experiments:

https://www.rpi4os.com/ <https://www.rpi4os.com/>

His code is on GitHub and is under a CC license.  I have not looked at it, but it might be worth a gander.

https://github.com/babbleberry/rpi4-osdev

Cheers,
Ian

> On Nov 5, 2025, at 3:48 PM, Matteo Golin <ma...@gmail.com> wrote:
> 
> Hi all,
> 
> Despite a relatively small bug with transfer size limits, the RPi4B microSD
> card support is basically done. This is largely in part to how simple it is
> on NuttX to write a lower-half SDIO implementation and have things just
> work, which is incredible :)
> 
> I now (ambitiously) want to set my eyes on graphics. It turns out that
> rendering with a framebuffer is actually quite easy, but very CPU
> intensive. I'm going to need to figure out how to get at the GPU properly. *My
> question is: *is anyone familiar with examples on how to implement the
> necessary "lower-half" for the NuttX graphics library? I.e. what
> functions/drivers I would need to get written to allow the basic windowing
> display manager & LVGL to work on the HDMI outputs of the Pi? I have
> briefly read the docs about the window manager and saw that there is a
> framebuffer char driver that can be implemented, but I'm not sure how well
> that scales to decent graphics. I suppose this is relatively uncharted
> territory on an RTOS designed mainly with LCDs in mind as the only graphics
> (?). If anyone has implemented graphics support for a device before and can
> let me know a few source files to look at, that would be great!
> 
> My main goal is essentially to get decently fast graphics going, since once
> that's done and some USB HID device support is set up, I can port DOOM to
> NuttX :)
> 
> Thanks,
> Matteo
> 


Re: RPI 4B Roadmap

Posted by spudaneco <sp...@gmail.com>.
Hi, Matteo,I used to know the frame buffer logic well.  I wrote most of the old X style frame buffer logic and have always had an intest in that..  I don't know what the LVGVL users and Xiaomi have changed, so I am out of date,All that being said, I would be interested in helping out in any way possible.GregSent from my Galaxy
-------- Original message --------From: Matteo Golin <ma...@gmail.com> Date: 05/11/25  3:49 pm  (GMT-06:00) To: dev@nuttx.apache.org Subject: Re: RPI 4B Roadmap Hi all,Despite a relatively small bug with transfer size limits, the RPi4B microSDcard support is basically done. This is largely in part to how simple it ison NuttX to write a lower-half SDIO implementation and have things justwork, which is incredible :)I now (ambitiously) want to set my eyes on graphics. It turns out thatrendering with a framebuffer is actually quite easy, but very CPUintensive. I'm going to need to figure out how to get at the GPU properly. *Myquestion is: *is anyone familiar with examples on how to implement thenecessary "lower-half" for the NuttX graphics library? I.e. whatfunctions/drivers I would need to get written to allow the basic windowingdisplay manager & LVGL to work on the HDMI outputs of the Pi? I havebriefly read the docs about the window manager and saw that there is aframebuffer char driver that can be implemented, but I'm not sure how wellthat scales to decent graphics. I suppose this is relatively unchartedterritory on an RTOS designed mainly with LCDs in mind as the only graphics(?). If anyone has implemented graphics support for a device before and canlet me know a few source files to look at, that would be great!My main goal is essentially to get decently fast graphics going, since oncethat's done and some USB HID device support is set up, I can port DOOM toNuttX :)Thanks,MatteoOn Wed, Oct 22, 2025 at 12:32 PM Matteo Golin <ma...@gmail.com>wrote:> Thanks Tomek! That would be a good resource.>> On Wed, Oct 22, 2025 at 7:29 AM Tomek CEDRO <to...@cedro.info> wrote:>>> OpenBSD 7.8 has been just released and it has official support for rPI>> 5 with all sorts of peripherals.. maybe this is the new source to look>> for drivers code? :-)>>>> https://ftp.openbsd.org/pub/OpenBSD/7.8/arm64/INSTALL.arm64>>>> https://cvsweb.openbsd.org/src/>>>> Have a good day :-)>> Tomek>>>> On Tue, Sep 16, 2025 at 5:22 PM Matteo Golin <ma...@gmail.com>>> wrote:>> >>> > Thanks Alan! Maybe I will reach out to Arasan, could have more luck than>> > with Broadcom, but I doubt it.>> >>> > I'll take a look at these documents!>> >>> > Thanks again,>> > Matteo>> >>> > On Tue, Sep 16, 2025, 11:00 AM Alan C. Assis <ac...@gmail.com> wrote:>> >>> > > Hi Matteo,>> > >>> > > Please that a look:>> > > https://www.arasan.com/products/sd-emmc/sdio-3-0-device/>> > >>> > > There is an option to Download (request) the Datasheet from that>> page, but>> > > you can access it directly here:>> > >>> > >>> https://www.arasan.com/wp-content/uploads/2016/05/3MCR-Total-IP-Solution.pdf>> > >>> > > This document is more about the IP core details, but could give you>> more>> > > understanding about internal block of the SDIO controller (its FIFO,>> > > initialization diagram, etc)>> > >>> > > You can also try to find the original>> > > SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in>> Raspberry>> > > documentation.>> > >>> > > BR,>> > >>> > > Alan>> > >>> > >>> > >>> > > On Tue, Sep 16, 2025 at 11:17 AM Matteo Golin <ma...@gmail.com>> >>> > > wrote:>> > >>> > > > Hi Alan,>> > > >>> > > > Thank you for the tips! Yes, SDIO looks pretty involved compared to>> SPI>> > > or>> > > > I2C. I'll try reading the specification like you suggested.>> > > >>> > > > The BCM2711 datasheet doesn't document it at all, however the EMMC>> > > > interface is supposedly the exact same from the BCM2835 and the>> registers>> > > > there are at least documented. All I know is that it is using an>> > > interface>> > > > by Arasan. I'm not as familiar with NuttX, but if this at all looks>> like>> > > > something that's already been supported, please let me know. In the>> > > > meantime, I'll look through the SDIO implementations to check:>> > > >>> > >>> https://www.raspberrypi.org/app/uploads/2012/02/BCM2835-ARM-Peripherals.pdf>> > > > (page 65)>> > > >>> > > > Thanks again!>> > > > Matteo>> > > >>> > > > On Tue, Sep 16, 2025 at 9:49 AM Alan C. Assis <ac...@gmail.com>>> wrote:>> > > >>> > > > > HI Matteo,>> > > > >>> > > > > I implemented the SDIO support for LPC43 some years ago and what>> helped>> > > > me>> > > > > most was reading the SD/MMC specification, the LPC43 reference>> manual>> > > and>> > > > > enabling the NuttX SD/MMC debug messages.>> > > > >>> > > > > There are many details to take care of: clock enable for the>> > > controller,>> > > > > interrupts, pins configuration, etc.>> > > > >>> > > > > Unfortunately, the BCM2711 doc is not good. You can start>> verifying the>> > > > > registers, maybe it is based on some SD/MMC core IP already>> supported>> > > by>> > > > > NuttX.>> > > > >>> > > > > BR,>> > > > >>> > > > > Alan>> > > > >>> > > > >>> > > > >>> > > > > On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin <>> matteo.golin@gmail.com>>> > > > > wrote:>> > > > >>> > > > > > Hi everyone,>> > > > > >>> > > > > > Now that I2C has been tackled, I am moving on to SDIO>> interfaces so>> > > the>> > > > > SD>> > > > > > card can be interacted with from NuttX.>> > > > > >>> > > > > > The NuttX SDIO documentation is a little bare, and I'm not the>> most>> > > > > > familiar with SDIO. Does anyone have any recommendations for>> > > > > > implementations to look at (besides the STM32 one that is>> linked in>> > > the>> > > > > > docs), resources to read (any blog posts from when you ported>> SDIO)>> > > or>> > > > > > advice in general? It would be much appreciated.>> > > > > >>> > > > > > Thank you,>> > > > > > Matteo>> > > > > >>> > > > > > On Fri, Sep 5, 2025, 11:15 AM Matteo Golin <>> matteo.golin@gmail.com>>> > > > > wrote:>> > > > > >>> > > > > > > Got another response from my earlier request to Raspberry Pi>> > > through>> > > > > > their>> > > > > > > website:>> > > > > > >>> > > > > > > Hi Matteo>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >> Thanks for getting in touch. We don't actually have any more>> > > > > > >> documentation that we can release on this. My usual>> recommendation>> > > > is>> > > > > > for>> > > > > > >> SW people to take a look at the Linux drivers to get a closer>> > > > > > understanding>> > > > > > >> of how the HW works. Not ideal, but the best I can offer.>> > > > > > >>> > > > > > >>> > > > > > > So I guess everyone is telling us the same thing!>> > > > > > >>> > > > > > >>> > > > > > > On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO <to...@cedro.info>>> > > wrote:>> > > > > > >>> > > > > > >> Sure! Public now :-)>> > > > > > >> Tomek>> > > > > > >>>> > > > > > >> On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin <>> > > matteo.golin@gmail.com>> > > > >>> > > > > > >> wrote:>> > > > > > >> >>> > > > > > >> > I have populated the RPi 4B project with some starting>> issues to>> > > > > > tackle>> > > > > > >> for>> > > > > > >> > the 4B implementation. I see that the project is marked as>> > > > private;>> > > > > is>> > > > > > >> > there any way to make it visible to potential contributors>> just>> > > > > > visiting>> > > > > > >> > the GitHub page? I think if they can see a list of issues>> in one>> > > > > place>> > > > > > >> when>> > > > > > >> > they go to the page it might help.>> > > > > > >> >>> > > > > > >> > Thanks,>> > > > > > >> > Matteo>> > > > > > >> >>> > > > > > >> > On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO <>> tomek@cedro.info>>> > > > > wrote:>> > > > > > >> >>> > > > > > >> > > Thank you Linguini, good luck and have fun! :-)>> > > > > > >> > > Tomek>> > > > > > >> > >>> > > > > > >> > > On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin <>> > > > > matteo.golin@gmail.com>> > > > > > >>> > > > > > >> > > wrote:>> > > > > > >> > > >>> > > > > > >> > > > To update the community, we've been told by Gordon>> that the>> > > Pi>> > > > > > >> Foundation>> > > > > > >> > > > doesn't have any documentation for the chip beyond>> what was>> > > > > > written>> > > > > > >> in>> > > > > > >> > > the>> > > > > > >> > > > peripheral datasheet. Broadcom themselves has written>> the>> > > > Linux>> > > > > > >> drivers>> > > > > > >> > > and>> > > > > > >> > > > Raspberry Pi has only made some slight bug fixes, etc.>> We've>> > > > > been>> > > > > > >> > > suggested>> > > > > > >> > > > to read the source to discover undocumented>> > > > > > registers/configuration>> > > > > > >> > > options.>> > > > > > >> > > >>> > > > > > >> > > > I plan to still continue with the port until the>> feature set>> > > > on>> > > > > > >> NuttX is>> > > > > > >> > > > equal or greater to what is available on QNX. I at>> least>> > > want>> > > > to>> > > > > > get>> > > > > > >> > > > Ethernet and some graphics running after the base>> peripheral>> > > > set>> > > > > > >> (I2C,>> > > > > > >> > > SPI,>> > > > > > >> > > > UART) are supported.>> > > > > > >> > > >>> > > > > > >> > > > Matteo>> > > > > > >> > > >>> > > > > > >> > > > On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin <>> > > > > > >> matteo.golin@gmail.com>>> > > > > > >> > > wrote:>> > > > > > >> > > >>> > > > > > >> > > > > Very interesting Sebastian. I got that impression>> from>> > > > > Broadcom>> > > > > > >> when I>> > > > > > >> > > was>> > > > > > >> > > > > initially trying to port NuttX to the Pi. The>> inability to>> > > > > > submit>> > > > > > >> > > forms on>> > > > > > >> > > > > their website seems like it might be by design...>> > > > > > >> > > > >>> > > > > > >> > > > > I'm hopeful the Raspberry Pi Foundation will have>> > > something>> > > > > more>> > > > > > >> for>> > > > > > >> > > us to>> > > > > > >> > > > > work with, they seem more positive to FOSS.>> Otherwise I>> > > will>> > > > > > still>> > > > > > >> > > continue>> > > > > > >> > > > > with reverse engineering until at least the point>> where>> > > the>> > > > > > >> > > functionality>> > > > > > >> > > > > driver-wise is on par with QNX.>> > > > > > >> > > > >>> > > > > > >> > > > > On Sun, Aug 31, 2025, 10:46 AM Tomek CEDRO <>> > > > tomek@cedro.info>>> > > > > > >> wrote:>> > > > > > >> > > > >>> > > > > > >> > > > >> James Dougherty contacted us with Gordon>> Hollingworth>> > > from>> > > > > > >> Raspberry>> > > > > > >> > > > >> Pi Foundation recently :-) We are waiting for>> response>> > > :-)>> > > > I>> > > > > > >> really>> > > > > > >> > > > >> hope we can get some sort of documentation and/or>> code>> > > > > samples>> > > > > > to>> > > > > > >> > > > >> write high quality NuttX port for the big>> raspberries :-)>> > > > > > >> > > > >>>> > > > > > >> > > > >> Open-Source matters even more in this crazy world.>> Thanks>> > > > for>> > > > > > >> > > > >> interesting article Sebastien! Personally I think we>> > > should>> > > > > > >> focus only>> > > > > > >> > > > >> on vendors that support Open-Source. What is the>> reason>> > > for>> > > > > > >> bumping>> > > > > > >> > > > >> sales for companies that in the end can sue you for>> > > > > reversing?>> > > > > > :D>> > > > > > >> > > > >>>> > > > > > >> > > > >> Have a good day folks :-)>> > > > > > >> > > > >> Tomek>> > > > > > >> > > > >>>> > > > > > >> > > > >>>> > > > > > >> > > > >>>> > > > > > >> > > > >> On Sun, Aug 31, 2025 at 10:15 AM Sebastien Lorquet <>> > > > > > >> > > sebastien@lorquet.fr>>> > > > > > >> > > > >> wrote:>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > Hello,>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > I just found this interesting document:>> > > > > > >> > > > >> >>> > > > > > >> > > > >> >>> > > > > > >> > > > >>>> > > > > > >> > >>> > > > > > >>>> > > > > >>> > > > >>> > > >>> > >>> https://fastcode.io/2025/08/30/the-69-billion-domino-effect-how-vmwares-debt-fueled-acquisition-is-killing-open-source-one-repository-at-a-time/>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > In a summary, if you expect anything cool from>> > > broadcom:>> > > > > > dont.>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > go go go reverse engineering!>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > Sebastien>> > > > > > >> > > > >> >>> > > > > > >> > > > >> >>> > > > > > >> > > > >> > On 8/29/25 15:37, Tomek CEDRO wrote:>> > > > > > >> > > > >> > > 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, Aug 28, 2025 at 9:35 PM Tomek CEDRO <>> > > > > > >> tomek@cedro.info>>> > > > > > >> > > wrote:>> > > > > > >> > > > >> > >> I just asked question at #asfinfra / slack,>> maybe>> > > > > someone>> > > > > > >> can>> > > > > > >> > > help>> > > > > > >> > > > >> > >> there or recommend someone who can, waiting for>> > > > response>> > > > > > :-)>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >> For a good start you can contact Broadcom and>> > > > > RaspberryPi>> > > > > > >> > > Foundation,>> > > > > > >> > > > >> > >> introduce yourself as Apache NuttX RTOS>> developer>> > > that>> > > > > > want>> > > > > > >> to>> > > > > > >> > > port>> > > > > > >> > > > >> > >> NuttX to rPI boards, and just ask if>> DataSheets are>> > > > > > >> available>> > > > > > >> > > :-) We>> > > > > > >> > > > >> > >> will know then first hand if this is possible>> or are>> > > > > there>> > > > > > >> any>> > > > > > >> > > > >> > >> problems / requirements :-)>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >> You can ask for 4B and probably Zero-2W SoC>> > > > > documentation>> > > > > > >> these>> > > > > > >> > > seems>> > > > > > >> > > > >> > >> most popular nowadays :-)>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >> Thanks :-)>> > > > > > >> > > > >> > >> Tomek>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >> On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin <>> > > > > > >> > > matteo.golin@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 <>> > > > > > >> tomek@cedro.info>>> > > > > > >> > > > >> wrote:>> > > > > > >> > > > >> > >>>>> > > > > > >> > > > >> > >>>> On Tue, Aug 26, 2025 at 10:05 PM Matteo>> Golin <>> > > > > > >> > > > >> matteo.golin@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>> > > > > > >> > > > >> > >>>>>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >>>> > > > > > >> > > > >> > >> -->> > > > > > >> > > > >> > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info>> > > > > > >> > > > >> > >>> > > > > > >> > > > >> > >>> > > > > > >> > > > >>>> > > > > > >> > > > >>>> > > > > > >> > > > >>>> > > > > > >> > > > >> -->> > > > > > >> > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info>> > > > > > >> > > > >>>> > > > > > >> > > > >>> > > > > > >> > >>> > > > > > >> > >>> > > > > > >> > >>> > > > > > >> > > -->> > > > > > >> > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info>> > > > > > >> > >>> > > > > > >>>> > > > > > >>>> > > > > > >>>> > > > > > >> -->> > > > > > >> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info>> > > > > > >>>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>>>>>>>> -->> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info>>>