Date: Fri, 16 Dec 2011 08:56:19 +0100 From: Stefan Bethke <stb@lassitu.de> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-embedded@freebsd.org Subject: Re: TL-WR1043: switch Message-ID: <1BED9DE4-3DB7-4523-AB7D-39A7960A4BA9@lassitu.de> In-Reply-To: <CAJ-VmokBfJE4CDUdk=nRwdGM=ixjC3QxbsrJM%2BoYqGzdPK5kiQ@mail.gmail.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-VmokGYpwepUYa_a4vJViU_5JRh9PetQpvwhTiMqUNxZnzgA@mail.gmail.com> <CAJ-VmokBfJE4CDUdk=nRwdGM=ixjC3QxbsrJM%2BoYqGzdPK5kiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 16.12.2011 um 02:29 schrieb Adrian Chadd: > Hi! >=20 > So I have it working; I've not tried vlans yet (I'm still building an > updated world complete with your config tool) so I'll report when I've > tested that, but so far so good. Both ports work, the default vlan tag > works, port status seems to work. For those trying to play along at home: I've updated the patch so it = actually compiles correctly, both as modules as well as compiled into = the kernel. > Thanks very much for this! You're welcome! > So next is looking at ray@'s work in zrouter on the ar8216/ar8316 > switch PHYs. There's going to be some rather (un) fun stuff, including > figuring out what to do about gluing in ukphy/switchphy entries as > needed, shared MII bus, etc. Yup. > Question: the tplink 1043nd arge0 hints currently has a phymask of > 0x000c, with a nailed up media/duplex. This avoids attaching a ukphy > to the device. How should that now be handled? Instead of this phymask > thing, add a flag which says "don't use a phy, we're attaching another > way" so that code path doesn't run, but it doesn't try probing a PHY? > Or? For the TL-WR1043ND, no PHY should be attached to arge0, and the speed = etc. should be hardwired to 1000/fdx, since that's what the switch MAC = arge0 is connected to is wired to. We could add code to change arge0 and the switch configuration, but I = see little benefit in that. Stefan --=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?1BED9DE4-3DB7-4523-AB7D-39A7960A4BA9>