From owner-freebsd-current@FreeBSD.ORG  Tue Apr 13 12:37:25 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EF54616A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 13 Apr 2004 12:37:25 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8859243D46
	for <freebsd-current@freebsd.org>;
	Tue, 13 Apr 2004 12:37:25 -0700 (PDT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i3DJbOkj010340;
	Tue, 13 Apr 2004 13:37:24 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 13 Apr 2004 13:38:12 -0600 (MDT)
Message-Id: <20040413.133812.104032376.imp@bsdimp.com>
To: nate@root.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040413115930.G76691@root.org>
References: <20040413184952.38408.qmail@web11410.mail.yahoo.com>
	<20040413115930.G76691@root.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: 3Com 3c905 failed to attach
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Apr 2004 19:37:26 -0000

In message: <20040413115930.G76691@root.org>
            Nate Lawson <nate@root.org> writes:
: I think Warner has to go through broken devices like this and fix their
: resource allocation.  His ATA patch (just committed today by sos@) is
: probably an example of this.

Actually, I'm not sure that the resource allocation is broken on xl,
per se, but rather we fail to detect that we should use I/O ports
properly.  I'm looking to see if I can find documentation on these
parts so that I might find a better way.  The old way relied on the
fact that we try memory, and that it will always fail.  Now that we do
lazy resource allocation, this is violates the assumptions made by the
xl driver.  A quick survey of other drivers shows that this shouldn't
be a wide-spread problem.

Warner