From: Solomon Peachy <solomon@linux-wlan.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Add support for the ESTeem 195E (PPC405EP) SBC
Date: Thu, 20 Aug 2009 13:45:19 -0400 [thread overview]
Message-ID: <20090820174519.GA8860@linux-wlan.com> (raw)
In-Reply-To: <20090817151359.GC8710@zod.rchland.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Mon, Aug 17, 2009 at 11:13:59AM -0400, Josh Boyer wrote:
> >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.
Should I call the new version 'hotfoot.h' or 'ppcboot-hotfoot.h'?
- Solomon
--
Solomon Peachy solomon@linux-wlan.com
AbsoluteValue Systems http://www.linux-wlan.com
721-D North Drive +1 (321) 259-0737 (office)
Melbourne, FL 32934 +1 (321) 259-0286 (fax)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-08-20 17:54 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
2009-08-20 17:45 ` Solomon Peachy [this message]
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=20090820174519.GA8860@linux-wlan.com \
--to=solomon@linux-wlan.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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.