Date: Sun, 09 Apr 2006 18:51:47 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: darren.pilgrim@bitfreak.org Cc: hackers@freebsd.org, mwm@mired.org Subject: Re: Using any network interface whatsoever (solution?) Message-ID: <20060409.185147.25157954.imp@bsdimp.com> In-Reply-To: <44396D33.8070900@bitfreak.org> References: <4438A0A3.3050600@bitfreak.org> <17465.20321.174794.576853@bhuda.mired.org> <44396D33.8070900@bitfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <44396D33.8070900@bitfreak.org>
Darren Pilgrim <darren.pilgrim@bitfreak.org> writes:
: Mike Meyer wrote:
: > In <4438A0A3.3050600@bitfreak.org>, Darren Pilgrim <darren.pilgrim@bitfreak.org> typed:
: >> You could test two different drivers on the same hardware and you wouldn't
: >> have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run:
: >
: > Yup, and this is an advantage. On the other hand, if you tie the
: > device name to the slot number (the real goal), you can swap different
: > hardware into that slot without having to modify any configuration
: > information at all.
:
: It wouldn't be too difficult to extend the configuration to allow entries
: like this:
:
: Interface0_addr="MAC 01:23:45:67:89:ab"
: Interface1_addr="PCI 0:1:2" # pci0, device 1, function 2
: Interface2_addr="USB 0:1:2" # usb0, addr 1, port 2
:
: Add some bits to grok dmesg or pciconf/usbdevs or maybe even trigger from
: devd and there you go.
:
: I should mention that the second and third options could be broken by the
: addition or removal of a card with a PCI bridge or USB root hub on it.
The device subsystem already exports a bus-dependent plug and play
position. No need to make it specific to USB/PCI/whatever.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060409.185147.25157954.imp>