netdev - bus id in PHY Abstraction Layer

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>] [day] [month] [year] [list]

Message-ID: <20070509084556.GA5967@localhost.localdomain>
Date:	Wed, 9 May 2007 10:45:56 +0200
From:	Sascha Hauer <s.hauer@...gutronix.de>
To:	netdev@...r.kernel.org
Cc:	afleming@...escale.com
Subject: bus id in PHY Abstraction Layer

Hi,

I made a quick shot to port the at91 network driver to the phy
abstraction layer. While doing so I stumbled upon the
(struct mii_bus)->id field. Currently the network driver registering the
bus has to set this field. au1000_eth.c for example uses 0 or 1. mii-fec.c
uses the id field of the corresponding platform device, which will start
from 0, too. So if a second ethernet driver comes around the id fields
will clash. I think the PAL has to assign the id field instead of the
network driver. Maybe a id convention like "mii_fec.x:yy" where x is a
running number and yy is the phy address would do it. Any opinions about
that?

Sascha

-- 
Pengutronix - Linux Solutions for Science and Industry
Entwicklungszentrum Nord     http://www.pengutronix.de
-
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