netdev - Re: [PATCH v1] net: phy: micrel: add KSZ8795 ethernet switch

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5f3fa323-bf36-5fcd-248f-a3b9ad70ea6d@prevas.dk>
Date:   Fri, 27 Jan 2017 08:42:39 +0100
From:   Sean Nyekjær <sean.nyekjaer@...vas.dk>
To:     Andrew Lunn <andrew@...n.ch>
CC:     <netdev@...r.kernel.org>
Subject: Re: [PATCH v1] net: phy: micrel: add KSZ8795 ethernet switch



On 2017-01-26 19:12, Andrew Lunn wrote:
>> I remove the word "Switch" from the commit message and phy name.
>> The rest is okay?
> Yes.
>
>> What is generally being done when to phy's have the same id, micrel
>> have done this many times...
> It should not be a problem. When you write a switch driver for the
> switch, it will be in device tree. Look at the Marvell Switches as an
> example. Switches don't probe based on the ID in registers 2 and 3,
> because switches often respond to many different addresses, or don't
> have an ID in register 2 and 3.
>
> So it should not matter if the switch and the PHYs embedded in the
> switch have the same ID.
>
> When do you plan to post your switch driver?
>
>         Andrew
I was not planning on doing that, the managed part of the switch is not 
needed in the project i'm working on.
Maybe i will do it when i have some spare time, it could be fun :-)

/Sean