All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Fuzzey <mfuzzey@gmail.com>
To: linux-serial@vger.kernel.org, tsbogend@alpha.franken.de
Cc: linux-kernel@vger.kernel.org
Subject: Serial: sc26xx device name
Date: Sat, 21 Nov 2009 14:51:36 +0100	[thread overview]
Message-ID: <4B07F068.1090801@gmail.com> (raw)

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


             reply	other threads:[~2009-11-21 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21 13:51 Martin Fuzzey [this message]
2009-11-21 14:09 ` Serial: sc26xx device name Alan Cox
2009-11-21 14:23   ` Martin Fuzzey
2009-11-21 23:24     ` Alan Cox

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=4B07F068.1090801@gmail.com \
    --to=mfuzzey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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.