From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: platform_serial.h
Date: Fri, 30 Nov 2001 22:49:42 +1100 (EST) [thread overview]
Message-ID: <15367.29270.548171.448033@argo.ozlabs.ibm.com> (raw)
Currently include/asm-ppc/serial.h has definitions for the 4 standard
PC serial ports plus other oddball ISA multiport serial adaptors:
fourport, accent, boca and hub6.
Has anyone *ever* used any of these ISA multiport adaptors on a PPC
system? I wouldn't be at all surprised if the answer was no.
I would like to move those extra oddball things out to
include/asm-ppc/isa-serial.h. Then I think <asm/serial.h> should
include <platform_serial.h>, and if that doesn't define
STD_SERIAL_PORT_DEFNS, define that to be the 4 standard PC serial
ports.
It boils down to the question of what default serial ports we think a
platform should get if it doesn't provide a platform_serial.h file:
- none,
- the four standard PC ports, or
- the four standard PC ports plus the oddball ones?
If we go for the second option and a platform wants the oddball ones,
it can #include <asm/isa-serial.h> in its platform_serial.h file.
Note that none of this will affect PCI multiport serial cards at all.
Comments?
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-11-30 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15367.29270.548171.448033@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@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).