From: Tom Rini <trini@kernel.crashing.org>
To: Murray Jensen <Murray.Jensen@csiro.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Hymod board support and related changes ...
Date: Tue, 28 May 2002 12:26:52 -0700 [thread overview]
Message-ID: <20020528192652.GM1295@opus.bloom.county> (raw)
In-Reply-To: <17991.1022564915@msa.cmst.csiro.au>
On Tue, May 28, 2002 at 03:48:35PM +1000, Murray Jensen wrote:
> Hymod board support and related changes ...
>
> - Hymod board support
> - 8260 fcc_enet: more flexible (or at least readable) approach to
> configuring i/o pins
> - 8260 fcc_enet: support different PHY interrupt "vector"s for each FCC
> - 8260 setup: fixed ppcboot jump address; should be 0x...110 not 0x...104
> - 8260 setup: turn off interrupts before jumping to the boot rom
Can you split this up into logical patches? Also, instead of testing
TQM8260 || HYMOD for PPCBoot, why don't we just add in something like:
if [ "$CONFIG_TQM8260" = "y" -o "$CONFIG_HYMOD" = "y" \
-o "$CONFIG_TQM8xx" = "y" ] ;then
define_bool CONFIG_PPCBOOT y
fi
And use that.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-28 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 5:48 [PATCH] Hymod board support and related changes Murray Jensen
2002-05-28 19:26 ` Tom Rini [this message]
2002-05-29 2:10 ` Murray Jensen
2002-05-28 20:18 ` Tom Rini
2002-05-28 20:19 ` Tom Rini
2002-05-29 2:07 ` Murray Jensen
2002-05-29 14:36 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 5:45 [PATCH] misc compiler warn/err fixes, typo fixes and aesthetic changes Murray Jensen
2002-05-28 18:35 ` Tom Rini
2002-05-29 1:42 ` Murray Jensen
2002-06-03 15:00 ` Tom Rini
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=20020528192652.GM1295@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Murray.Jensen@csiro.au \
--cc=linuxppc-embedded@lists.linuxppc.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 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).