Ok, stumped with something.
There is a "not for regular use" branch v2.1-dev-dt in which there is a kernel module which does not write directly to the hardware. It appears to be happy on 64 bit, too, so long as you don't want the PWM waveform to drive the network clock. (I have no idea why that isn't working, but it isn't - there are no errors being reported to the kernel module to suggest it's not happening, and the pin is correctly configured as ALT5!)
Anyway, putting all that to one side...
I have been experimenting with that version on a Pi5 - at this stage, by manually loading the econet-gpio-v2.dts overlay (compiled into a .dtbo, obvs) but with no HAT plugged in. On other platforms, the module happily loads and probe()s when I load the overlay. On the Pi 5 - which seems to put the overlay in place happily, the module loads but it would appear probe() is never called at all.
Anyone any ideas why??
(And before anyone looks at the v2.0 stock kernel module which doesn't implement probe() properly at all, that's all changed...)
The module in this branch is not for regular use. It has known problems with overruns even on a Pi4, which I am hoping to have a look at in due course...
All help welcomed,
Thanks,
C.
There is a "not for regular use" branch v2.1-dev-dt in which there is a kernel module which does not write directly to the hardware. It appears to be happy on 64 bit, too, so long as you don't want the PWM waveform to drive the network clock. (I have no idea why that isn't working, but it isn't - there are no errors being reported to the kernel module to suggest it's not happening, and the pin is correctly configured as ALT5!)
Anyway, putting all that to one side...
I have been experimenting with that version on a Pi5 - at this stage, by manually loading the econet-gpio-v2.dts overlay (compiled into a .dtbo, obvs) but with no HAT plugged in. On other platforms, the module happily loads and probe()s when I load the overlay. On the Pi 5 - which seems to put the overlay in place happily, the module loads but it would appear probe() is never called at all.
Anyone any ideas why??
(And before anyone looks at the v2.0 stock kernel module which doesn't implement probe() properly at all, that's all changed...)
The module in this branch is not for regular use. It has known problems with overruns even on a Pi4, which I am hoping to have a look at in due course...
All help welcomed,
Thanks,
C.
Statistics: Posted by cr12925 — Fri Mar 22, 2024 6:11 pm