From: "Jason Dravet" <dravet@hotmail.com>
To: rmk+lkml@arm.linux.org.uk
Cc: bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org
Subject: Re: wrong number of serial port detected
Date: Sat, 10 Dec 2005 11:56:12 -0600 [thread overview]
Message-ID: <BAY103-F14F00806E485B60FFA140CDF440@phx.gbl> (raw)
In-Reply-To: <20051210154628.GA22707@flint.arm.linux.org.uk>
>From: Russell King <rmk+lkml@arm.linux.org.uk>
>To: Jason Dravet <dravet@hotmail.com>
>CC: bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org
>Subject: Re: wrong number of serial port detected
>Date: Sat, 10 Dec 2005 15:46:28 +0000
>
>On Sat, Dec 10, 2005 at 08:24:59AM -0600, Jason Dravet wrote:
> > How is this for an idea? The serial driver enumerates ACPI, PNPBIOS, or
> > whaterver it needs for the onboard serial ports. If you have a PCI
>based
> > serial card it would show up in the emuneration of the PCI bus, right?
>For
> > the case of ISA serial cards couldn't they have an option in
>modprobe.conf
> > to tell the kernel about the ISA serial card and the proper number of
> > serial ports on the card itself?
>
>That's already thought about and rejected.
>
>If you want to pass a string telling the serial module where the ports
>are, you could be looking at a very _long_ string. You need to specify
>the IO address, IRQ and base baud as a minimum for every port, along
>with optional flags.
>
>Assuming 5 characters for the IO address, 1 for the IRQ, and 6 for
>the baud base, plus 2 for separators between each of these, and one
>character separator per group, you're looking at 15 characters
>minimum per port. For 8 ports, that's 120 characters. 16 would
>be 240 characters. If the driver is built-in to the kernel, you're
>limited to 255 characters to describe all kernel options, so you
>couldn't hope to describe 32 ports.
I was not aware that it worked like that. My last experience with ISA cards
was to put a line in the modules.conf that pointed to the base IO and IRQ
for the card. There was a serperate file that setup the serial ports. This
was way back in RedHat 6.x days. Thank you for the new information.
>The alternative is something like Dave's patch which allows you to
>tell the driver the number of ports you want to support and setserial.
Dave's patch is good and I look forward to seeing it in the kernel.
Thanks,
Jason
next prev parent reply other threads:[~2005-12-10 17:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 15:44 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
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
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=BAY103-F14F00806E485B60FFA140CDF440@phx.gbl \
--to=dravet@hotmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®