so what can I expect to happen if I define a cape as being present in uEnv.txt then remove the cape without (un)defining it?
Eric On Sun, May 18, 2014 at 1:09 PM, John Syn <[email protected]> wrote: > > > From: Eric Fort <[email protected]> > Reply-To: <[email protected]> > Date: Sunday, May 18, 2014 at 12:01 AM > To: beagleboard <[email protected]> > Subject: Re: [beagleboard] Re: beagle audio cape (Rev B1) > > So on the capes that have an EEPROM, why do they need it and how is the > eeprom used? Also, lets say I add the cape to the cape stack and add it to > uEnv.txt. do I then need to remove the edits to uEnv.txt if/when I remove > the audio cape from the stack? what are the effects of doing or not doing > so. > > Instead of defining the Device Tree Overlay manually in uEnv.txt, capes > with EEPROM enables the kernel to identify the cape and load the DTO > automatically. > > Regards, > John > > > > Eric > > > On Sat, May 17, 2014 at 1:06 PM, John Syn <[email protected]> wrote: > >> >> >> From: Eric Fort <[email protected]> >> Reply-To: <[email protected]> >> Date: Saturday, May 17, 2014 at 10:57 AM >> To: beagleboard <[email protected]> >> Subject: [beagleboard] Re: beagle audio cape (Rev B1) >> >> ok, setup directions are here.... >> http://elinux.org/CircuitCo:Audio_Cape_RevB#Audio_Cape_Revision_B1 but >> I'm still trying to understand how all this works. are the cape eeproms >> and the info within them just not used? how is the cape Identified and >> setup automatically..... or must I edit one or more files to do this >> manually each and every time I add or remove the audio cape from the stack. >> >> Well, again it depends on your kernel version. If you are using V3.8, you >> add the audio cape in your uEnv.txt file and you enable the TLV320AIC3x >> driver in your kernel config. When your kernel boots, it runs the audio >> codec init which will eventually call the probe function and that will read >> in the audio cape device tree overlay and configure the audio codec. If you >> are using a kernel version later than V3.8, you have to manually add the >> audio cape device tree to your board device tree. >> >> Regards, >> John >> >> >> >> Eric >> >> >> On Sat, May 17, 2014 at 10:30 AM, Eric Fort <[email protected]> wrote: >> >>> The beagle audio cape seems to not have a cape eeprom. How then is it >>> detected as being there with the present kernel? since it has no cape >>> eeprom does this mean that it does not count as to being one of the 4 cape >>> addresses thus giving a free pass with the ability to have this cape and 4 >>> others. I'm really looking forward to playing with this board. >>> >>> Eric >>> >> >> -- >> 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. >> > > -- > 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. > -- 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.
