Date: Tue, 13 Dec 2011 18:19:03 +0100 From: Stefan Bethke <stb@lassitu.de> To: Warner Losh <imp@bsdimp.com> Cc: Adrian Chadd <adrian@FreeBSD.org>, freebsd-embedded@FreeBSD.org Subject: Re: TL-WR1043: switch Message-ID: <725DC34F-2A68-43E2-BE05-3AC76D07F8B5@lassitu.de> In-Reply-To: <96F0A4F9-671B-422C-B8F2-6F386B1B3672@bsdimp.com> References: <68ABED76-CB1F-405A-8036-EC254F7511FA@lassitu.de> <3B3DB17D-BF87-40EE-B1C1-445F178E8844@lassitu.de> <86030CEE-6839-4B96-ACDC-2BA9AC1E4AE4@lassitu.de> <2D625CC9-A0E3-47AA-A504-CE8FB2F90245@lassitu.de> <203BF1C8-D528-40C9-8611-9C7AC7E43BAB@lassitu.de> <3C0E9CA3-E130-4E9A-ABCC-1782E28999D1@lassitu.de> <CAJ-VmomWsGy9wMb0zA-WjTRP6Qh%2BO2u_Pe-rgkerFFpi04iKnw@mail.gmail.com> <6387ABA5-AC55-49DD-9058-E45CC0A3E0A0@lassitu.de> <CAJ-VmonM91s-kbbEqVDy9PvtH-gxLWYmusGiqzqCWMtfMdoo2A@mail.gmail.com> <EA0807C1-6FEE-4743-8DCA-1AC873664005@lassitu.de> <74E4AF57-3D22-415E-B913-176753B09B16@lassitu.de> <710E2C7A-E9AC-4103-8C61-0EDC4A3AF9DE@lassitu.de> <C2885254-F02C-401B-B56D-39F62933F3CC@lassitu.de> <24FB4633-B729-4582-9FF6-CA8656742985@lassitu.de> <CAJ-VmokdvgPC5gXy9n6KFxYwvLLZCtVL%2B_Y-JN5VuH=8CCroVQ@mail.gmail.com> <55D569DB-875B-412B-8650-C56F85D8E327@lassitu.de> <96F0A4F9-671B-422C-B8F2-6F386B1B3672@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 13.12.2011 um 16:41 schrieb Warner Losh: >> I'm using sbin/ifconfig/if_media.c unchanged except for exporting = some of the low level functions for printing and parsing media and = mediaopt. I'm not certain where this code would go to be shared = efficiently. Also, wherever it goes ifconfig still needs to be = buildable for /rescue. >=20 > Unless the code is huge, I'd like to see it in ifconfig as well from a = usability standpoint. Why require yet another application to do this? = We put all the wireless stuff into ifconfig. >=20 > If the infrastructure really is getting in the way, I'd like to look = at ways to make ifconfig more flexible and less in the way. I'm fine with rolling all this into ifconfig, but please note that the = switch configuration has very little to do with the systems ethernet = interfaces. It just so happens that usually one of the systems ethernet = interfaces is also connected to the switch. The PHYs connected to the = switch are completely separate from any interface ifconfig manages*. I = just wanted to simplify my own work by trying to use the existing miibus = code. The commands and the output from my prototype configuration utility are = intentionally similar to ifconfig, but the ioctls go through a separate = cdev, not through the socket ioctl. I believe it would be = counterintuitive to try and fit the switch configuration through the = interface configuration interface, as there is very little overlap = beyond the PHY stuff. If we want to integrate the switch configuration into ifconfig, the = first question from a usability perspective would be how to identify the = switch and it's various configurable entities (ports, vlans, queues, = etc.), since that namespace would be distinct from the ifnet namespace. Stefan * On some switch chip models, one of the built-in PHYs is exposed = through a separate MII, and can be used as any discrete PHY would be = used. But that has little to do with the switch itself. --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?725DC34F-2A68-43E2-BE05-3AC76D07F8B5>