From: Nick Craig-Wood <ncw@axis.demon.co.uk>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Ivan Passos <ivan@cyclades.com>, Andrew Morton <akpm@zip.com.au>,
"Michael H. Warfield" <mhw@wittsend.com>,
David Weinehall <tao@acc.umu.se>,
linux-kernel@vger.kernel.org
Subject: Re: Serial Driver Name Question (kernels 2.4.x)
Date: Thu, 10 Jan 2002 09:14:42 +0000 [thread overview]
Message-ID: <20020110091442.B9541@axis.demon.co.uk> (raw)
In-Reply-To: <200201062012.g06KCIu16158@vindaloo.ras.ucalgary.ca> <3C38BC19.72ECE86@zip.com.au> <200201070636.g076asR25565@vindaloo.ras.ucalgary.ca> <3C3A7DA7.381D033D@zip.com.au> <20020108071548.J5235@khan.acc.umu.se> <3C3A9048.CB80061A@zip.com.au> <20020108165851.B26294@alcove.wittsend.com> <3C3B6E96.8FB0341A@zip.com.au> <3C3B81D7.F1F43495@cyclades.com> <200201091636.g09GaU705860@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201091636.g09GaU705860@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Wed, Jan 09, 2002 at 09:36:30AM -0700
On Wed, Jan 09, 2002 at 09:36:30AM -0700, Richard Gooch wrote:
> Since you have to change all the drivers anyway, I'd prefer if
> _tty_make_name() was left unchanged, and instead you put the "%d" in
> each driver.name, thusly:
> #ifdef CONFIG_DEVFS_FS
> wod_driver.name = "tts/N%d";
> #else
> wod_driver.name = "ttyN%d";
> #endif
>
> The reason: maximum flexibility in the kinds of names we can
> support. If for some reason we want a name like "tts/N%d_A" and
> "tts/N%d_B" (say a driver with linked ttys, like the pty driver), we
> don't need to make a global change.
I think that is a good idea.
However these names appear in /proc/devices too which looks rather
ugly running with devfs at the moment...
# cat /proc/devices
Character devices:
1 mem
2 pty/m%d
3 pty/s%d
4 ttys/%d
5 serial/%d
10 misc
108 ppp
128 ptm
136 pts/%d
162 raw
--
Nick Craig-Wood
ncw@axis.demon.co.uk
next prev parent reply other threads:[~2002-01-10 9:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 2:07 Serial Driver Name Question (kernels 2.4.x) Ivan Passos
2002-01-03 4:40 ` Andrew Morton
2002-01-03 6:37 ` Richard Gooch
2002-01-03 7:03 ` Andrew Morton
2002-01-06 20:12 ` Richard Gooch
2002-01-06 20:36 ` Alan Cox
2002-01-06 20:27 ` Richard Gooch
2002-01-06 21:05 ` Andrew Morton
2002-01-07 6:36 ` Richard Gooch
2002-01-07 7:20 ` Andrew Morton
2002-01-08 5:03 ` Andrew Morton
2002-01-08 6:15 ` David Weinehall
2002-01-08 6:23 ` Andrew Morton
2002-01-08 18:54 ` Ivan Passos
2002-01-08 21:58 ` Michael H. Warfield
2002-01-08 22:11 ` Andrew Morton
2002-01-08 23:33 ` Ivan Passos
2002-01-09 16:36 ` Richard Gooch
2002-01-10 9:14 ` Nick Craig-Wood [this message]
2002-01-08 18:47 ` Ivan Passos
2002-01-03 16:32 ` Ivan Passos
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=20020110091442.B9541@axis.demon.co.uk \
--to=ncw@axis.demon.co.uk \
--cc=akpm@zip.com.au \
--cc=ivan@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhw@wittsend.com \
--cc=rgooch@ras.ucalgary.ca \
--cc=tao@acc.umu.se \
/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