[poky] Booting BeagleBoard

[Koen Kooi]

Op 13 feb 2011, om 16:06 heeft Gary Thomas het volgende geschreven:

> On 02/13/2011 08:00 AM, Koen Kooi wrote:
>> 
>> Op 13 feb 2011, om 15:57 heeft Gary Thomas het volgende geschreven:
>> 
>>> On 02/12/2011 08:01 AM, Koen Kooi wrote:
>>>> 
>>>> Op 12 feb 2011, om 15:52 heeft Gary Thomas het volgende geschreven:
>>>> 
>>>>> I have a BeagleBoard C3 (not the new xM).  Trying to run the
>>>>> latest Poky ran into some problems:
>>>>> 
>>>>> * The boot commands in README.hardware are no longer accurate
>>>>>  for the 2.6.37 (linux-yocto) kernel.  At least you need to
>>>>>  use ttyO2 for the serial console.
>>>>> * There is no video?  /dev/fb0 is not being created.
>>>>> 
>>>>> I know that the previous (Angstrom based) 2.6.32 kernel had
>>>>> lots of additions which support video (DSS subsystem) and
>>>>> also camera (ISP).  Has this support been ported forward
>>>>> into the Yocto kernel?
>>>> 
>>>> Even better, there is a proper BSP with beagleboard support: http://gitorious.org/angstrom/angstrom-layers/commits/master
>>> 
>>> How is this used?  I tried just adding a pointer to that tree
>>> in my conf/bblayers.conf.  I also tried moving that tree into
>>> my poky sources at the same level as meta-emenlow, etc.  Both
>>> attempts immediately yielded this error:
>>>  ERROR: Unable to parse conf/bitbake.conf: Could not include required file conf/machine/include/omap3.inc
>>> 
>>> Perhaps you can give some guidance for how to use this?
>> 
>> http://thread.gmane.org/gmane.linux.distributions.angstrom.devel/4698/focus=4700
> 
> Obviously this is not what I'm looking for.
> 
> What I had wanted to test was your layering on top of my extant
> Poky/Yocto environment.  I don't want to start over as I have my
> own layers that work just fine with Poky.

I obviously misunderstood your request on the angstrom mailinglist on how to setup angstrom on top of yocto as a request on how to setup angstrom on top of yocto. I'm sorry that I fail to understand such obvious things. I will from now on stop trying to understand your requests to avoid any confusion and perceived wrongdoing on my part.