linux-kernel - Re: [RESEND PATCH] serial: samsung: fix 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100924074247.GB11371@n2100.arm.linux.org.uk>
Date:	Fri, 24 Sep 2010 08:42:47 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Simon Richter <Simon.Richter@...yros.de>
Cc:	Darius Augulis <augulis.darius@...il.com>, kgene.kim@...sung.com,
	Ben Dooks <ben-linux@...ff.org>, paulius.zaleckas@...il.com,
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RESEND PATCH] serial: samsung: fix device name

On Fri, Sep 24, 2010 at 09:34:53AM +0200, Simon Richter wrote:
> Hi,
> 
> On Fri, Sep 24, 2010 at 09:57:19AM +0300, Darius Augulis wrote:
> 
> > It does - now devices are named /dev/s3c2410_serial, and patch changes
> > its name to /dev/ttySAC
> 
> I wonder if it'd make sense to name them ttyS[0-9]. I've never
> understood why the platform standard fixed serial ports on any device
> should have a different name.

It's called namespace.  If platform serial ports are different, then
they have to have a separate namespace otherwise things like
console= end up having to have a separate namespace from the one
which the user sees in the filesystem.

Moreover, you introduce a bunch of special cases into the 8250 serial
driver - or you simply exclude the 8250 serial driver being used on a
platform.
--
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/