From: "H. Peter Anvin" <hpa@zytor.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Russell King <rmk+serial@arm.linux.org.uk>,
Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 2/2] 8250_pnp: register x86 COM ports at the conventional ttyS names
Date: Wed, 16 Jan 2008 14:49:44 -0500 [thread overview]
Message-ID: <478E5FD8.5060906@zytor.com> (raw)
In-Reply-To: <200801161247.34821.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
>>> +
>> Arguably, the right thing is to use the addresses present in the array
>> at address 0x400. In particular, COM3 and COM4 aren't always at those
>> addresses.
>
> Wow. I bow before your storehouse of x86 arcana :-)
>
> I guess you're referring to the "BIOS data area," which I'd never
> heard of before (but fortunately, Google knows).
>
> What would you think about doing this only for COM1 and COM2? The
> only real value for doing this in the first place is so "console=ttyS0"
> always goes to COM1, even if we don't have SERIAL_PORT_DFNS. User-
> space ought to use some sort of udev magic if it cares about persistent
> naming.
>
Well, there are four ports that the BIOS have slots for, and if so, we
probably should use them.
-hpa
next prev parent reply other threads:[~2008-01-16 19:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 17:05 [patch 0/2] serial: explicitly request ttyS0-3 for COM1-4 Bjorn Helgaas
2008-01-16 17:05 ` Bjorn Helgaas
2008-01-16 17:05 ` [patch 1/2] 8250: add serial8250_register_port_at() for requesting specific ttyS lines Bjorn Helgaas
2008-01-16 17:05 ` Bjorn Helgaas
2008-01-16 17:05 ` [patch 2/2] 8250_pnp: register x86 COM ports at the conventional ttyS names Bjorn Helgaas
2008-01-16 17:05 ` Bjorn Helgaas
2008-01-16 18:42 ` Russell King
2008-01-16 18:44 ` H. Peter Anvin
2008-01-16 19:47 ` Bjorn Helgaas
2008-01-16 19:49 ` H. Peter Anvin [this message]
2008-01-16 18:39 ` [patch 0/2] serial: explicitly request ttyS0-3 for COM1-4 Russell King
2008-01-16 19:59 ` Bjorn Helgaas
2008-01-16 20:14 ` Russell King
2008-01-17 16:07 ` Bjorn Helgaas
2008-01-17 16:16 ` Russell King
2008-01-17 17:56 ` Bjorn Helgaas
[not found] <9MjWa-VI-9@gated-at.bofh.it>
[not found] ` <9MjWb-VI-11@gated-at.bofh.it>
[not found] ` <9MlEG-3Mx-13@gated-at.bofh.it>
[not found] ` <9Mmra-56f-29@gated-at.bofh.it>
2008-01-16 20:33 ` [patch 2/2] 8250_pnp: register x86 COM ports at the conventional ttyS names Bodo Eggert
2008-01-16 20:33 ` Bodo Eggert
2008-01-16 20:42 ` H. Peter Anvin
2008-01-16 23:34 ` Rene Herman
2008-01-18 18:10 ` H. Peter Anvin
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=478E5FD8.5060906@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
/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.