From: "George G. Davis" <davis_g@attbi.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Jim Van Zandt <jrv@vanzandt.mv.com>,
device@lanana.org, linux-kernel@vger.kernel.org
Subject: Re: Why does the Comtrol Rocketport card not have a major assigned?
Date: Wed, 04 Dec 2002 16:16:52 -0500 [thread overview]
Message-ID: <3DEE70C4.5D74A8B3@attbi.com> (raw)
In-Reply-To: 20021204205525.GE2544@fs.tum.de
Adrian Bunk wrote:
>
> Perhaps it's a silly question but I'd like to know why it is the way it
> is:
>
> The 2.2, 2.4 and 2.5 kernels include a driver for the Comtrol Rocketport
> card (drivers/char/dtlk.c) which uses a local major (it does a
> "register_chrdev(0, "dtlk", &dtlk_fops);
> ). Is there a reason why it doesn't have a fixed major assigned?
Huh?:
dtlk.c - DoubleTalk PC driver for Linux
That doesn't look like the Comtrol Rocketport (drivers/char/rocket.c)
driver to me. : )
Meanwhile 2.4.19 Documentation/devices.txt shows:
46 char Comtrol Rocketport serial card
0 = /dev/ttyR0 First Rocketport port
1 = /dev/ttyR1 Second Rocketport port
...
--
Regards,
George
> TIA
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-12-04 21:09 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 not have a major assigned? Adrian Bunk
2002-12-04 21:16 ` George G. Davis [this message]
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
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=3DEE70C4.5D74A8B3@attbi.com \
--to=davis_g@attbi.com \
--cc=bunk@fs.tum.de \
--cc=device@lanana.org \
--cc=jrv@vanzandt.mv.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.