From: Paul Fulghum <paulkf@microgate.com>
To: Lee Revell <rlrevell@joe-job.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:11:20 -0500 [thread overview]
Message-ID: <44E602C8.3030805@microgate.com> (raw)
In-Reply-To: <1155923734.2924.16.camel@mindpipe>
Lee Revell wrote:
> 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?
I can't think of any. The interrupts are occurring
and being serviced. Nothing else seems to be sitting
on that interrupt. It's reaching a bit: maybe there
is some console output interfering with the
file transfer protocol, but it only occurs with
interrupt enabled because of some initial timing?
(polling mode may delay things enough to work)
What protocol is ckermit using? (zmodem, etc)
--
Paul Fulghum
Microgate Systems, Ltd.
next prev parent reply other threads:[~2006-08-18 18:11 UTC|newest]
Thread overview: 23+ 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
2006-08-18 18:11 ` Paul Fulghum [this message]
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
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=44E602C8.3030805@microgate.com \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox