I read through this thread and noted that the PRU isn't working yet? I ended up compiling a 4.9.0-rc6 kernel, although not the ti variant, and was able to get the PRU working with the old UIO driver. I was hoping at some point to switch to the new remoteproc driver, but reading through this thread, it seems as its not ready? I know this thread is about a month old now, but is my understanding accurate? Or have things progressed to a working state? If my understanding is accurate, how much more work does the remoteproc driver require?
I've even tested the old driver with my code and without any changes, it was performing like a champ. My only problem now is I haven't been able to get the USB gadget interface to work. Everything seems to go fine up until I attempt: ls /sys/class/udc > UDC # enable my gadget At this point, I get a crash around line 620 in f_hid.c in usb/gadget/function . At least the crash is in alloc_ep_req. It says, if I'm reading it right, that the in_ep is NULL, which I don't think it is supposed to be or can't be. So I'm not sure what I'm doing wrong that I'm getting a NULL endpoint, but I thought maybe I hadn't configured the kernel quite right for USB. So now that TI has a more "official" 4.9 release, maybe things work there? At any rate, I needed both the USB gadget interface and the PRU to work and eventually am hoping to migrate my code toward remoteproc so I don't have the current issues (I needed various components that didn't seem to be all in one place until 4.9). On Monday, October 31, 2016 at 5:47:06 PM UTC-4, RobertCNelson wrote: > > Hey Everyone, > > Over the weekend, TI imported and tagged there first v4.9.x branch: > > > http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-4.9.y > > > I've added our patchset, overlays are broken past the first i2c > address: (havn't tried with a board plugged in) > > debian@beaglebone:~$ dmesg | grep bone > [ 2.101727] bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,00C0,2516BBBK2626' > [ 2.101753] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > [ 2.101796] bone_capemgr bone_capemgr: Failed to add slot #1 > [ 2.126911] bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,00C0,2516BBBK2626' > [ 2.126940] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > [ 2.126971] bone_capemgr bone_capemgr: Failed to add slot #1 > [ 2.360973] bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,00C0,2516BBBK2626' > [ 2.361012] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > > cpufreq is broken, this should be fixed pretty soon.. > > HDMI-Audio: this is new and went mainline in v4.9.x-rc, fingers > crossed, it should work so please test. ;) ( i finally have a lcd > monitor (with audio) that i can finally test with. .;) ) > > pru: nothing yet.. > > eqep: needs porting.. > > Kernel should hit the apt repo in a day or two, i'll reply to this > message when ready... > > cd /opt/scripts/tools/ > git pull > sudo ./update_kernel.sh --ti-channel --lts-4_9 > > (no rt yet) > > SRC is here: > > https://github.com/beagleboard/linux/tree/4.9 > > https://github.com/beagleboard/linux/commits/4.9 > > The best way to build it is via yakbuild: > > git clone https://github.com/RobertCNelson/yakbuild > cd ./yakbuild/ > cp recipe.sh.v4.9.x.sample recipe.sh > ./build_kernel.sh > > While the dtb's can be built/tested via dtb-rebuilder > > #this is one line.. > git clone -b 4.9-ti https://github.com/RobertCNelson/dtb-rebuilder/ > cd ./dtb-rebuilder/ > make > > status > v4.4.x-ti - still supported and on-going working > v4.1.x-ti - maintenance-only please upgrade to v4.4.x-ti > v3.14.x-ti - maintenance (really eol) > v3.8.13-bone - maintenance, probably never EOL... (i see another gcc6 > patch coming on the horizon). ;) > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/dd7687f5-90ce-4470-b2a4-1544f389b323%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
