From: "Adam J. Richter" <adam@yggdrasil.com>
To: driver@jpl.nasa.gov
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs + PCI serial card = no extra serial ports
Date: Mon, 10 Mar 2003 10:37:20 -0800 [thread overview]
Message-ID: <200303101837.KAA05343@adam.yggdrasil.com> (raw)
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 ?
I don't know what you mean by "force." devfs_register does
not know (or "care") if there is a physical device associated with the
major/minor/ops that it is given.
>Or are you saying I write a script to goto /dev/tts after boot and mknod
>the ports that are missing?
User level programs can also do mknod() calls in devfs
directories, if that is what you are referring to, so you could
do "mknod /dev/tts/3 c 4 68", for example.
By the way, I notice that 2.5.64 with devfs already creates
/dev/tts/0 through /dev/tts/49.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-03-10 18:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 18:37 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-15 0:54 devfs + PCI serial card = no extra serial ports 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 17:12 Ed Vance
2003-03-08 19:48 Adam J. Richter
2003-03-10 18:25 ` Bryan Whitehead
2003-03-14 15:23 ` David Woodhouse
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=200303101837.KAA05343@adam.yggdrasil.com \
--to=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;
as well as URLs for NNTP newsgroup(s).