linux-kernel - Re: questions about 8250 uart support for adhoc boards

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 for Android: free password hash cracker in your pocket

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

Message-ID: <45E43F20.9060300@kuchera.com>
Date:	Tue, 27 Feb 2007 09:24:32 -0500
From:	Rob Prowel <prowel@...hera.com>
To:	Rob Prowel <prowel@...hera.com>,
	Stuart MacDonald <stuartm@...necttech.com>,
	linux-kernel@...r.kernel.org
Subject: Re: questions about 8250 uart support for adhoc boards

Russell King wrote:
> On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote:
>   
>> See below for a (script) dump of that demonstrates the behavior I 
>> describe.  Additional ports are not configurable until a driver such as 
>> fourport is loaded.  This is in 2.6.20.1 and 2.6.17 (those versions I 
>> have tested).
>>     
>
> Check what /proc/tty/driver/serial contains, rather than relying on
> setserial.  setserial distributed by distros hasn't kept up with the
> changes in the serial layer.
>
>   
The setserial being used is the latest one from sourceforge.  Its 
relevant output matches the /proc entries.  The problem still remains 
though.  Entries for ttyS4 and up seem to be read-only until I add a 
supplemental driver such as fourport.


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