Re: Building for pandaboard

Brian Park <bsp2020@...>

Thanks for the info.
As I'm very new to Yocto, I'd not know how to create local.conf to build for panda, even knowing that the kernel will support pandaboard. How would I go about configuring Yocto to build for panda? If you can point me to some documentation showing how to do it, I'd appreciate it.

I'm just learning yocto, in my spare time, and just went through the quick start guide to build for x86qemu image and skimmed through the development manual. But I'm not too sure how to go about configuring for pandaboard. I figured, I can build for beagle board and then modify config to make it work for panda. However, I'm having build issue when trying to build for beagle board.

If there is already an existing pandaboard config, I'd like to try it.

Thank you.


On Thu, Oct 27, 2011 at 9:51 PM, Bruce Ashfield <bruce.ashfield@...> wrote:
On 11-10-27 8:45 PM, Brian Park wrote:
I'm interested in using Yocto to build linux for PandaBoard. It seems
there are already patches some where that I can use to build for panda,
as I found some discussions mentioning PandaBoard patch in the archive.
But I could not apply it. I'd appreciate some pointers on how to find
and apply the right patch.

Just trying to apply
as a patch using "git am" command gave the following error. I'm using
release 1.1 Edison.

briansp@LinuxMint11 ~/poky $ git am < ~/Documents/pandaboard.patch
previous rebase directory /home/briansp/poky/.git/rebase-apply still
exists but mbox given.

I'm new to developing for linux and yocto. So, any help would be

Those same patches are merged into the 2.6.37 kernel tree here:

So if you do want to use the linux-yocto kernel, you could set
your preferred kernel version to 2.6.37 and you'd get that
kernel and branch for the board.

But like anything, nothing is completely simple, the support in
the 2.6.37 tree was contributed in an effort to add some more board
support to a yocto tested/standardized kernel. There are multiple
sources for pandaboard support, with different functionality (i.e. deeper, different kernel version, etc), different integration and
different goals. i.e. angstrom and meta-texasinstruments.

To use the 2.6.37 support you'd need a configuration of the machine and
a meta layer defining the userspace. There was a prototype one that
floated around, but it was being re-worked to use layer tooling and not
duplicate effort that is in other layers already.

If you like, I can locate that layer and send it along, or you can
try out the other references I mentioned (others may have better /
more detailed information).



Thank you


yocto mailing list

Join { to automatically receive all group messages.