From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Does Edison work with Beagleboard & linux-yocto-3.0 kernel?
Date: Wed, 11 Jan 2012 09:57:59 -0500 [thread overview]
Message-ID: <4F0DA377.9090903@windriver.com> (raw)
In-Reply-To: <CAFZh4h-oJeiWFcM1mowKDwmF0gqT3Y0DBMFZ0WEcjJchUS+N4A@mail.gmail.com>
On 12-01-11 09:41 AM, Brian Hutchinson wrote:
> Hi,
>
> I followed the example in the "Yocto Project Development Manual" for
> setting up a local kernel repo and it didn't go so well.
>
> A month or two ago I checked out Edison and was able to build all the
> images required for Beagleboard and it booted fine (using command line
> ... not hob. Tried hob but couldn't get it to work).
>
> So then I checked out linux-yocto-3.0 kernel and setup a local kernel
> git repo and went through the process of setting up poky-extras,
> modifying bblayers.conf etc. to point to my local repo.
>
> Any time I try to build core-image-minimal it looks like it always
> wants to use the 2.6.37 recipe instead of finding my 3.0 repo. I've
> tried everything I can think of and I must me missing something.
>
> So, I guess my questions are:
>
> 1. Will linux-yocto-3.0 work with Beagleboard?
It will. I sent patches recently to make that the preferred version
in the master branch. Cherry picking that change would probably
be all you would need.
> 2. Is the example for setting up for kernel modification in the
> development manual still valid for Edison?
Should be.
Bruce
>
> Regards,
>
> Brian
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-01-11 14:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 14:41 Does Edison work with Beagleboard & linux-yocto-3.0 kernel? Brian Hutchinson
2012-01-11 14:57 ` Bruce Ashfield [this message]
2012-01-11 15:20 ` Brian Hutchinson
2012-01-11 15:24 ` Jack Mitchell
2012-01-11 15:31 ` Bruce Ashfield
2012-01-11 15:29 ` Bruce Ashfield
2012-01-11 16:29 ` Brian Hutchinson
2012-01-11 20:35 ` Brian Hutchinson
2012-01-11 20:46 ` Bruce Ashfield
2012-01-11 20:50 ` Brian Hutchinson
2012-01-11 20:47 ` Joshua Lock
2012-01-11 20:57 ` Brian Hutchinson
2012-01-12 15:21 ` Brian Hutchinson
2012-01-12 15:56 ` Jack Mitchell
2012-01-12 16:29 ` Brian Hutchinson
2012-01-12 16:00 ` Bruce Ashfield
2012-01-12 16:20 ` Brian Hutchinson
2012-01-12 16:24 ` Bruce Ashfield
2012-01-12 16:48 ` Brian Hutchinson
2012-01-12 18:28 ` Bruce Ashfield
2012-01-15 8:47 ` Koen Kooi
2012-01-15 17:35 ` Brian Hutchinson
2012-01-23 3:33 ` Brian Hutchinson
2012-01-23 3:55 ` Bruce Ashfield
2012-01-23 19:40 ` Brian Hutchinson
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=4F0DA377.9090903@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=b.hutchman@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.