From: "Kalle Pokki" <kalle.pokki@iki.fi>
To: "Boris Shteinbock" <boris@fabiotec.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] CPM_UART: Fix non-console transmit
Date: Thu, 19 Oct 2006 22:07:19 +0300 [thread overview]
Message-ID: <a425f86c0610191207i3a9977c9ree3f66cbfb52950e@mail.gmail.com> (raw)
In-Reply-To: <4537A263.3010104@fabiotec.com>
On 10/19/06, Boris Shteinbock <boris@fabiotec.com> wrote:
>
> After applying your patch,
> the transmission doesn't take place at all..
> just hanging in write...
> at least it is possible to exit the program.
That's strange. No matter how I test the driver it now works
perfectly for me with my patches. Did you apply them both? However, I
cannot see why the length of the transmission would cause any
difference.
What is you baud rate on SMC2? How about the TX buffer count and TX
FIFO size - have you changed them? I suspect that cpm_uart_tx_pump()
could disable your TX interrupt when you have all characters queued in
separate TX buffers. I'll test this theory tomorrow.
You might want to strace your program and post the results here. Also put
#define DEBUG
in front of cpm_uart_core.c and cpm_uart_cpm2.c and recompile. You'll
get a lot of debugging messages after
echo 8 > /proc/sys/kernel/printk
That should give us clues what goes wrong. The output of
stty -F /dev/ttyCPM1 -a
would also help.
next prev parent reply other threads:[~2006-10-20 3:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 16:05 [PATCH] CPM_UART: Fix non-console transmit Boris Shteinbock
2006-10-19 19:07 ` Kalle Pokki [this message]
2006-10-31 10:24 ` Laurent Pinchart
2006-10-31 11:52 ` Kalle Pokki
-- strict thread matches above, loose matches on Subject: below --
2006-10-19 12:52 Kalle Pokki
2006-10-31 15:08 ` Vitaly Bordug
2006-11-01 3:35 ` Paul Mackerras
2006-11-01 7:52 ` Kalle Pokki
2006-10-19 12:25 kalle.pokki
2006-10-19 19:28 ` Vitaly Bordug
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=a425f86c0610191207i3a9977c9ree3f66cbfb52950e@mail.gmail.com \
--to=kalle.pokki@iki.fi \
--cc=boris@fabiotec.com \
--cc=linuxppc-embedded@ozlabs.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).