From: "Ralf HECKHAUSEN" <RHeckhau@frequentis.com>
To: "<"<linuxppc-embedded@lists.linuxppc.org>
Subject: UART driver problem
Date: Fri, 21 Jan 2000 10:15:21 +0100 [thread overview]
Message-ID: <s88831d7.021@mail.frequentis.com> (raw)
I have a strange problem with the uart driver. The 8xx_write in uart.c always fails because copy_from_user returns 0 instead of the requested number of bytes. When I ignore the comparison with the requested number of bytes everything works ok, the correct bytes are transmitted and 8xx_write returns something >0.
The next strange thing: a write to a tty file descriptor sometimes returns a negative number, although the output succeded. perror in this case outputs an unknown error.
Does anyone know this problems?
Ralf
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-01-21 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 9:15 Ralf HECKHAUSEN [this message]
2000-01-25 13:27 ` [PATCH] Re: UART driver problem Marcus Sundberg
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 14:41 Pavel Roskin
2000-04-05 5:34 ` Graham Stoney
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=s88831d7.021@mail.frequentis.com \
--to=rheckhau@frequentis.com \
--cc=linuxppc-embedded@lists.linuxppc.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).