From: "Cédric Le Goater" <clg@kaod.org>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"Milton D. Miller II" <miltonm@us.ibm.com>,
Patrick Williams <patrick@stwcx.xyz>
Subject: Re: updating u-boot_2013.07.bb recipe
Date: Fri, 27 May 2016 13:50:32 +0200 [thread overview]
Message-ID: <57483488.1040401@kaod.org> (raw)
In-Reply-To: <CACPK8Xe6Cu-7+1bKd3DaNcGbv4+BhW_nziA=TVgU8A6STRGzDg@mail.gmail.com>
Hello Joel,
On 05/27/2016 12:13 PM, Joel Stanley wrote:
> Hey Cedric,
>
> On Fri, May 27, 2016 at 6:28 PM, Cédric Le Goater <clg@kaod.org> wrote:
>> The uboot recipe in openbmc is still at 4b44678c11. Without them, I see
>> memory corruption under qemu, so I suppose this is the same for real HW.
>>
>> commit 6f7818cdb8d8 "net: aspeednic: Do not start hardware in initialize"
>> seems to solve the problem.
>>
>> Is there a reason for staying at that level in uboot ? Could we take all
>> Milton's patches in ?
>
> We updated to 44f1262bdf39ad93032d39f17a298165372be82e just yesterday:
>
> https://github.com/openbmc/openbmc/commit/265b0d55113d364554102d532177916741c8c379
Ah. I missed that.
So, I baked a new flash and all is fine now. The generated flash boots
the qemu guest without modification.
> The hold up related to some discussion around not going back to the
> default compiler:
>
> https://github.com/openbmc/openbmc/pull/227
>
> I see Patrick closed this yesterday. I'm not sure what the plans are
> there; I would strongly recommend we go back to the more modern compiler.
u-boot.bin boots a palmetto bmc when compiled with :
gcc version 5.2.0 (crosstool-NG crosstool-ng-1.22.0)
I didn't try the kernel though.
Cheers,
C.
prev parent reply other threads:[~2016-05-27 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 8:58 updating u-boot_2013.07.bb recipe Cédric Le Goater
2016-05-27 10:13 ` Joel Stanley
2016-05-27 11:50 ` Cédric Le Goater [this message]
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=57483488.1040401@kaod.org \
--to=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=miltonm@us.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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.