From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Xavier Bestel <xavier.bestel@free.fr>,
Jason Dravet <dravet@hotmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: wrong number of serial port detected
Date: Wed, 7 Dec 2005 21:38:56 +0000 [thread overview]
Message-ID: <20051207213856.GN6793@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051207213128.GM6793@flint.arm.linux.org.uk>
On Wed, Dec 07, 2005 at 09:31:28PM +0000, Russell King wrote:
> On Wed, Dec 07, 2005 at 10:28:05PM +0100, Xavier Bestel wrote:
> > Le mercredi 07 d?cembre 2005 ? 21:15 +0000, Russell King a ?crit :
> >
> > > 4. User tries the well documented "setserial /dev/ttyS2 port 0x220 irq 5"
> > > procedure, which has been supported since Linux 1.x
> > >
> > > 5. User finds that, because there is no ttyS2 device in /dev, they
> > > can't configure their card.
> >
> > Well, instead of polluting everybody's /dev for the 3 users having such
> > cards, why not just tell the user to run
> > MAKEDEV /dev/ttyS2 ; setserial /dev/ttyS2 port 0x220 irq 5
> > instead ? (Or even mknod)
>
> Oh sorry. Mail me your root password and IP address, let me log in
> to your system, and I'll remove those device nodes right now. Thanks
> for pointing that out.
>
> Seriously, surely you aren't suggesting that I somehow have personal
> control over this?
Additionally, if you have a problem with this, the total number of
ports _is_ kernel configurable.
So if you're getting 32 ports from a distro targetted at the current
range of consumer hardware which commonly has maybe 1 or 2 and
possibly a modem card (iow probably max 4 ports), please take it up
with them.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-07 21:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 15:44 wrong number of serial port detected Jason Dravet
2005-12-07 15:50 ` Russell King
2005-12-07 19:59 ` Jason Dravet
2005-12-07 21:15 ` Russell King
2005-12-07 21:28 ` Xavier Bestel
2005-12-07 21:31 ` Russell King
2005-12-07 21:38 ` Russell King [this message]
2005-12-07 23:03 ` Dave Jones
2005-12-07 23:46 ` Russell King
2005-12-08 0:50 ` Dave Jones
2005-12-08 3:09 ` Dave Jones
2006-01-07 16:46 ` Russell King
2006-01-07 21:05 ` Dave Jones
2006-01-08 1:23 ` Jason Dravet
2006-01-08 9:08 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 3:02 Jason Dravet
2005-12-08 10:54 ` Russell King
2005-12-09 14:37 ` Jason Dravet
2005-12-09 17:27 ` Russell King
2005-12-09 19:54 ` Bjorn Helgaas
2005-12-10 1:46 ` Jason Dravet
2005-12-10 10:35 ` Russell King
2005-12-10 14:24 ` Jason Dravet
2005-12-10 15:46 ` Russell King
2005-12-10 17:56 ` Jason Dravet
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=20051207213856.GN6793@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=dravet@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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