| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <989B956029373F45A0B8AF0297081890D837CB@zch01exm26.fsl.freescale.net> Date: Tue, 3 Jul 2007 11:42:39 +0800 From: "Li Yang-r58472" <LeoLi@...escale.com> To: "Joakim Tjernlund" <joakim.tjernlund@...nsmode.se>, "linuxppc-dev Development" <linuxppc-dev@...abs.org>, "Netdev" <netdev@...r.kernel.org>, "Fleming Andy-afleming" <afleming@...escale.com> Subject: RE: [PATCH] ucc_geth.c, make PHY device optional. > -----Original Message----- > From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org] On > Behalf Of Joakim Tjernlund > Sent: Tuesday, July 03, 2007 8:52 AM > To: 'linuxppc-dev Development'; 'Netdev'; Li Yang-r58472 > Subject: [PATCH] ucc_geth.c, make PHY device optional. > > > This patch makes the PHY optional for ucc_geth.c ethernet driver. > > This is useful to support a direct mii to mii connection to, for example, > > a onboard swicth. > > > > Signed-off-by: Joakim Tjernlund <joakim.tjernlund@...nsmode.se> > ---- Hi Joakim, I'm wondering if we really need to have the option to disable phylib. Actually we have made phylib selected by default for ucc_geth. Many L2 switch chips have the capacity to be controlled. Therefore they can be managed as a phy device. For the MII interface which is not configurable, shouldn't we use the fixed phy support from Vitaly? - Leo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists