netdev - Re: [PATCH RFC] ixp4xx_eth: Allow setting the MDIO bus name in platform data

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 21:34:38 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Simon Kågström <simon.kagstrom@...insight.net>
Cc:	"linux-arm-kernel\@lists.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Arnd Bergmann <arnd@...db.de>, <arm@...nel.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	<davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH RFC] ixp4xx_eth: Allow setting the MDIO bus name in platform data

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".
-- 
Krzysztof Halasa
--
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