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:	Wed, 4 Feb 2009 17:15:43 -0600
From:	Andy Fleming <afleming@...il.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	Hendrik Sattler <post@...drik-sattler.de>, netdev@...r.kernel.org
Subject: Re: IXP4xx networking and phylib

On Mon, Jan 12, 2009 at 11:36 AM, Krzysztof Halasa <khc@...waw.pl> wrote:
> 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).

There is a "fixed-phy" driver.  It allows you to configure things such
that phylib will treat a PHY at a given address like it is a PHY with
whatever attributes you choose.  The other option is to look at the
DSA code from Lennert, and make the Marvell switch work with that (I
haven't looked closely enough to see if that's feasible, but the end
goal should be that all such integrated switches are covered by some
framework).

Andy
--
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