Message-ID: <45E43F20.9060300@kuchera.com>
Date: Tue, 27 Feb 2007 09:24:32 -0500
From: Rob Prowel <prowel@kuchera.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070104 Red Hat/1.0.7-0.6.fc5 SeaMonkey/1.0.7
MIME-Version: 1.0
To: Rob Prowel <prowel@kuchera.com>,
       Stuart MacDonald <stuartm@connecttech.com>,
       linux-kernel@vger.kernel.org
Subject: Re: questions about 8250 uart support for adhoc boards
References: <000001c75853$3e9599f0$294b82ce@stuartm> <45E312C1.5050802@kuchera.com> <20070226180554.GA16857@flint.arm.linux.org.uk>
In-Reply-To: <20070226180554.GA16857@flint.arm.linux.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 25

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/