Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 5 Nov 2002 04:12:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 5 Nov 2002 04:12:32 -0500 Received: from modemcable074.85-202-24.mtl.mc.videotron.ca ([24.202.85.74]:11020 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Tue, 5 Nov 2002 04:12:31 -0500 Date: Tue, 5 Nov 2002 04:20:00 -0500 (EST) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: Russell King cc: Linux Kernel Subject: Re: 2.5.45 odd deref in serial_in In-Reply-To: <20021105090256.A17931@flint.arm.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1172 Lines: 32 On Tue, 5 Nov 2002, Russell King wrote: > a) have to rely on interrupts running Not really ;) If i'm successful i may get this working albeit only for specific boxes. Although we'd need an IDT at least, but interrupts may remain masked... > b) have to buffer the data somewhere, which may possibly fill up and > then what do we do with the printk message > > Bear in mind that dropping random printk messages because we've filled > a buffer isn't acceptable. Also note that the behaviour in this area > hasn't changed since 2.4 times. > > Obviously, the way to reduce the time spent writing console messages to > the serial port is to increase the baud rate. 8) I'm runnning 115200 :P It looks like a race however because i don't always trigger it, but when i do the trace is always the same. However i'm not going to make you run circles for my potentially dodgy code. Cheers, Zwane -- function.linuxpower.ca - 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/