From owner-freebsd-current Sat May 8 9:37: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3C08B14DDA for ; Sat, 8 May 1999 09:37:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA22233; Sat, 8 May 1999 09:37:28 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Matthew Thyer Cc: current@FreeBSD.ORG Subject: Re: Doesn't anyone care about the broken sio ?? In-reply-to: Your message of "Sat, 08 May 1999 23:18:04 +0930." <37344094.620D8ACF@camtech.com.au> Date: Sat, 08 May 1999 09:37:28 -0700 Message-ID: <22229.926181448@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I mailed a simple way to reproduce the serious brokeness of the > serial port driver on my system and no one responds. > > What does this mean ? It means that nobody is probably willing to go bring up a MAME environment just to test this. You need to isolate it to a more minimal test case if you want people to jump on what could be a local problem (some serial hardware is better behaved than others) or a misbehaving X server (which is masking interrupts for too long; see mailing list archives on this topic). The more complex your reproduction case, in other words, the less likely it is that anyone will respond to it. If you can say "here's a small stand-alone C program which hogs things to the extent that the serial driver seriously overruns its buffers" then it's likely that someone will be at least motivated to compile, run and try it. If it involves running some esoteric application which requires downloading data of questionable legality on top of it, it's far less likely that anyone will even bother to look. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message