my bad, I missed a necessary point there. Basically you need to change status = "disabled"; to status = "okay";
Then it is my best guess that everything you need to use uio_pruss will be loaded correctly. On Tue, Nov 10, 2015 at 5:17 PM, William Hermans <[email protected]> wrote: > So a bit more information. Here is the device tree overlay i've loaded > > > /dts-v1/; > /plugin/; > > / { > compatible = "ti,beaglebone", "ti,beaglebone-black"; > > /* identification */ > part-number = "pruss_enable"; > version = "00A0"; > > fragment@0 { > target = <&pruss>; > __overlay__ { > status = "okay"; > > }; > }; > > }; > > So, the target is &pruss. Looking in the am335x-boneblack.dts file there > is no mention of &pruss. But this file does have two includes at the top. > > #include "am33xx.dtsi" > #include "am335x-bone-common.dtsi" > > Searching through am33xx.dtsi for "pruss" turns up this fragment. > > pruss: pruss@4a300000 { > compatible = "ti,pruss-v2"; > ti,hwmods = "pruss"; > ti,deassert-hard-reset = "pruss", "pruss"; > reg = <0x4a300000 0x080000>; > ti,pintc-offset = <0x20000>; > interrupt-parent = <&intc>; > status = "disabled"; > interrupts = <20 21 22 23 24 25 26 27>; > }; > > So, I believe you have a couple options. First, you can create an overlay > like file, and #include it in am335x-boneblack.dts. IN order to do this you > will need to copy your current dtbo file, decompile it, edit the file, etc > ,etc, then recompile the file. Back up, and move the old > am335x-boneblack.dts file out of the way. Replace with your newly compiled > file. The second option is pretty much the same thing, but your change the > am335x-boneblack.dtbo file directly. > > Anyway, there is actually a third option. Get rid of that 3.14.x kernel, > and use a 4.x kernel . . . a kernel that can actually use cape manager. > > > On Tue, Nov 10, 2015 at 4:29 PM, William Hermans <[email protected]> > wrote: > >> I've just started learning about uio myself, but my guess is that you've >> loaded the uio_pruss module manually. Yes ? So with a kernel that has cape >> manager . . . >> >> $ uname -r >> 4.1.9-bone-rt-r16 >> $ lsmod |grep pru >> >> $ sudo sh -c "echo 'pru_enable' > >> /sys/devices/platform/bone_capemgr/slots" >> $ lsmod |grep pru >> uio_pruss 4143 0 >> uio 8006 2 uio_pruss,uio_pdrv_genirq >> >> So, anyway, the module you're missing is *uio_pdrv_genirq* but this >> minimal generic driver module needs parameters when loaded. That much I >> know, but what I do not know is how to load that module. Well not exactly. >> That, and I'm not sure how to dissect the Linux Image I have now to find >> out . . . >> >> On Tue, Nov 10, 2015 at 2:50 PM, Tou Parish <[email protected]> >> wrote: >> >>> I've got a slight issue-- >>> >>> On my hardware: >>> >>> root@localhost:/sys/class/uio# uname -r >>> 3.14.54-ti-rt-r77 >>> >>> root@localhost:/sys/class/uio# lsmod >>> Module Size Used by >>> usb_f_ecm 7909 1 >>> g_ether 1802 0 >>> usb_f_rndis 17719 2 g_ether >>> u_ether 10156 3 usb_f_ecm,g_ether,usb_f_rndis >>> libcomposite 38699 3 usb_f_ecm,g_ether,usb_f_rndis >>> *uio_pruss 2372 0* >>> omap_serial_rs485 16943 0 >>> root@localhost:/sys/class/uio# >>> >>> And finally... >>> >>> root@localhost:/sys/class/uio# ls >>> root@localhost:/sys/class/uio# >>> >>> So after installing uio_pruss nothing shows up in the uio directory for >>> it. >>> >>> Any ideas? >>> >>> Thanks >>> >>> -- >>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
