devices.txt errors

devices.txt errors

[Albert Cahalan]

Major 216 was ttyUB%d (looks normal), but is now rfcomm%d instead?
The description claims that the device is a tty, yet it no longer
has a tty name?

Char major 204, the low-density serial ports, has some
sort of problem with the /dev/ttyCPM%d devices. Depending
on how I read things, there are 2, 4, or 6 of these.

Minors claimed: 46, 47
Minors available: 46, 47, 48, 49
Names claimed:  0, 1, 2, 3, 4, 5
The description:  0, 1, 2, 3, 4, 5

Here it is in context:

44 = /dev/ttyMM0               Marvell MPSC - port 0
45 = /dev/ttyMM1               Marvell MPSC - port 1
46 = /dev/ttyCPM0              PPC CPM (SCC or SMC) - port 0
   ...
47 = /dev/ttyCPM5              PPC CPM (SCC or SMC) - port 5
50 = /dev/ttyIOC0              Altix serial card
   ...
81 = /dev/ttyIOC31             Altix serial card
82 = /dev/ttyVR0               NEC VR4100 series SIU
83 = /dev/ttyVR1               NEC VR4100 series DSIU

Less serious:

Major 78 and major 112 claim the same name.

Some names, like "/dev/iseries/vtty%d", are too damn big.
Keeping things to "/dev/tty?????" would be appreciated.

Last I checked, ttyD%d didn't match the code.

Re: devices.txt errors

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

On Sun, 9 Jul 2006 02:49:19 -0400 "Albert Cahalan" <acahalan@gmail.com> wrote:
>
> Some names, like "/dev/iseries/vtty%d", are too damn big.

As far as I know they were never used and certainly aren't now.  We did
once use /dev/viocons/%d, but that went away a long time ago (before the
code was in the mainline kernel).  Major 229 is now used by the pSeries
Hypervisor consoles (/dev/hvc%d) and hopefully soon by a new iSeries
hypervisor console with the same name.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: devices.txt errors

[Albert Cahalan]

On 7/9/06, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Sun, 9 Jul 2006 02:49:19 -0400 "Albert Cahalan" <acahalan@gmail.com> wrote:
> >
> > Some names, like "/dev/iseries/vtty%d", are too damn big.
>
> As far as I know they were never used and certainly aren't now.  We did
> once use /dev/viocons/%d, but that went away a long time ago (before the
> code was in the mainline kernel).  Major 229 is now used by the pSeries
> Hypervisor consoles (/dev/hvc%d) and hopefully soon by a new iSeries
> hypervisor console with the same name.

Since that still isn't in devices.txt...

/dev/ttyHV%d would match the standard pattern better.
(assuming you only need 3-digit numbers)

Re: devices.txt errors

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Sun, 9 Jul 2006 13:22:53 -0400 "Albert Cahalan" <acahalan@gmail.com> wrote:
>
> On 7/9/06, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > On Sun, 9 Jul 2006 02:49:19 -0400 "Albert Cahalan" <acahalan@gmail.com> wrote:
> > >
> > > Some names, like "/dev/iseries/vtty%d", are too damn big.
> >
> > As far as I know they were never used and certainly aren't now.  We did
> > once use /dev/viocons/%d, but that went away a long time ago (before the
> > code was in the mainline kernel).  Major 229 is now used by the pSeries
> > Hypervisor consoles (/dev/hvc%d) and hopefully soon by a new iSeries
> > hypervisor console with the same name.
> 
> Since that still isn't in devices.txt...
> 
> /dev/ttyHV%d would match the standard pattern better.
> (assuming you only need 3-digit numbers)

However, it is already in the mainline kernel (the pSeries HV console) and
in common use ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: devices.txt errors

[Greg KH]

On Sun, Jul 09, 2006 at 02:49:19AM -0400, Albert Cahalan wrote:
> Major 216 was ttyUB%d (looks normal), but is now rfcomm%d instead?
> The description claims that the device is a tty, yet it no longer
> has a tty name?

Fun with bluetooth issues.  The ttyUB driver is now gone, and the bluez
code uses it instead.  Take it up with those developers if you have
questions...

thanks,

greg k-h