All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [poky] [PATCH 1/1] README.hardware: remove u-boot flashing	instructions for mpc8315e-rdb
Date: Thu, 31 Mar 2011 09:32:58 -0700	[thread overview]
Message-ID: <4D94ACBA.90409@linux.intel.com> (raw)
In-Reply-To: <20110331141920.3B1C5F03208@gemini.denx.de>



On 03/31/2011 07:19 AM, Wolfgang Denk wrote:
> Dear Paul Eggleton,
>
> In message<41ae31ba057b63d3c518e2edf217109c59b64603.1301578942.git.paul.eggleton@linux.intel.com>  you wrote:
>> From: Paul Eggleton<paul.eggleton@linux.intel.com>
>>
>> Upgrading u-boot is apparently not necessary with current board revisions,
>> and these instructions may not work properly anyway (our toolchain seems not
>> to be able to compile u-boot in the way described), and given that they are
>> potentially risky they should be removed.
>
> The instructions you delete appear to be pretty generic ones, and I
> see no reason why they would not work.
>

When I followed them I ended up with a dead mpc3815e-rdb. I suspect my 
u-boot image was bad in some way, but my concern was that others would 
end up in the same situation following the instructions. Since the 
existing u-boot version was able to boot the linux-yocto kernel recipe, 
there appears to be no need to reflash u-boot.

> If the Poky too chain has issues with this, then there is a problem
> with that tool chain, and you should enter a bug report.
>
> What exactly would that problem be?

Absolutely, this wasn't intended as a final "solution". The issue 
appears to be related to the 4.5.1 version of gcc failing in various 
ways to build either u-boot master or v2010.09, or v2010.12. I will 
report this to the u-boot mailing list just as soon as I can get back to it.

--
Darren

>
> In any case, just papering over the problems seems not a good
> startegy to me.
>
> Best regards,
>
> Wolfgang Denk
>

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



WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@linux.intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] README.hardware: remove u-boot flashing	instructions for mpc8315e-rdb
Date: Thu, 31 Mar 2011 09:32:58 -0700	[thread overview]
Message-ID: <4D94ACBA.90409@linux.intel.com> (raw)
In-Reply-To: <20110331141920.3B1C5F03208@gemini.denx.de>



On 03/31/2011 07:19 AM, Wolfgang Denk wrote:
> Dear Paul Eggleton,
>
> In message<41ae31ba057b63d3c518e2edf217109c59b64603.1301578942.git.paul.eggleton@linux.intel.com>  you wrote:
>> From: Paul Eggleton<paul.eggleton@linux.intel.com>
>>
>> Upgrading u-boot is apparently not necessary with current board revisions,
>> and these instructions may not work properly anyway (our toolchain seems not
>> to be able to compile u-boot in the way described), and given that they are
>> potentially risky they should be removed.
>
> The instructions you delete appear to be pretty generic ones, and I
> see no reason why they would not work.
>

When I followed them I ended up with a dead mpc3815e-rdb. I suspect my 
u-boot image was bad in some way, but my concern was that others would 
end up in the same situation following the instructions. Since the 
existing u-boot version was able to boot the linux-yocto kernel recipe, 
there appears to be no need to reflash u-boot.

> If the Poky too chain has issues with this, then there is a problem
> with that tool chain, and you should enter a bug report.
>
> What exactly would that problem be?

Absolutely, this wasn't intended as a final "solution". The issue 
appears to be related to the 4.5.1 version of gcc failing in various 
ways to build either u-boot master or v2010.09, or v2010.12. I will 
report this to the u-boot mailing list just as soon as I can get back to it.

--
Darren

>
> In any case, just papering over the problems seems not a good
> startegy to me.
>
> Best regards,
>
> Wolfgang Denk
>

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


  parent reply	other threads:[~2011-03-31 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 13:46 [PATCH 0/1] remove u-boot flashing instructions for mpc8315e-rdb Paul Eggleton
2011-03-31 13:46 ` [PATCH 1/1] README.hardware: " Paul Eggleton
2011-03-31 14:19   ` [poky] " Wolfgang Denk
2011-03-31 14:19     ` Wolfgang Denk
2011-03-31 14:23     ` [poky] " Bruce Ashfield
2011-03-31 14:23       ` Bruce Ashfield
2011-03-31 14:45       ` [poky] " Wolfgang Denk
2011-03-31 14:45         ` Wolfgang Denk
2011-03-31 16:32     ` Darren Hart [this message]
2011-03-31 16:32       ` Darren Hart
2011-03-31 21:31       ` [poky] " Wolfgang Denk
2011-03-31 21:31         ` Wolfgang Denk
2011-03-31 22:18         ` [poky] " Darren Hart
2011-03-31 22:18           ` Darren Hart
2011-03-31 16:27   ` [poky] " Darren Hart
2011-03-31 16:27     ` Darren Hart
2011-03-31 14:38 ` [PATCH 0/1] " Richard Purdie
2011-03-31 14:38   ` [OE-core] " Richard Purdie

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=4D94ACBA.90409@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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.