From: Arjan van de Ven <arjanv@redhat.com>
To: Ruud Linders <rkmp@xs4all.nl>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.x kernels and ttyS45 for 6 serial ports ?
Date: Mon, 05 Apr 2004 16:21:06 +0200 [thread overview]
Message-ID: <1081174866.4679.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <40716855.50900@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
On Mon, 2004-04-05 at 16:08, Ruud Linders wrote:
> I realise that my 'patch' isn't the perfect solution.
> But how much sense makes adding a 4-port card and getting
> ttyS14/15/44/45 for these 4-ports ?
does it matter really ????
(and if it does, why aren't you using udev ;)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-05 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 10:35 2.6.x kernels and ttyS45 for 6 serial ports ? Ruud Linders
2004-04-05 11:04 ` Russell King
2004-04-05 14:08 ` Ruud Linders
2004-04-05 14:21 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 16:37 Bjorn Helgaas
2004-04-06 16:45 ` Bjorn Helgaas
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=1081174866.4679.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkmp@xs4all.nl \
--cc=rmk+lkml@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.