On Wed, Sep 8, 2010 at 8:21 AM, Chase Maupin <[email protected]> wrote: > * Added a description of the SOC_FAMILY variable that > can be set in the machine configuration files. > > Signed-off-by: Chase Maupin <[email protected]> > --- > docs/usermanual/chapters/common_use_cases.xml | 13 +++++++++++++ > 1 files changed, 13 insertions(+), 0 deletions(-) > > diff --git a/docs/usermanual/chapters/common_use_cases.xml > b/docs/usermanual/chapters/common_use_cases.xml > index d86d0ca..9d1dc6d 100644 > --- a/docs/usermanual/chapters/common_use_cases.xml > +++ b/docs/usermanual/chapters/common_use_cases.xml > @@ -94,6 +94,19 @@ SRCDATE = "20061014" > </listitem> > </itemizedlist></para> > > + <para>There are also some optional variables that can be defined: > + <itemizedlist> > + <listitem> > + <para><command>SOC_FAMILY</command> describes a family of > processors > + that all share common features such as kernel versions, > + bootloaders, etc. This is used to allow overrides for a whole > + set of devices rather than per machine overrides being used. > + The use of SOC_FAMILY as an override is currently a distribution > + or local setting. > + </para> > + </listitem> > + </itemizedlist></para> > +
You should also explain why it is different from MACHINE_CLASS and possibly add one use case as an example > <para>Next the kernel recipe needs to be added if it doesn't already > exist. > </para> > </section> > -- > 1.7.0.4 > > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
