Date: Wed, 11 Jul 2012 23:51:05 -0400 From: Arnaud Lacombe <lacombar@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-current@freebsd.org, Warner Losh <imp@bsdimp.com> Subject: Re: newbus' ivar's limitation.. Message-ID: <CACqU3MXZpR=6PZk5MQr5K3H%2BteipONEJSp%2BfcqTSxFrTYxdGLA@mail.gmail.com> In-Reply-To: <201207091127.30289.jhb@freebsd.org> References: <CACqU3MVh6shncm2Vtqj9oe_HxowWscCZ1eJf0q2F%2B=t_xKKBfQ@mail.gmail.com> <CACqU3MWpBNYgMJ-9Cm5_5udLZynraWCP_TTAaBdV4py1xqt%2BXQ@mail.gmail.com> <08E43D4E-EBB0-4469-9FC0-4E05C1D68DE4@bsdimp.com> <201207091127.30289.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MXZpR=6PZk5MQr5K3H%2BteipONEJSp%2BfcqTSxFrTYxdGLA>