12-01-2017, 06:38 PM
Thanks Joe.
In re the rock64, the RK3328 seems to be the correct bit of smart sand. And I wasn't really concerned about the 7i92 as I expect it can have an ipv4 address assigned, and a smart switch used. What I would like to see happen is the rpspi.ko driver from linuxcnc ported to the rock64, as thats a much faster machine control interface. I have a pi writing 32 bit packets to a Mesa 7i90HD at 41 megabaud, and reading the 7i90HD's responses at 25 megabaud right now, But the pi's penchant for throwing away keyboard and mouse events absolutely kills any safety margin by leaving the machine jogging in which ever direction it was moving until it crashes into something, possibly breaking things.
The rock64 doesn't suffer from this design flaw, but its stock spi bus is the kernels version and that infamously very badly broken.
Nobody in media uses spi, so its not getting any TLC at all.
Heck, I've built 2 or 3 kernels, on the rock64, takes a bit over an hour. But I've found zero docs of how to make it boot a different kernel even if its been installed by the makefile. If I can make, install and boot one of the latest rt kernels, then I might take a swing at making this spi driver run on the rock64. It will take switching the header files out for the ones for the RK3328, AND the wholesale excising of a few paragraphs of code designed to keep it from running on anything but a pi-2 or pi-3.
But there's little use of working on the driver until I have a way worked out to make it run the realtime kernel.
Questions about that, which I've asked here over the last couple months, have simply been ignored, yet here is a tiny card that could put both the pi's and the best of the beagle bone blacks out to pasture for good.
Why the secrecy? Do they not want folks to develop anything but movie players on it?
Thanks Joe, and take care of you and yours.
In re the rock64, the RK3328 seems to be the correct bit of smart sand. And I wasn't really concerned about the 7i92 as I expect it can have an ipv4 address assigned, and a smart switch used. What I would like to see happen is the rpspi.ko driver from linuxcnc ported to the rock64, as thats a much faster machine control interface. I have a pi writing 32 bit packets to a Mesa 7i90HD at 41 megabaud, and reading the 7i90HD's responses at 25 megabaud right now, But the pi's penchant for throwing away keyboard and mouse events absolutely kills any safety margin by leaving the machine jogging in which ever direction it was moving until it crashes into something, possibly breaking things.
The rock64 doesn't suffer from this design flaw, but its stock spi bus is the kernels version and that infamously very badly broken.
Nobody in media uses spi, so its not getting any TLC at all.
Heck, I've built 2 or 3 kernels, on the rock64, takes a bit over an hour. But I've found zero docs of how to make it boot a different kernel even if its been installed by the makefile. If I can make, install and boot one of the latest rt kernels, then I might take a swing at making this spi driver run on the rock64. It will take switching the header files out for the ones for the RK3328, AND the wholesale excising of a few paragraphs of code designed to keep it from running on anything but a pi-2 or pi-3.
But there's little use of working on the driver until I have a way worked out to make it run the realtime kernel.
Questions about that, which I've asked here over the last couple months, have simply been ignored, yet here is a tiny card that could put both the pi's and the best of the beagle bone blacks out to pasture for good.
Why the secrecy? Do they not want folks to develop anything but movie players on it?
Thanks Joe, and take care of you and yours.
