Why does the _DoubleTalk card_ not have a major assigned?

Adrian Bunk (bunk@fs.tum.de)
Wed, 4 Dec 2002 22:33:25 +0100


On Wed, Dec 04, 2002 at 04:16:52PM -0500, George G. Davis wrote:
> 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. : )

I was thinking about something else related to the Comtrol Rocketport
when writing my mail, and I mixed the two things... :-(

Please do a s/Comtrol Rocketport/DoubleTalk/g in my initial mail.

> 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
> ...

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).

> Regards,
> George

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

- 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/