From: Alexandre Courbot <Alexandre.Courbot@lifl.fr>
To: linux-serial@vger.kernel.org
Subject: Bug with 2.6 serial driver when in UART 8250 mode
Date: Thu, 19 Aug 2004 18:53:49 +0200 [thread overview]
Message-ID: <4124DB1D.8040401@lifl.fr> (raw)
Hello everybody,
I've sent this email to the lkml but it seems to have raised no
discussion at all. So I'm submitting it with hopes that someone will at
least have a look at the matter. Thanks! :)
For communicating with a serial device of ours we need to disable the
UART buffer (the device at the other end doesn't have a serial buffer at
all and therefore we can't use hardware control flow efficiently). The
only way to do this with Linux seems to pass the UART in 8250 mode,
which doesn't use the buffer:
# setserial /dev/ttyS0 uart 8250
We did that with success with 2.4 kernel series. Since most of our
machines are using 2.6, we tried to do the same on them, but noticed
something wrong: only one byte upon 16 is being sent. For instance, if I
$ echo -n "qwertyuiopasdfgh" > /dev/ttyS0
My device only receives the 'h', while with a 2.4 kernel it receives the
entire string.
So I think that for some reason, the UART buffer is not deactivated
while switching it to 8250 mode, and that the driver only sends the last
byte it contains when the interrupt is triggered.
I've tried to look at the code but unfortunately only lost myself
without being able to even identify the right source file to look at.
Sorry about that. :/
Could someone have a look at this or point me to the right section of
code so I do it myself?
Thanks,
Alex.
--
Alexandre Courbot
PhD Student - LIFL/RD2P
http://www.lifl.fr/~courbot/
reply other threads:[~2004-08-19 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4124DB1D.8040401@lifl.fr \
--to=alexandre.courbot@lifl.fr \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).