All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 12 Jan 2012 11:00:43 -0500	[thread overview]
Message-ID: <4F0F03AB.1010808@windriver.com> (raw)
In-Reply-To: <CAFZh4h8CtWD3q7_bWQoH9X1j=J=irW05Mhvbqvv5h_fp-oFn+A@mail.gmail.com>

On 12-01-12 10:21 AM, Brian Hutchinson wrote:
> Yet another follow up.  I finally found my C3 Beagleboard and the
> default kernel built off master yesterday works on that platform too.
>
> I was able to do another build with the tips you guys gave and it
> looks like it is picking up the kernel from my local git repo now.  I
> did the "calibrate" example and while I couldn't see the printk's due
> to the silent boot being turned on somehow, uname -a was different
> than the default image .... mine is now:
>
> root@beagleboard:~# uname -a
> Linux beagleboard 3.0.14-yocto-standard+ #1 PREEMPT Thu Jan 12
> 08:45:10 EST 2012 armv7l GNU/Linux
>
> And just for sanity, I made another copy of my bare clone and verified
> that I pushed the "calibrate" changes correctly.
>
> So it looks like I'm good now thanks to your help!
>
> Do I have to do a cleanall every time I'm finished pushing changes
> back to my local kernel repo?

The bitbake AUTOREV code should take care of updating the clone
of your local repo in downloads/git2. I take it that this isn't
happening ?

>
> Is there a document that gives clues as to how to setup a local u-boot
> repo for making changes to it?  Is is simply changing the u-boot
> recipe SRC_URI to use my local u-boot git repo in
> poky/meda/recipes-bsp/u-boot or is it more involved than that?  Is
> there a u-boot dev layer like the poky-extras/meta-kernel-dev?

It should be (largely) as simple as that. We could create something
simple and throw it in with the meta-kernel-dev layer if there's any
interest in adding it.

Cheers,

Bruce

>
> Regards,
>
> Brian



  parent reply	other threads:[~2012-01-12 16:00 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
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 [this message]
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=4F0F03AB.1010808@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.