From: Manuel Lauss <manuel.lauss@googlemail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] High Speed Serial Problem
Date: Sun, 14 Mar 2010 17:34:50 +0100 [thread overview]
Message-ID: <f861ec6f1003140934n53d3b176je6faa7df3eeb3632@mail.gmail.com> (raw)
In-Reply-To: <20100314102459.20d7883b@osage.osagesoftware.com>
David,
I suggest you post this question to linux-kernel@vger.kernel.org and
linux-serial@vger.kernel.org
instead.
One question though: does your target have a real (physically real) uart chip?
There are some x86 systems out there which emulate a 8250 through SMM code,
which exhibit these kinds of failures at high baud rates. Do lower
baudrates work?
Best regards,
Manuel Lauss
next prev parent reply other threads:[~2010-03-14 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 14:24 [gentoo-embedded] High Speed Serial Problem David Relson
2010-03-14 16:34 ` Manuel Lauss [this message]
2010-03-14 17:14 ` David Relson
2010-03-14 17:51 ` Peter Stuge
2010-03-15 1:47 ` Peter Bell
2010-03-15 13:34 ` Bob Dunlop
2010-03-15 17:47 ` Relson, David
2010-03-20 19:02 ` [gentoo-embedded] SOLUTION (partial) was: " David Relson
2010-03-23 5:19 ` James Ausmus
2010-03-15 14:07 ` [gentoo-embedded] " wireless
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=f861ec6f1003140934n53d3b176je6faa7df3eeb3632@mail.gmail.com \
--to=manuel.lauss@googlemail.com \
--cc=gentoo-embedded@lists.gentoo.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