All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: bernard 5.0.1 and beagle-xm rev c
Date: Wed, 15 Jun 2011 20:18:52 +0300	[thread overview]
Message-ID: <itaphs$mug$1@dough.gmane.org> (raw)
In-Reply-To: <4DF8E01F.8040209@linux.intel.com>

Hi,

On 06/15/2011 07:38 PM, Darren Hart wrote:
> 
> For details on that effort and it's status, please see:
> 
> https://lists.yoctoproject.org/pipermail/yocto/2011-June/001599.html
> 

I'm aware of this.

> 
> Both Koen and Jason K. have been helping to get the right bits merged
> for the kernel. I had hoped to use mainline u-boot, but it appears we
> may need at least a set of patches in support of Rev C.

What else is needed in addition to [2]?

> 
> The updated BSP will be released with 1.1. My patches and commits will
> of course hit the list before then and you can build from master once
> they arrive there. Within a week I suspect.
> 

I hope we'll have something which works without graphics on the Beagle
XM - Rev C before October (1.1) - before summer would be great.

This means, I would assume, gcc 4.6.0 fixes and the Beagle XM Rev C
stuff. I did not dare to touch master due to the gcc 4.6.0 issues.
Will this be fixed as well in the near future?

I also played around with the patches in the meantime and

[1] for the x-loader
[2] for for u-boot

seem to apply cleanly on whatever comes with bernard 5.0.1

[1]
http://gitorious.org/x-loader/x-loader/commit/2efa178acd56d83c86210b5934895cfb9ea62125

[2]
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=f6e593bb1255d1e15201cb5dec8c95264489e729

The kernel patch against 2.6.37 seems to be a bit more involved.

Of course more code might be needed to make the Beagle XM Rev C work.

Regards,

Robert

> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel

..."In my egotistical opinion, most people's C programs should be
indented six feet downward and covered with dirt." - Blair P. Houghton

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2011-06-15 17:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 21:13 bernard 5.0.1 and beagle-xm rev c Robert Berger
2011-06-15  1:31 ` Darren Hart
2011-06-15 11:01   ` Robert Berger
2011-06-15 11:46     ` Robert Berger
2011-06-15 16:38     ` Darren Hart
2011-06-15 17:18       ` Robert Berger [this message]
2011-06-15 23:36         ` Darren Hart
2011-06-16  1:32           ` Jason Kridner
     [not found]             ` <4DFA2189.7020804@ahsoftware.de>
2011-06-16 17:48               ` Darren Hart
2011-06-15 18:26       ` Jason Kridner
2011-06-15 19:05         ` Robert Berger
2011-06-15 20:43           ` Jason Kridner
2011-06-18 19:05 ` [PATCH] " Robert Berger
2011-06-27 22:15   ` Darren Hart
2011-06-28  4:43     ` Robert Berger

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='itaphs$mug$1@dough.gmane.org' \
    --to=gmane@reliableembeddedsystems.com \
    --cc=poky@pokylinux.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.