From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: board specific defines in commproc.h !?!?
Date: Mon, 17 Jun 2002 11:20:02 +0200 [thread overview]
Message-ID: <3D0DA9C2.D78C43E5@imc-berlin.de> (raw)
Hi there,
I think we should move the board specific defines such as
/*** RPXCLASSIC *****************************************************/
#ifdef CONFIG_RPXCLASSIC
/* Bits in parallel I/O port registers that have to be set/cleared
* to configure the pins for SCC1 use.
*/
#define PA_ENET_RXD ((ushort)0x0001)
#define PA_ENET_TXD ((ushort)0x0002)
#define PA_ENET_TCLK ((ushort)0x0200)
etc. out of ./include/asm-ppc/commproc.h into the board specific header
files like ./arch/ppc/platforms/xxx.h
The advantage is, that you don't have to change many files to port linux
to a new, custom platform. After all #define PA_ENET_RXD
((ushort)0x0001) is a board specific configuration define.
The same goes for the status_led.h from DENX (which unfortunatly has not
yet made it into linuxppc_2_4_devel!?!?)
At the same time we should changes this in the PPCBoot source - to make
porting Linux to a new platform easier.
I am prepared to do this - if you think it's worth it!
So?
Cheers,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-17 9:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 9:20 Steven Scholz [this message]
2002-06-17 14:05 ` board specific defines in commproc.h !?!? John W. Linville
2002-06-17 15:32 ` Tom Rini
2002-06-17 15:37 ` Steven Scholz
2002-06-17 15:49 ` Tom Rini
2002-06-17 16:01 ` Steven Scholz
2002-06-17 16:28 ` Tom Rini
2002-06-17 17:25 ` Wolfgang Denk
[not found] ` <20020617173550.GV13541@opus.bloom.county>
2002-06-17 17:46 ` Steven Scholz
2002-06-17 20:23 ` Wolfgang Denk
[not found] ` <3D106922.7026437A@imc-berlin.de>
2002-06-19 15:05 ` Tom Rini
2002-06-19 15:18 ` Steven Scholz
2002-06-19 15:25 ` Tom Rini
2002-06-19 15:33 ` Steven Scholz
2002-06-19 15:41 ` Tom Rini
2002-06-19 15:47 ` Steven Scholz
2002-06-19 15:51 ` Tom Rini
2002-06-19 21:11 ` Dan Malek
2002-06-19 21:22 ` Tom Rini
2002-06-20 16:32 ` Dan Malek
2002-06-19 22:15 ` Wolfgang Denk
2002-06-19 23:26 ` Conn Clark
2002-06-20 16:40 ` Dan Malek
[not found] ` <3D12F140.23BA447F@imc-berlin.de>
[not found] ` <15635.12386.415897.593660@argo.ozlabs.ibm.com>
2002-06-21 14:18 ` John Traill
[not found] <20020617214339.GZ13541@opus.bloom.county>
2002-06-17 22:28 ` Wolfgang Denk
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=3D0DA9C2.D78C43E5@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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).