From owner-freebsd-current@FreeBSD.ORG  Thu Jul 12 03:51:07 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8EC3D106566C;
	Thu, 12 Jul 2012 03:51:07 +0000 (UTC)
	(envelope-from lacombar@gmail.com)
Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com
	[209.85.217.182])
	by mx1.freebsd.org (Postfix) with ESMTP id 978B88FC0C;
	Thu, 12 Jul 2012 03:51:06 +0000 (UTC)
Received: by lbon10 with SMTP id n10so3310776lbo.13
	for <multiple recipients>; Wed, 11 Jul 2012 20:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=Ld4EQ0vVtcIYE4PJWTr+vZeGtinJ1zcOqM1qyRqgms8=;
	b=QUChQv8D1lKm9y/Si+SacNnAMbw2Fnbfjgr8B54Esm69Ks2bBE9sOgKTU7lel2WWB0
	Lu+6J2kC1K9qkTCpMN6GcX16m71AXqOTedkyZy/8un4madZIl1dRV+/xzvJIsnGpCGUQ
	fvflu2O/rxQh3d05pPRwwLMPchgGi8JnavnuwhQa6ZUwlvAJB/chcu22hbJK0nCz0HGk
	ZIhS4HDvOB/h6tb4IM0M+HZIFoysK+JdvZz9Yh21xUrFk5xLueDbgFbYWiDplaLCj9tm
	IsbdxCSxRN76tU1b1+gTwQav6uexxyHS3pR/XMOew+OpoIWNPmwj9/3F4nvA14APAXv2
	bJYA==
MIME-Version: 1.0
Received: by 10.152.105.173 with SMTP id gn13mr51660627lab.20.1342065065417;
	Wed, 11 Jul 2012 20:51:05 -0700 (PDT)
Received: by 10.114.13.68 with HTTP; Wed, 11 Jul 2012 20:51:05 -0700 (PDT)
In-Reply-To: <201207091127.30289.jhb@freebsd.org>
References: <CACqU3MVh6shncm2Vtqj9oe_HxowWscCZ1eJf0q2F+=t_xKKBfQ@mail.gmail.com>
	<CACqU3MWpBNYgMJ-9Cm5_5udLZynraWCP_TTAaBdV4py1xqt+XQ@mail.gmail.com>
	<08E43D4E-EBB0-4469-9FC0-4E05C1D68DE4@bsdimp.com>
	<201207091127.30289.jhb@freebsd.org>
Date: Wed, 11 Jul 2012 23:51:05 -0400
Message-ID: <CACqU3MXZpR=6PZk5MQr5K3H+teipONEJSp+fcqTSxFrTYxdGLA@mail.gmail.com>
From: Arnaud Lacombe <lacombar@gmail.com>
To: John Baldwin <jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-current@freebsd.org,
	Warner Losh <imp@bsdimp.com>
Subject: Re: newbus' ivar's limitation..
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Thu, 12 Jul 2012 03:51:07 -0000

Hi,

On Mon, Jul 9, 2012 at 11:27 AM, John Baldwin <jhb@freebsd.org> wrote:
> Also, I think we should do this in general.  We already have one example (e.g.
> ACPI IVARs start at 100 so that things like the ACPI PCI bus driver can
> provide both ACPI and PCI IVARs to child devices).  I think we should assign
> each bus it's own IVAR range.  It would make it easier to determine if a
> specific IVAR is event supported.  Certainly I think ISA and PCI at a minimum
> should be changed to start at, say, 200 and 300.
>
What's the point doing that ? Let's just resign to the conclusion that
FreeBSD devices' subsystem provides no dynamic way for a client device
to deals with multiple bus driver. Instead all possible combination
have to be harcoded and hand-crafted, when at all possible, to look
like they're coming from a single bus...

But again, newbus is 14 years old...

 - Arnaud