linux-kernel - Re: [PATCH][uart] fit blackfin uart over sport driver into common uart inftrastructure (v2)

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: <4e5ebad50909172211s309cfcdbl7edd904178996799@mail.gmail.com>
Date:	Fri, 18 Sep 2009 13:11:50 +0800
From:	Sonic Zhang <sonic.adi@...il.com>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux Serial <linux-serial@...r.kernel.org>
Subject: Re: [PATCH][uart] fit blackfin uart over sport driver into common 
	uart inftrastructure (v2)

On Fri, Sep 18, 2009 at 12:54 PM, Sonic Zhang <sonic.adi@...il.com> wrote:
> On Thu, Sep 17, 2009 at 2:56 AM, Mike Frysinger <vapier.adi@...il.com> wrote:
>>
>> then we get proper device bindings between ttySS# and SPORT# by using
>> the .id field.  ttySS0 should always be SPORT0, ttySS1 should always
>> be SPORT1, etc...
>
> You can't either. Because the index of tty devices is increased
> automatically when you successfully register a uart port.  If sport0
> is used for devices other than uart, uart over sport1 is always bond
> to ttySS0.
>
>
OK. This looks possible. I will take a look.

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