From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-commit@source.mvista.com
Subject: Re: Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc_2_4_devel
Date: Thu, 08 Nov 2001 18:06:06 -0500 [thread overview]
Message-ID: <3BEB0FDE.9080107@embeddededge.com> (raw)
In-Reply-To: 20011108144704.B2271@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
> Yes, but then you end up....
Not what I had in mind :-).
For example, in include/asm-ppc/mpc8xx.h:
#define piggy_serial_init() mpc_serial_init(bp)
...and in include/asm-ppc/ibm4xx.h
#define piggy_serial_init() serial_init(0)
...and in misc-embedded.c change you list of #ifdefs to be:
piggy_serial_init();
If the individual boards need some different initialization, just
move the macro to a lower level include file.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-08 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011108193006.26A0010028@hostme.bitkeeper.com>
2001-11-08 19:38 ` Incoming to hostme.bitkeeper.com:/ua/repos/p/ppc/linuxppc_2_4_devel Tom Rini
2001-11-08 21:40 ` Dan Malek
2001-11-08 21:47 ` Tom Rini
2001-11-08 23:06 ` Dan Malek [this message]
[not found] <20020604181844.00BFE10306@hostme.bitkeeper.com>
[not found] ` <20020604155258.B22057@ecam.san.rr.com>
2002-06-04 22:57 ` andrew may
[not found] <20011121185116.6539A100D1@hostme.bitkeeper.com>
2001-11-21 18:59 ` Tom Rini
[not found] <20011101001030.EFA5510094@hostme.bitkeeper.com>
[not found] ` <3BE1932E.DB7956CA@linux-m68k.org>
2001-11-01 18:56 ` Tom Rini
2001-11-01 22:22 ` Roman Zippel
2001-11-02 2:10 ` Tom Rini
2001-11-02 10:09 ` Roman Zippel
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=3BEB0FDE.9080107@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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.