For pinmux only, existing tools could be reimplemented or modified, but the real challenge is in the hundreds of possible drivers and their configurations. It would be interesting to see if those could automatically be extracted from a running kernel with symbols. On Wed, Jan 17, 2018 at 6:58 PM Joshua Datko <[email protected]> wrote:
> Hey Jason, > > First of all thanks for all the work (and from many others on this) for > the BeagleBone et. al.! > > This is just my 2c and it's probably worth that much. > > What I would say is that it shouldn't matter that the board uses device > tree or <insert new thing here>. What designers of capes want, I think, is > the ability to configure the beaglebone (or pocket beagle) as they like. > With the device tree, as you've shown, this is how one accomplishes that > task. > > But I'm stumbled through building device tree fragments before and it's a > bit painful. > > What I would suggest is a tool that makes device tree generation easier. > This probably should be a GUI (with scripting option). But as a HW designer > for a cape, if I could click pins on a GUI, set modes, defaults, etc... and > out spit a device tree fragment, I would think that'd be cool. > > I'm also not volunteering to build this :) But if the device tree fragment > is the output, clearly a nicer frontend can be made to produce this. And I > realize there's all sorts of complexity here, I'm just suggest the idea of > a tool to more easily produce device tree fragments. > > Josh > -- https://beagleboard.org/about -- 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/CA%2BT6QPmO-Bt9S9mM48zP6fDcpKRvMAnZdKrsdpEbosA-6QJrrg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
