linux-kernel - Serial: sc26xx device name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B07F068.1090801@gmail.com>
Date:	Sat, 21 Nov 2009 14:51:36 +0100
From:	Martin Fuzzey <mfuzzey@...il.com>
To:	linux-serial@...r.kernel.org, tsbogend@...ha.franken.de
CC:	linux-kernel@...r.kernel.org
Subject: Serial: sc26xx device name

Hi all,
I noticed the sc26xx driver uses ttySC205 / ttySC206 for device name.

grep ttySC Documentation/devices.txt gives
          8 = /dev/ttySC0        SCI serial port (SuperH) - port 0
          9 = /dev/ttySC1        SCI serial port (SuperH) - port 1
         10 = /dev/ttySC2        SCI serial port (SuperH) - port 2
         11 = /dev/ttySC3        SCI serial port (SuperH) - port 3
         205 = /dev/ttySC0        SC26xx serial port 0
         206 = /dev/ttySC1        SC26xx serial port 1
         207 = /dev/ttySC2        SC26xx serial port 2
         208 = /dev/ttySC3        SC26xx serial port 3
          8 = /dev/cusc0        Callout device for ttySC0
          9 = /dev/cusc1        Callout device for ttySC1
         10 = /dev/cusc2        Callout device for ttySC2
         11 = /dev/cusc3        Callout device for ttySC3

Removing the line:
    sc26xx_reg.tty_driver->name_base = sc26xx_reg.minor;
makes it revert to ttySC0

So two questions:
1) Who is right (the driver or devices.txt)?
2) How are device name conflicts handled?

Cheers,

Martin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/