From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: include/asm-ppc/platforms/
Date: Fri, 30 Nov 2001 10:12:33 +1100 [thread overview]
Message-ID: <31270.1007075553@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 29 Nov 2001 15:46:10 PDT." <20011129154610.M29541@cpe-24-221-152-185.az.sprintbbd.net>
On Thu, 29 Nov 2001 15:46:10 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>On Fri, Nov 30, 2001 at 09:38:36AM +1100, Keith Owens wrote:
>> Tom Rini <trini@kernel.crashing.org> wrote:
>> >and all platforms need a
>> >platform/platform_serial.h file for serial to work with this scheme?
>>
>> No, an empty one is automatically generated if necessary.
>
>So yes, for CONFIG_SERIAL to work, the file needs to exist. Which has
>the downside that at least a handful of platforms will need to cp
>all_ppc_serial.h.
Are the *_serial.h files intended as extensions for asm-ppc/serial.h or
as complete replacements for it? If they are extensions then adding
#include <platform_serial.h> to asm-ppc/serial.h is enough. If they are
complete replacements then the code is a little harder, but not much.
*.c files include only <asm/serial.h>. In platform *_serial.h files,
#define REPLACES_PPC_SERIAL_H. In asm-ppc/serial.h,
#include <platform_serial.h>
#ifndef REPLACES_PPC_SERIAL_H
... default ppc serial definitions
#endif
Do that once and forget about it, instead of needing #ifdef CONFIG for
each platform throughout the code.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 23:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 11:32 include/asm-ppc/platforms/ Paul Mackerras
2001-11-27 15:22 ` include/asm-ppc/platforms/ Tom Rini
2001-11-27 20:06 ` include/asm-ppc/platforms/ Roman Zippel
2001-11-28 2:35 ` include/asm-ppc/platforms/ Keith Owens
2001-12-27 14:59 ` include/asm-ppc/platforms/ Dan Malek
2001-11-27 12:00 ` include/asm-ppc/platforms/ Matt Porter
2001-11-27 15:18 ` include/asm-ppc/platforms/ Geert Uytterhoeven
2001-12-27 15:18 ` include/asm-ppc/platforms/ Dan Malek
2001-11-27 23:44 ` include/asm-ppc/platforms/ Wolfgang Denk
2001-11-28 6:13 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 6:23 ` include/asm-ppc/platforms/ Dan Malek
2001-11-29 11:48 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-29 15:26 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 22:19 ` include/asm-ppc/platforms/ Keith Owens
2001-11-29 22:27 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 22:38 ` include/asm-ppc/platforms/ Keith Owens
2001-11-29 22:46 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 23:12 ` Keith Owens [this message]
2001-11-29 23:18 ` include/asm-ppc/platforms/ Tom Rini
2001-11-28 8:46 ` include/asm-ppc/platforms/ Adrian Cox
2001-11-28 21:34 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 21:46 ` include/asm-ppc/platforms/ Adrian Cox
2001-11-29 17:57 ` include/asm-ppc/platforms/ Frank Rowand
2001-11-28 23:50 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 10:57 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 23:51 ` include/asm-ppc/platforms/ Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 13:30 include/asm-ppc/platforms/ Ralph Blach
2001-11-30 22:08 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-30 23:22 ` include/asm-ppc/platforms/ Frank Rowand
2001-12-01 3:31 ` include/asm-ppc/platforms/ Dan Malek
2001-12-01 18:19 ` include/asm-ppc/platforms/ Frank Rowand
2001-12-01 22:22 ` include/asm-ppc/platforms/ Dan Malek
2001-12-01 22:41 ` include/asm-ppc/platforms/ Tom Rini
2001-12-01 0:19 ` include/asm-ppc/platforms/ Armin Kuster
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=31270.1007075553@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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 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).