From: Rob Prowel <prowel@kuchera.com>
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
Date: Tue, 27 Feb 2007 09:24:32 -0500 [thread overview]
Message-ID: <45E43F20.9060300@kuchera.com> (raw)
In-Reply-To: <20070226180554.GA16857@flint.arm.linux.org.uk>
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.
next prev parent reply other threads:[~2007-02-27 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 17:05 questions about 8250 uart support for adhoc boards Rob Prowel
2007-02-23 20:21 ` Russell King
2007-02-23 20:48 ` Rob Prowel
2007-02-24 20:34 ` Stuart MacDonald
2007-02-26 17:02 ` Rob Prowel
2007-02-26 18:05 ` Russell King
2007-02-27 14:24 ` Rob Prowel [this message]
2007-02-27 17:38 ` Russell King
2007-02-27 19:06 ` Stuart MacDonald
2007-02-27 20:40 ` Rob Prowel
2007-03-08 15:16 ` Russell King
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=45E43F20.9060300@kuchera.com \
--to=prowel@kuchera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartm@connecttech.com \
/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.