Converting a 7i76e config to 7c81/7i76 pair

Further to that, which maybe of interest, the Raspbian team are still working on a Bookworm release.
I guess that they patch the kernel for the device overlay tree which is needed to need to get the whole spi overlay loaded.

I have spi-bcm2835 loading on boot now. I still don't have the /dev/spi0.0 and/or /dev/spi0.1 being created.
I don't find a module spidev. It looks like it should be a kernel module but some of the info sounds like it may be a user module for talking to spi-bcm2835.

Cant do this anymore bye all wrote:

I was under the impression that the hm2-rpspi required a entry in the dev folder for spi and the Hal gpio driver was a different beast.
 

hm2-rpspi does not require the SPI  device driver (or GPIO)
but mesaflash does require the SPI device driver

From the info I found, I could be wrong, the mainline kernel doesn’t support device tree overlays, or the mechanism required to get an spi device entry in /dev. It would seem this a patch that the raspbian team applies.
So I’m thinking that until the raspbian team has a kernel for bookworm, the Raspberry Pi will require Bullseye for any board that requires SPI to operate.
Bookworm should, in theory, be fine for Ethernet devices.
Now I could be totally wrong regarding this.

Sebastian has hm2_rpspi running under Debian Bookworm. I succeeded in getting spi-bcm2835 to load on boot but I still can't create the /dev/spi0.0 and /dev/spi0.1 devices on Bookworm. The kernel on Bookworm compiles the devices that would normally be loaded in the device tree as kernel modules. So, I am just trying to find out what piece or pieces are either missing or not loaded.
I just think it would be great to be able to run mesaflash on the 7c81 on Bookworm.

The issue is and if you at this post forum.linuxcnc.org/38-general-linuxcnc-q...pair?start=10#279252
it explains why the device tree is not loading. CONFIG_OF_CONFIGFS=y is the important part.
Later in that post I checked the raspbian kernel config from my running RP400 for that option and it is there, but when I downloaded a RT arm64 kernel from debian and run grep on the kernel config it wasn't there. If the option was available it would have an N instead of Y.
Yep I had the kernel modules loading but no /dev entries under bookworm.

This explains the device tree far better than I could
docs.kernel.org/devicetree/overlay-notes.html

What lead me down this hole was when I was messing around with Linuxcnc-RIO which uses an ICE40 fpga and communicates via SPI. It would just not work under Debain Bookworm, but was fine with Bullseye. I don't want to recall how much time I spent.......and I only found out about the info I posted about above yesterday.