From: Russell King <rmk+lkml@arm.linux.org.uk>
To: akennedy@techmoninc.com
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Serial console issues.
Date: Thu, 15 Feb 2007 10:49:08 +0000 [thread overview]
Message-ID: <20070215104907.GB15772@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070214173922.bfc52cea95091b0fffcb409eab6296ba.d67be632a9.wbe@email.secureserver.net>
On Wed, Feb 14, 2007 at 05:39:22PM -0700, akennedy@techmoninc.com wrote:
> Well, this is the most bastardized sucker I've ever seen. . . I have had
> no end of trouble with it (couldn't even get a boot loader to work with
> it - had to write my own). And, as luck would have it, the serial port
> is no different. Using setserial, I changed the type of this port to a
> 16550A and all my problems went away. The question now remains: How
> can I FORCE the Linux serial driver to see this as a 16550A -- As I
> before stated, I know that this has a 16-byte buffer. Therefore, the
> 16750 with its mammoth buffer size is killing this serial port. Short
> of modifying the kernel (which I'd rather not do) or including the
> setserial with the kernel image (also I'd rather not do as I only have
> 2.3 MB of storage on this device) I need a command line parameter to
> control the serial line -- is there one? A build option? PLEASE
> SOMETHING???
No. Use setserial which is a small tool to achieve what you require.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-02-15 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 0:39 akennedy
2007-02-15 10:49 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-14 23:11 akennedy
2007-02-15 0:24 ` Alan
2007-02-12 20:39 Andy Kennedy
2007-02-12 20:56 ` David Lang
2007-02-13 20:20 ` Andy Kennedy
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=20070215104907.GB15772@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akennedy@techmoninc.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®