Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 May 1998 22:40:02 -0700 (PDT)
From:      Matthew Dillon <dillon@backplane.com>
To:        freebsd-bugs@FreeBSD.ORG
Subject:   Re: i386/5398 
Message-ID:  <199805030540.WAA22835@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/5398; it has been noted by GNATS.

From: Matthew Dillon <dillon@backplane.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: John-Mark Gurney <gurney_j@efn.org>, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/5398 
Date: Sat, 2 May 1998 22:34:59 -0700 (PDT)

     Look guys, I'm not going to argue... I have worse things to worry about
     then a bug report relating to a digital camera interface.  But I am
     extremely disappointed that you are taking such a cavalier attitude
     towards it and making assumptions that, in my view, make little or no 
     sense just to close out the report.  I'm not an idiot... I've been 
     writing operating systems and doing digital hardware design for over 
     15 years, so don't fraggin quote databooks at me and expect to get
     away with it.
 
     There's only one way to solve this problem and, unfortunately, I don't
     have time to do it... and that is to add debugging code to the kernel
     to do a histogram of the PC of the pushed context at the beginning of the
     core interrupt code to see which diasble/enable pair is causing the
     greatest number of latency problems.  But, as I said, I don't have the
     time to do it myself.
 
     At the very least, don't close bug reports that I spent hours
     putting together on an 'assumption'.  It's annoying and insulting. 
     It is also annoying and insulting to start quoting missing hardware
     configurations at me... you know damn well that if every bug report 
     had the hardware configuration detail down to the last transistor they
     would be mostly useless bug reports because the FreeBSD crew would be
     spending more time trying to sift through the garbage to locate the
     meat.  This bug report was pretty straight forward.  The PCI bus may not
     be the quickest thing in the world, but 8 microseconds times 8 character
     slots is still a hellofalong time to start blaming it for interrupt 
     latencies that cause a serial FIFO to overflow.
 
 						-Matt
 
 :Poul-Henning Kamp             FreeBSD coreteam member
 :phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
 :"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
 :
 
     Matthew Dillon   Engineering, BEST Internet Communications, Inc.
 		     <dillon@backplane.com>
     [always include a portion of the original email in any response!]

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805030540.WAA22835>