Subject: Re: Serial issue
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>
In-Reply-To: <44E602C8.3030805@microgate.com>
References: <1155862076.24907.5.camel@mindpipe>
	 <1155915851.3426.4.camel@amdx2.microgate.com>
	 <1155923734.2924.16.camel@mindpipe>  <44E602C8.3030805@microgate.com>
Content-Type: text/plain
Date: Fri, 18 Aug 2006 14:17:04 -0400
Message-Id: <1155925024.2924.22.camel@mindpipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 978
Lines: 28

On Fri, 2006-08-18 at 13:11 -0500, Paul Fulghum wrote:
> 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)
> 

I think it's just using the kermit file transfer protocol.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/