[yocto] Problem with BSP supporting different machines
Bruce Ashfield
bruce.ashfield at gmail.com
Thu Aug 9 07:48:30 PDT 2012
On Thu, Aug 9, 2012 at 10:46 AM, Markus Hubig <mhubig at imko.de> wrote:
> Hi @all,
>
> I'm having some trouble building a BSP supporting two different machines.
> The machines in question are the Stamp9g20 and PortuxG20 from taskit. These
> machines are just slightly different course the PortuxG20 is basically just
> a small SBC built around the Stamp9G20.
>
> You can have a look at my BSP here: http://bitbucket.org/imko/meta-stamp9g20
> but take attention that you're selecting the denzil branch...
>
> If I set MACHINE = stamp9g20 in local.conf all went fine, but with
> MACHINE = portuxg20 I get a kernel for common-pc instead of
> arm-versatile-926ejs ...
>
> Comparing the output of "bitbake -e linux-yocto" for both MACHINE settings
> I notice that for stamp9g20 KMACHINE is "stamp9g20" but for portuxg20 it's
> "common-pc", which results in these "updateme" command:
>
> | updateme --branch standard/default/arm-versatile-926ejs -DKDESC=common-pc:standard
> | --feature features/netfilter --feature features/taskstats arm common-pc
> | poky/meta-stamp9g20/recipes-kernel/linux/files/hardware.cfg
> | poky/meta-stamp9g20/recipes-kernel/linux/files/non-hardware.cfg
> | poky/meta-stamp9g20/recipes-kernel/linux/files/portuxg20/portuxg20.cfg
> | poky/meta-stamp9g20/recipes-kernel/linux/files/portuxg20/portuxg20-preempt-rt.scc
> | poky/meta-stamp9g20/recipes-kernel/linux/files/portuxg20/portuxg20.scc
> | poky/meta-stamp9g20/recipes-kernel/linux/files/portuxg20/portuxg20-standard.scc
>
> Which again (I think ...) leads to a kernel compile error ...
>
> Unfortunately I was not able to find out why the KMACHINE variable is not setup
> correctly with my BSP for PortuxG20 ...
>
> Please can someone have a look? ;-)
Is this the same BSP producing the kconf check warnings on denzil ? I
ran tests this
morning and denzil itself is clean, so there's definitely something
wrong in the layer.
If this is the same BSP, I can have a look and see about solving the
two problems at
once.
Bruce
>
> Cheers, Markus
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
More information about the yocto
mailing list