From: Andreas Tobler <toa@pop.agri.ch>
To: Alain RICHARD <alain.richard@equation.fr>
Cc: Benjamin Herrenschmidt <bh40@calva.net>,
Paul Mackerras <paulus@linuxcare.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: MacSerial and Serial driver cohabitation
Date: Mon, 17 Jul 2000 11:46:25 +0200 [thread overview]
Message-ID: <3972D5F0.617E9E6F@pop.agri.ch> (raw)
In-Reply-To: p04320400b59877f5cc70@[192.168.240.10]
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
Alain RICHARD wrote:
> There is a long waiting problem in making the two serial drivers
> (legacy serial driver named serial.o and macintosh serial driver
> named macserial.o). The problem is that the two drivers thinks there
> are the legacy one and numbers each serial port found from ttyS0 to
> ttySn. So if you try to load them simultaneously, you'll get a kernel
> fault.
>
> There are several workarounds, either :
>
> - compiles only macserial and disable legacy serial.
> - compiles the two drivers as modules and load only one (by adding
> "alias char-major-4 macserial" and "alias char-major-5 macserial" in
> your /etc/conf.modules file).
I do it this way, the macserial is built in, the serial as a module.
When you do build the serial into the kernel you get a build error:
multiple definition of `serial_console_init'
>
> This is just a hack, but the problem is worst : macserial is a serial
> driver for Z8530 chipsets and serial is a serial driver for 16x50
> UARTs. There are several cases where you may need the two drivers :
>
> a) in a powerbook when using a pcmcia modem : most, if not all, modem
> cards are based on a 16x50 UART and do need the serial.o driver.
> b) most PCI serial cards are using 16x50 UARTs
>
> Powerbooks kernels compiled by Paul Mackerras have a quick fix in the
> serial driver in order to make it skip the first 2 ttyS entries when
> compiled on PMAC architecture. This fix works but was never included
> in the main kernel because it is just a simple hack.
It's not only the skipping, there is some more needed. When you build the serial
and start the kernel then it panics since the autoconfig in serial.c is not
working on PPC.
Attached my suggestion. Here it works on a wallstreet I, which has 2 heathrow's,
that's why the offset is 4 and not 2 as mentioned above.
Andreas
[-- Attachment #2: cb-serial2217.patch.gz --]
[-- Type: application/x-gzip, Size: 950 bytes --]
next prev parent reply other threads:[~2000-07-17 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.10.10007150057110.4812-100000@unix1.wm.edu>
[not found] ` <20000715082955.6590@192.168.1.10>
2000-07-17 9:22 ` MacSerial and Serial driver cohabitation Alain RICHARD
2000-07-17 9:46 ` Andreas Tobler [this message]
2000-07-17 10:21 ` Benjamin Herrenschmidt
2000-07-17 12:32 ` Geert Uytterhoeven
2000-07-17 15:33 ` Michael Schmitz
2000-07-25 21:56 ` Michel Lanners
2000-07-28 8:37 ` Benjamin Herrenschmidt
2000-07-28 10:39 ` Michael Schmitz
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=3972D5F0.617E9E6F@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=alain.richard@equation.fr \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.com \
/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).