public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Jon Smirl <jonsmirl@gmail.com>, Vojtech Pavlik <vojtech@suse.cz>,
	Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Christmas list for the kernel
Date: Wed, 23 Nov 2005 15:51:44 +0000	[thread overview]
Message-ID: <20051123155143.GE15449@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43848D37.4080007@drzeus.cx>

On Wed, Nov 23, 2005 at 04:39:35PM +0100, Pierre Ossman wrote:
> Russell King wrote:
> >On Wed, Nov 23, 2005 at 04:20:00PM +0100, Pierre Ossman wrote:
> >  
> >>But if no hardware is connected to those devices, then where does the 
> >>driver route the setserial stuff?
> >>    
> >
> >setserial /dev/ttyS2 port 0x200 irq 5 autoconfig
> >
> >and you might then end up with another serial port detected.  If
> >/dev/ttyS2 and above do not exist, you can't do that.  That would
> >in turn effectively prevent folk with some serial cards using them
> >with Linux without editing and rebuilding their kernel.
> 
> Ah. But why is this not done through module parameters? That would be 
> more consistent with how you specify resources for other drivers.

Take a moment to consider how you would supply a large number of ports
via this method - eg, 16 ports, where a port IO and IRQ configuration
takes about 10 characters ("0x1234,11"), and then what about the baud
base, probe flags (auto_irq, skip_test) ?

Also consider that ttyS0 might be your serial console for your headless
box, so you're unable to build 8250 as a module in the first place.

It really isn't simple.  Serial _is_ special - and that is why it keeps
sprouting new and wonderful initialisation paths.  I'd rather not add
yet another gods greatest invention initialisation path on top of those
we already have.

> >As for the rest of the "setserial stuff" it gets recorded against
> >the port and remembered for when the hardware turns up, which it
> >may do if it's your PCMCIA modem card.
> 
> This could be a bit more questionable. Setting the initial state of 
> hardware is better done (IMHO) by reacting to some hotplug event. E.g. 
> fedora uses an 'install' line in modprobe.conf to restore mixer state 
> for sound cards.

Actually, my example was slightly flawed - when the hardware turns up
it gets reset back to something sane.  So the settings are merely
remembered while the hardware doesn't exist.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-11-23 15:52 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 18:31 Christmas list for the kernel Jon Smirl
2005-11-22 18:39 ` Alistair John Strachan
2005-11-22 19:10   ` Jon Smirl
2005-11-23  0:43     ` Andrew Morton
2005-11-23  1:09       ` Jon Smirl
2005-11-23  1:37         ` Josh Boyer
2005-11-23  2:00         ` Andrew Morton
2005-11-23  5:18           ` Jon Smirl
2005-11-23  5:45             ` Andrew Morton
2005-11-23 16:12       ` Bill Davidsen
2005-11-23 19:27         ` Andrew Morton
2005-11-22 19:31 ` Christoph Hellwig
2005-11-22 19:57   ` Jon Smirl
2005-11-23 22:16     ` Pavel Machek
2005-11-23 22:12   ` Pavel Machek
2005-11-22 20:49 ` Greg KH
2005-11-22 21:13   ` Jon Smirl
2005-11-22 21:28     ` Kasper Sandberg
2005-11-22 21:41       ` Jon Smirl
2005-11-22 21:56         ` David Lang
2005-11-22 22:00         ` Anton Altaparmakov
2005-11-22 23:36         ` Alan Cox
2005-11-22 23:56           ` Jon Smirl
2005-11-23  9:09             ` Russell King
2005-11-23 16:07           ` Bill Davidsen
2005-11-23  8:47         ` Denis Vlasenko
2005-11-23 14:44         ` Vojtech Pavlik
2005-11-23 17:21           ` Gene Heskett
2005-11-23 17:30             ` Russell King
2005-11-23 19:28               ` Bill Davidsen
2005-11-22 23:35     ` Alan Cox
2005-11-22 23:58       ` Jon Smirl
2005-11-23  0:37         ` Alistair John Strachan
2005-11-23 11:19         ` Alan Cox
2005-11-23 12:17     ` Vojtech Pavlik
2005-11-23 14:43       ` Jon Smirl
2005-11-23 15:03         ` Russell King
2005-11-23 15:12           ` Jon Smirl
2005-11-23 15:56             ` Marc Koschewski
2005-11-23 16:05               ` Russell King
2005-11-23 16:37                 ` Jon Smirl
2005-11-23 16:49                   ` Vojtech Pavlik
2005-11-23 16:59                     ` Jon Smirl
2005-11-23 17:05                       ` Marc Koschewski
2005-11-23 17:13                         ` Jon Smirl
2005-11-23 17:16                           ` Vojtech Pavlik
2005-11-23 17:24                           ` Marc Koschewski
2005-11-23 17:15                       ` Vojtech Pavlik
2005-11-23 19:32                     ` Bill Davidsen
2005-11-23 15:19           ` Jon Smirl
2005-11-23 15:25             ` Russell King
2005-11-23 15:31               ` Jon Smirl
2005-11-23 15:36                 ` Russell King
2005-11-23 16:02             ` Marc Koschewski
2005-11-23 16:16               ` Russell King
2005-11-23 16:23                 ` Marc Koschewski
2005-11-23 16:23                 ` Vojtech Pavlik
2005-11-23 16:27                   ` Russell King
2005-11-23 16:31                     ` Dmitry Torokhov
2005-11-23 16:34                       ` Vojtech Pavlik
2005-11-23 16:33                     ` Vojtech Pavlik
2005-11-23 15:20           ` Pierre Ossman
2005-11-23 15:29             ` Russell King
2005-11-23 15:39               ` Pierre Ossman
2005-11-23 15:51                 ` Russell King [this message]
2005-11-23 15:49               ` Jon Smirl
2005-11-23 15:56                 ` Russell King
2005-11-23 16:32           ` Bill Davidsen
2005-11-23 16:50             ` Jon Smirl
2005-11-23 15:49         ` John Stoffel
2005-11-23 15:27       ` Martin Mares
2005-11-22 21:28   ` Dmitry Torokhov
2005-11-22 23:33   ` Alan Cox
2005-11-23  7:10   ` Early boot issues (WAS: Christmas list for the kernel) Benjamin Herrenschmidt
2005-11-23 19:47     ` Andi Kleen
2005-11-22 22:11 ` Christmas list for the kernel Bill Davidsen
2005-11-24  4:17   ` Rob Landley
2005-11-23 22:23 ` Pavel Machek

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=20051123155143.GE15449@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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