From: Lee Revell <rlrevell@joe-job.com>
To: Paul Fulghum <paulkf@microgate.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: Serial issue
Date: Fri, 18 Aug 2006 13:55:33 -0400 [thread overview]
Message-ID: <1155923734.2924.16.camel@mindpipe> (raw)
In-Reply-To: <1155915851.3426.4.camel@amdx2.microgate.com>
On Fri, 2006-08-18 at 10:44 -0500, Paul Fulghum wrote:
> On Thu, 2006-08-17 at 20:47 -0400, Lee Revell wrote:
> > I've found a weird serial bug. My host is a Via EPIA M-6000 running
> > 2.6.17 connected to a PPC Yosemite board running 2.6.13.
> >
> > In all cases the serial console works great. But, with the default
> > setting of IRQ 4, Kermit file transfers via the serial interface simply
> > time out. However if I use polling mode (setserial /dev/ttyS0 irq 0 on
> > the host), file transfers work.
> >
> > When set to IRQ 4, the interrupt count does increase.
> >
> > # cat /proc/tty/driver/serial
> > serinfo:1.0 driver revision:
> > 0: uart:16550A port:000003F8 irq:4 tx:267 rx:667 DSR|CD
> > [...]
> >
> > Any ideas? I'm guessing it might be a quirk of the VIA chipset?
>
> You mention serial console. Hasn't there been some changes
> related to reenabling the THRE interrupt after sending
> console data? IIRC the changes fixed transmit stalls on
> some machines but broke things on other machine.
I tried Paul's suggestion:
--- drivers/serial/8250.c~ 2006-06-17 21:49:35.000000000 -0400
+++ drivers/serial/8250.c 2006-08-18 12:57:16.000000000 -0400
@@ -2263,7 +2263,7 @@
* and restore the IER
*/
wait_for_xmitr(up, BOTH_EMPTY);
- serial_out(up, UART_IER, ier);
+ serial_out(up, UART_IER, ier | UART_IER_THRI);
if (locked)
spin_unlock_irqrestore(&up->port.lock, flags);
But it had no effect.
Could it be a hardware-specific bug? After all VIA chipsets are
notorious for interrupts not working right.
Any other suggestions?
Lee
next prev parent reply other threads:[~2006-08-18 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 0:47 Serial issue Lee Revell
2006-08-18 15:44 ` Paul Fulghum
2006-08-18 16:25 ` Lee Revell
2006-08-18 16:34 ` Lee Revell
2006-08-18 17:55 ` Lee Revell [this message]
2006-08-18 18:11 ` Paul Fulghum
2006-08-18 18:17 ` Lee Revell
2006-08-18 18:36 ` Russell King
2006-08-18 18:40 ` Lee Revell
2006-08-18 18:52 ` Russell King
2006-08-18 19:06 ` Paul Fulghum
2006-08-18 19:09 ` Russell King
2006-08-18 19:15 ` linux-os (Dick Johnson)
2006-08-18 19:21 ` Lee Revell
2006-08-18 20:05 ` linux-os (Dick Johnson)
2006-08-18 20:25 ` Mark Hounschell
2006-08-18 20:28 ` Lee Revell
2006-08-18 20:32 ` Mark Hounschell
2006-08-18 20:36 ` Russell King
2006-08-18 20:57 ` Mark Hounschell
2006-08-18 20:34 ` Russell King
2006-08-18 20:54 ` Lee Revell
2006-08-18 21:02 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 21:45 Lee Revell
2006-07-26 21:57 ` Wolfgang Denk
2006-07-26 22:00 ` Lee Revell
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=1155923734.2924.16.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.