From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dave Jones <davej@redhat.com>,
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 23:46:04 +0000 [thread overview]
Message-ID: <20051207234603.GQ6793@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051207230302.GD22690@redhat.com>
On Wed, Dec 07, 2005 at 06:03:02PM -0500, Dave Jones wrote:
> Ok, how about something along the lines of this (completely untested) patch,
> which adds a runtime param to lower the number of registered ports,
> also allowing a default to be set for common cases.
>
> Would something like this be acceptable ?
Sure, looks fine. The new parameter should probably be documented
though, so folk know about it.
> @@ -2653,6 +2657,9 @@ module_param(share_irqs, uint, 0644);
> MODULE_PARM_DESC(share_irqs, "Share IRQs with other non-8250/16x50 devices"
> " (unsafe)");
>
> +module_param(nr_uarts, uint, 0644);
> +MODULE_PARM_DESC(nr_uarts, "Maximum number of UARTs supported.");
Should this help string include the compile-time maximum somehow?
What limits it to the compile-time maximum?
> diff -urpN --exclude-from=/home/devel/davej/.exclude vanilla/drivers/serial/Kconfig linux-2.6.14/drivers/serial/Kconfig
> --- vanilla/drivers/serial/Kconfig 2005-12-07 17:56:56.000000000 -0500
> +++ linux-2.6.14/drivers/serial/Kconfig 2005-12-07 17:53:34.000000000 -0500
> @@ -95,6 +100,15 @@ config SERIAL_8250_NR_UARTS
> PCI enumeration and any ports that may be added at run-time
> via hot-plug, or any ISA multi-port serial cards.
>
> +config SERIAL_8250_RUNTIME_UARTS
> + int "Number of 8250/16550 serial ports to register at runtime"
> + depends on SERIAL_8250
> + default "4"
Can this be restricted to a range of 1 to SERIAL_8250_UARTS ?
> + help
> + Set this to the maximum number of serial ports you want
> + the kernel to register at boot time. This can be overriden
> + with the parameter "nr_uarts".
And should we also give a pointer to the boot-time parameter (which
I think will be 8250.nr_uarts ?)
--
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 23:46 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
2005-12-07 23:03 ` Dave Jones
2005-12-07 23:46 ` Russell King [this message]
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=20051207234603.GQ6793@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=davej@redhat.com \
--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 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.