> > *After further testing, if you create a /dev/uio directory before* > * trying to load a uio driver (like the PRU driver), everything works* > * fine. Interestingly, there are *NO* symlinks actually generated in* > * the /dev/uio directory, but the simple fact that it exists seems to be* > * enough to keep the systemd-udevd processes from chewing up tons of CPU* > * until they get killed.* > > * So the solution seems to be one of:* > > * * Create a /dev/uio directory* > > * * Remove the SYMLINK line from /etc/udev/uio.rules* > > * I'm not enough of a udev guru to know which is the better option, but* > * removing or commenting the SYMLINK line in uio.rules seems like the* > * better choice, since there aren't any symlinks generated anyway.* >
I'm not an expert Charles, but I think the symlink should be removed from the udev rules file, and when various drivers that require uio are installed via *however* the "vendor" needs to include their own *.rules file. That's how it's done already in many cases. As creating a directory structure in the /dev/ directory tree probably is not a good idea if it never gets used, or even just isn't installed. Because it could be a potential cause of confusion. On Thu, Apr 21, 2016 at 7:01 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 4/21/2016 7:41 PM, Charles Steinkuehler wrote: > > On 4/21/2016 7:32 PM, Robert Nelson wrote: > >> On Thu, Apr 21, 2016 at 7:25 PM, Charles Steinkuehler < > char...@steinkuehler.net > >> <mailto:char...@steinkuehler.net>> wrote: > >> > >> and of course, i never added who pinged me on this, when i pushed the > change... > >> > >> > https://github.com/RobertCNelson/omap-image-builder/commit/47f982cf2896664dacd21126cf4381b078b94d15 > > > > Well things are _mostly_ working. The /dev/uio[0-7] entries are > > created, they apparently just don't get symlinked to wherever it is > > the first line in the uio.rules file is trying to put them. > > > > Any ideas what this was all about? > > > > Is it OK to just comment out the SYMLINK line? > > After further testing, if you create a /dev/uio directory before > trying to load a uio driver (like the PRU driver), everything works > fine. Interestingly, there are *NO* symlinks actually generated in > the /dev/uio directory, but the simple fact that it exists seems to be > enough to keep the systemd-udevd processes from chewing up tons of CPU > until they get killed. > > So the solution seems to be one of: > > * Create a /dev/uio directory > > * Remove the SYMLINK line from /etc/udev/uio.rules > > I'm not enough of a udev guru to know which is the better option, but > removing or commenting the SYMLINK line in uio.rules seems like the > better choice, since there aren't any symlinks generated anyway. > > -- > Charles Steinkuehler > char...@steinkuehler.net > > -- > 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 beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/57198616.6050505%40steinkuehler.net > . > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpvX3CzLTTiw73yQMaFRq%2Ben80Tsw%3DRxznqpcOrNThGHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
