mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Bryan Whitehead <driver@jpl.nasa.gov>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: 14 Mar 2003 15:23:50 +0000	[thread overview]
Message-ID: <1047655430.14792.86.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <3E6CD8B1.5070300@jpl.nasa.gov>

On Mon, 2003-03-10 at 18:25, Bryan Whitehead wrote:
> [snip]
> >       There is nothing in devfs that prevents you from registering
> > devfs devices even if they are not yet bound to specific hardware
> > (you do not need a sysfs mapping, for example).  So, you should be
> > able to register /dev/tts/0..N at initialization, where N is the
> > maximum number of serial devices you want to support.
> 
> are you saying there is a way to force devfs to make more entries in 
> /dev/tts/ without any hardware being attached to the entries? Then i can 
> use setserial? so on boot I'd have 4 entries in /dev/tts ?

Don't do this. The whole concept of opening a device node for a device
which is _absent_, then doing magic ioctls on it to make the driver
probe for the hardware, is utterly bogus.

Fix it properly instead -- disallow opening of a /dev/ttySx node with
uart type unknown, and implement a proper way to tell the serial driver
'please look for a device _here_', via sysfs or something. 

-- 
dwmw2


  reply	other threads:[~2003-03-14 15:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-08 19:48 Adam J. Richter
2003-03-10 18:25 ` Bryan Whitehead
2003-03-14 15:23   ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-15  0:54 Ed Vance
2003-03-15  0:02 Adam J. Richter
2003-03-14 20:28 Adam J. Richter
2003-03-14 20:43 ` Russell King
2003-03-14 19:49 Ed Vance
2003-03-14 20:07 ` Russell King
2003-03-14 19:06 Adam J. Richter
2003-03-10 18:37 Adam J. Richter
2003-03-10 17:12 Ed Vance
2003-03-08  1:30 Ed Vance
2003-03-07 23:57 Ed Vance
2003-03-08  0:59 ` Bryan Whitehead
2003-03-11  9:07 ` Theodore Ts'o
2003-03-07 23:40 Ed Vance
2003-03-08  0:15 ` Marek Michalkiewicz
2003-03-07 23:04 Ed Vance
2003-03-07 23:17 ` Bryan Whitehead
2003-03-07 22:51 Bryan Whitehead
2003-03-07 22:55 ` Bryan Whitehead
2003-03-07 23:28 ` Bryan Whitehead
2003-03-08  0:10   ` Marek Michalkiewicz
2003-03-07 23:38 ` Theodore Ts'o
2003-03-11 23:12 ` whitnl73

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=1047655430.14792.86.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=adam@yggdrasil.com \
    --cc=driver@jpl.nasa.gov \
    --cc=linux-kernel@vger.kernel.org \
    /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®