From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Brian Park <bsp2020@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Building for pandaboard
Date: Fri, 28 Oct 2011 00:51:55 -0400 [thread overview]
Message-ID: <4EAA34EB.5060205@windriver.com> (raw)
In-Reply-To: <CAFNE1kTTFYhhqK_nopj4MG7VNzWKriZTbGJYAZt-shTinw_ROA@mail.gmail.com>
On 11-10-27 8:45 PM, Brian Park wrote:
> Hi,
> 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
> http://article.gmane.org/gmane.linux.embedded.yocto.general/2037/match=pandaboard
> 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
> appreciated.
Those same patches are merged into the 2.6.37 kernel tree here:
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37/log/?h=yocto/standard/pandaboard
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).
Cheers,
Bruce
>
> Thank you
>
> Brian
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-10-28 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 0:45 Building for pandaboard Brian Park
2011-10-28 4:51 ` Bruce Ashfield [this message]
2011-10-28 17:06 ` Brian Park
2011-10-29 16:47 ` Bruce Ashfield
2011-10-31 7:25 ` Koen Kooi
2011-10-28 14:10 ` Robert P. J. Day
2011-10-31 7:25 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EAA34EB.5060205@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=bsp2020@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.