From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Solomon Peachy <solomon@linux-wlan.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Add support for the ESTeem 195E (PPC405EP) SBC
Date: Mon, 17 Aug 2009 11:13:59 -0400 [thread overview]
Message-ID: <20090817151359.GC8710@zod.rchland.ibm.com> (raw)
In-Reply-To: <20090730200848.GF10244@zod.rchland.ibm.com>
On Thu, Jul 30, 2009 at 04:08:49PM -0400, Josh Boyer wrote:
>>> Ok. So I'm not really all that thrilled with changes to ppcboot.h.
>>> We try to keep this file as much in-sync with U-Boot as we can. Did
>>> your HOTFOOT changes get pulled into upstream U-Boot?
>>
>>Yeah, I thought this may be a problem, but I didn't know a better way to
>>go about this and still maintain compatibility with the many thousands
>>of boards already in the field. I mean, I could strip out the ppcboot.h
>>changes and maintain that as an out-of-tree patch, but without that
>>patch, the kernel won't boot on in-the-field boards, rendering the
>>upstreaming of support for this board kinda pointless.
>>
>>I haven't tried to push anything to upstream u-boot, given how ancient
>>the in-production bootloader is. The guy who originally mangled u-boot
>>for this board did so before the "standard" 405EP dual ethernet layout
>>was added, and never tried to push it upstream. Any upstream uboot work
>>will take the form of a native dts/fdt port that probably won't use
>>ppcboot.h anyway, which brings us full circle...
>
>There is another way. Perhaps you could just copy ppcboot.h to a new file
>called "hotfoot.h" and just use that. It's a duplication of ppcboot.h to
>some degree, but it seems to make sense for your board and it helps preserve
>the "stock" ppcboot.h for other boards.
Solomon, any update on this? As far as I'm concerned, the ppcboot.h issue is
the only thing that really needs to be reworked before we bring this patch
in.
josh
next prev parent reply other threads:[~2009-08-17 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 15:21 [PATCH] Add support for the ESTeem 195E (PPC405EP) SBC Solomon Peachy
2009-07-24 15:59 ` Josh Boyer
2009-07-24 16:10 ` Solomon Peachy
2009-07-24 16:45 ` Josh Boyer
2009-07-30 14:06 ` Josh Boyer
2009-07-30 19:45 ` Solomon Peachy
2009-07-30 20:08 ` Josh Boyer
2009-07-31 0:45 ` David Gibson
2009-07-31 2:38 ` Josh Boyer
2009-08-17 15:13 ` Josh Boyer [this message]
2009-08-20 17:45 ` Solomon Peachy
2009-08-20 19:20 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2009-07-23 15:21 Solomon Peachy
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=20090817151359.GC8710@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=solomon@linux-wlan.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).