Plans for adding support into mainline?

Presentation about the board uses “open source” phrase very often. Some may say that too often but that’s the other story.

Some people, outside of Radxa company, already have boards. So far no one complained about lack of kernel source which they should get access to due to GPLv2 license.

Public source code release is promised in “Q1 2025” so up to two months and we can take a look.

But that’s vendor kernel. 6.1, LTS, not up to date, vendor kernel. With whatever makes board run inside.

Who will take care of adding support for the board in mainline kernel? Radxa? Cixtech? Someone paid by one of them? Or random people from community in their spare time?

What about upstream edk2-platforms? Same question set.

I do not ask about FreeBSD support even cause it may be too early for it.

2 Likes

Just a quick note: whole China is on holiday since yesterday so please don’t expect ‘official’ answers right now (or even till Lantern Festival)

2 Likes

It is currently the Chinese New Year holiday, all work and responses are delayed. They sent the first batch of boards to early birds and developers in advance so that they can get familiar with the hardware in advance.

Who will take care of adding support for the board in mainline kernel? Radxa? Cixtech? Someone paid by one of them? Or random people from community in their spare time?

CIX tech said in their presentation that they will start upstreaming EDK2 and Linux kernel in the first half of 2025. You need a translator to read this from their website.

Translated version:

As we all know, for a successful development kit, open source support is essential. Cix technology will actively embrace the community and contribute to open source. For the newly released Radxa Orion O6 development kit, Cix technology will promote the open source and upstream support of EDK2 firmware and Linux kernel in the first half of 2025.

In fact, this board can already run the upstream kernel and distro well, just like the x86 platform, boot and flash the system through a flash disk. Personally, I am more concerned about the performance of video codec and GPU, so I decided to stay in BSP/vendor kernel for a while.

1 Like

There’s no additional GPU on the PCIe bus? Framebuffer output?

Also curious why lspci output with distro vs. BSP kernel shows mismatching vendor IDs (with Cix/Radxa image I get 1f6c (registered for ’ CIX Technology (Shanghai) Co., Ltd’) while your output shows the Cadence ID (from them the whole PCie subsystem probably has been licensed).

Yes. It’s simple-drm out.

BSP kernel has CONFIG_PHY_CIX_PCIE=y, which i think they will upstream this driver.

Regarding source availability, for having myself been through that process of distributing hardware and having to package sources in a downloadable and buildable form in the past, I can say that it can take an amazing amount of work just to package something you’re not ashamed of. During development you can have dirty processes, stuff that only works on your local machine, ugly scripts quickly done an afternoon etc that you cannot even expose. We’ve all seen some build scripts with hard-coded NFS or TFTP server addresses for example. That’s a pain to go through, but it must be done and takes time. Let’s for now trust them that this will really happen. If it does not we can start to ask, but for now everything’s more or less on time so let’s not annoy everyone on the grounds of opensource claims, it just discourages vendors from doing so next time!

Also it makes sense to debug before mainlining. It often takes a long time to get patches accepted into mainline projects (kernel, boot loaders, etc), and sometimes they must even be completely re-architected. Thus better provide something that requires few future changes at once.

Regarding FreeBSD, I know Radxa gave a few boards away to select developers. I also presented another one I know who could be helpful.

I really think that Radxa is acting well with available resources, let’s not disturb their work, it would only delay things.

3 Likes