From: Adrian Bunk <bunk@fs.tum.de>
To: Nicolas Pitre <nico@cam.org>
Cc: "George G. Davis" <davis_g@attbi.com>,
Jim Van Zandt <jrv@vanzandt.mv.com>,
device@lanana.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Why does the _DoubleTalk card_ not have a major assigned?
Date: Sun, 15 Dec 2002 02:01:37 +0100 [thread overview]
Message-ID: <20021215010137.GF27658@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0212041646190.775-100000@xanadu.home>
On Wed, Dec 04, 2002 at 04:50:50PM -0500, Nicolas Pitre wrote:
> On Wed, 4 Dec 2002, Adrian Bunk wrote:
>
> > This is indeed true for the Comtrol Rocketport card but there's no
> > major for the DoubleTalk card (and this is the card I wanted to write
> > about).
>
> Maybe because it doesn't need a static major? For funky hardware like the
> Doubletalk for which the number of Linux users worldwide can probably be
> counted on your fingers you can just grep /proc/devices for its allocated
> major and create the /dev node on the fly.
Thanks for your answer, I knew that this might have been a silly
question (and my confusing first mail didn't make it better...).
> Nicolas
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2002-12-15 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 20:55 Why does the Comtrol Rocketport card " Adrian Bunk
2002-12-04 21:16 ` George G. Davis
2002-12-04 21:33 ` Why does the _DoubleTalk card_ " Adrian Bunk
2002-12-04 21:50 ` Nicolas Pitre
2002-12-15 1:01 ` Adrian Bunk [this message]
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=20021215010137.GF27658@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=davis_g@attbi.com \
--cc=device@lanana.org \
--cc=jrv@vanzandt.mv.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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
Powered by JetHome