This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Apr 26 23:16:13 2024 Delivery-date: Fri, 18 Aug 2006 19:15:56 +0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932496AbWHRTPX (ORCPT ); Fri, 18 Aug 2006 15:15:23 -0400 Received: from spirit.analogic.com ([204.178.40.4]:36621 "EHLO spirit.analogic.com") by vger.kernel.org with ESMTP id S932487AbWHRTPV convert rfc822-to-8bit (ORCPT ); Fri, 18 Aug 2006 15:15:21 -0400 Received: from chaos.analogic.com ([10.112.50.11]) by phoenix.analogic.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 18 Aug 2006 15:15:19 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Received: from chaos.analogic.com (localhost [127.0.0.1]) by chaos.analogic.com (8.12.11/8.12.11) with ESMTP id k7IJFJmf019880; Fri, 18 Aug 2006 15:15:19 -0400 Received: (from linux-os@localhost) by chaos.analogic.com (8.12.11/8.12.11/Submit) id k7IJFJo6019879; Fri, 18 Aug 2006 15:15:19 -0400 X-OriginalArrivalTime: 18 Aug 2006 19:15:20.0013 (UTC) FILETIME=[A5748FD0:01C6C2FA] content-class: urn:content-classes:message Subject: Re: Serial issue Date: Fri, 18 Aug 2006 15:15:19 -0400 Message-Id: In-Reply-To: <1155925024.2924.22.camel@mindpipe> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Serial issue Thread-Index: AcbC+qV+bKDln2CPR4WY5elZ8tHO8w== References: <1155862076.24907.5.camel@mindpipe> <1155915851.3426.4.camel@amdx2.microgate.com> <1155923734.2924.16.camel@mindpipe> <44E602C8.3030805@microgate.com> <1155925024.2924.22.camel@mindpipe> From: "linux-os \(Dick Johnson\)" To: "Lee Revell" Cc: "Paul Fulghum" , "linux-kernel" , "Russell King" Reply-To: "linux-os \(Dick Johnson\)" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 18 Aug 2006, Lee Revell wrote: > 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 A file-transfer protocol??? Has he got hardware the __required__ hardware flow-control enabled on both ends? One can't spew high-speed serial data out forever without a hardware handshake. Cheers, Dick Johnson Penguin : Linux version 2.6.16.24 on an i686 machine (5592.62 BogoMips). New book: http://www.AbominableFirebug.com/ _  **************************************************************** The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them. Thank you. - 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/