> > *It would be nice if it was possible to do* > * something like enable a UART and have it's pin mux setup correctly, but* > * *ALSO* be able to do something like just enable the Tx pin without* > * generating a custom device-tree. Thoughts?* >
Sounds very flexible, and also very complex to implement. If you can pull it off I'd say it would be an excellent addition. On Thu, Sep 4, 2014 at 3:24 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 9/4/2014 3:43 PM, Jason Kridner wrote: > > Charles, > > > > It would be great if you could take a look at this and see if it is > > suitable for you and if I'm headed down the right path. There is a > > pre-built linux-image package and if you use one of Robert's recent test > > images, you can simply use 'dpkg -i XXX.deb && reboot' to install it. > > This is great news, and what I was hoping for when I started working on > a universal device-tree overlay! > > > It would be great if config-pin was updated to work with this. Right > now, I > > have commented out the exit statement where cape-universal isn't > detected. > > I'll see if I can find some spare time soon to test and get some better > checks into the config-pin script. > > I've also been thinking config-pin should perhaps be something other > than a bash script for speed (perhaps Python?), but I'm not sure if it's > the shell or sysfs that's so sluggish when setting up a large number of > pins. Using something other than bash would also make it possible to > factor some of the pin intelligence into user-mode (instead of kernel > code or the device-tree). It would be nice if it was possible to do > something like enable a UART and have it's pin mux setup correctly, but > *ALSO* be able to do something like just enable the Tx pin without > generating a custom device-tree. Thoughts? > > Ultimately, config-pin should probably get turned into something that > can generate DT changesets and ask the kernel to apply them. I > currently have no idea what this interface is going to look like. > > -- > 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. > 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. For more options, visit https://groups.google.com/d/optout.
