netdev - Re: IXP4xx networking and phylib

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

Message-ID: <m3wsd0a0k3.fsf@maximus.localdomain>
Date:	Mon, 12 Jan 2009 18:36:44 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Hendrik Sattler <post@...drik-sattler.de>
Cc:	netdev@...r.kernel.org
Subject: Re: IXP4xx networking and phylib

Hi,

Added CC: netdev.

Hendrik Sattler <post@...drik-sattler.de> writes:

> My IXP465 MII port is connected to a Marvell switch (port 5). This port 
> is "always on" and has no PHY registers. It is configured in hardware. The 
> switch ports 1-4 have phy registers but that's not the matter.
> The problem is that there is no standard way in the platform info to tell the 
> driver (now phylib) that there are _no_ PHY registers.
>
> Is there a standard way to say: enable the ethernet interface and be done with 
> it?
> I currently do this by patching the driver. The PHYLIB patch makes that even 
> easier but it would be better to not need patching at all (at least one 
> driver less to patch).
>
> Maybe something like:
>   if (phyid < 0)
>      /* only enable the interface but there are no PHY registers */
-- 
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