From oberman@es.net  Tue Feb 25 09:20:17 2003
Return-Path: <oberman@es.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 01A2937B401; Tue, 25 Feb 2003 09:20:17 -0800 (PST)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A335143F3F; Tue, 25 Feb 2003 09:20:15 -0800 (PST)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP id MUA74016;
        Tue, 25 Feb 2003 09:20:14 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id 67F7D5D06; Tue, 25 Feb 2003 09:20:14 -0800 (PST)
Message-Id: <20030225172014.67F7D5D06@ptavv.es.net>
Date: Tue, 25 Feb 2003 09:20:14 -0800
From: "Kevin Oberman" <oberman@es.net>
To: "Bruce A. Mah" <bmah@freebsd.org>
Cc: bde@freebsd.org, freebsd-gnats-submit@freebsd.org
In-Reply-To: Your message of "Tue, 25 Feb 2003 09:05:11 PST."
             <20030225170511.GA53886@intruder.bmah.org> 
Subject: Re: PR bin/33963 

>Number:         48677
>Category:       bin
>Synopsis:       Re: PR bin/33963
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 25 09:30:06 PST 2003
>Closed-Date:    Fri Feb 28 16:32:24 PST 2003
>Last-Modified:  Fri Feb 28 16:32:24 PST 2003
>Originator:     oberman@es.net
>Release:        
>Organization:
>Environment:
>Description:
 > Date: Tue, 25 Feb 2003 09:05:11 -0800
 > From: "Bruce A. Mah" <bmah@freebsd.org>
 > 
 > I'm trying to figure out what to do with this PR, which has been
 > languishing for awhile and gives me momentary angst every week when it
 > shows up in my PR reminders list.
 > 
 > Some discussion with bde (shortly after the last PR followup) has made
 > me realize that the root cause of these misleading sio(4) probe
 > messages wasn't what I thought it was, and that I don't have the
 > qualification or time ot deal with this.
 > 
 > The alternatives seem to be:
 > 
 > 1.  Toss the PR back to freebsd-bugs.
 > 
 > 2.  Give it to bde, who's the de facto sio(4) maintainer.
 > 
 > 3.  Close it.
 
 imp vetoed the first section of the patch and I agree with his point
 in doing so. But I think the second half (8250 or not responding) is a
 legitimate bug fix as the driver currently implies that it actually
 could tell the device is an 8250 when the message is really only an
 indication that the driver did not receive a response to its query. It
 assumes that this means an 8250 as any flavor of 16550 or any decent
 clone will respond in some way.
 
 I can re-submit with only the single line change, but if bde "owns"
 the sio driver these days, I'll leave it up to him. 
 
 R. Kevin Oberman, Network Engineer
 Energy Sciences Network (ESnet)
 Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
 E-mail: oberman@es.net			Phone: +1 510 486-8634
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ceri 
State-Changed-When: Fri Feb 28 16:31:52 PST 2003 
State-Changed-Why:  

Misfiled followup to bin/33963 [content migrated]. 


Responsible-Changed-From-To: gnats-admin->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Fri Feb 28 16:31:52 PST 2003 
Responsible-Changed-Why:  

Take from gnats-admin. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48677 
>Unformatted:
