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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 24 Mar 2014 13:42:29 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	Simon Kågström 
	<simon.kagstrom@...insight.net>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Arnd Bergmann <arnd@...db.de>, netdev <netdev@...r.kernel.org>,
	"arm@...nel.org" <arm@...nel.org>,
	David Miller <davem@...emloft.net>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RFC] ixp4xx_eth: Allow setting the MDIO bus name in
 platform data

2014-03-24 13:34 GMT-07:00 Krzysztof Halasa <khc@...waw.pl>:
> Simon Kågström <simon.kagstrom@...insight.net> writes:
>
>> Allows using e.g., a fixed MDIO bus with the ixp4xx_eth driver.
>> Example:
>>
>>   static struct eth_plat_info board_plat_eth_internal[] = {
>>       {
>>               .mdio_bus_id    = "fixed-0",
>>               .phy            = 31,
>>               .rxq            = 4,
>>               .txreadyq       = 21,
>>               .hwaddr         = {0x02, 0x00, 0x00, 0x00, 0x00, 0x00},
>>       }
>>   };
>
> Why do we need it? I'm not sure I know what constitutes a "fixed MDIO
> bus".

This is a software emulation MDIO bus for when your Ethernet MAC is
connected to a PHY which does not appear on the MDIO bus. This is
typically used to provide the Ethernet driver with a link that is
always seen as UP, when you cannot directly query it via MDIO/MDC.
-- 
Florian
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ