On 9/23/2015 3:59 PM, Rick Mann wrote: > > Thanks, Charles, that's helpful. I may offer a patch to the docs > with this explanation, would you be okay with that?
Sure! PRs are always welcome! > In my case, I'm developing a custom cape, and intending to support > only 4.1+, and don't mind writing a DTB. In fact, I may have to, > since my cape has an audio CODEC on it and I need to enable McASP. > > Is that assessment correct, or should I go the route of using a > universal overlay and configuring everything at app run time? If you need to enable the McASP with anything other than the settings for the HDMI transmitter chip, you'll need to craft your own device tree overlay. It's up to you whether you want the overlay to support everything needed by your cape or just the McASP part (and have it work in conjunction with one of the universal overlays). There are pros and cons to both approaches, but the more traditional option is to have a single overlay supporting all the required features for your cape. This will allow the overlay to properly loaded by the cape manager at boot time (assuming your cape has a properly programmed EEPROM). -- Charles Steinkuehler [email protected] -- 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.
