Bruce said, in his own quite way, that somebody had broken fast interrupts as part of newbus, and that is the end of that story.
Poul-Henning In message <22229.926181...@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> 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 majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
