<Ansuel>
same but i bet it's just some problem with the ssdk trying to guess the starting phy
<Ansuel>
since i assume the phy driver are very close on getting upstream maybe we should consider implementing the new way directly
<robimarko>
Could be, its rather weird to me
jeff___m has joined #openwrt-devel
<Ansuel>
btw net-next is still not open right?
<robimarko>
It should be open as the merge window has passed
<Ansuel>
ehh will see tomorrow... would love to start the PHY package discussion very fast since I already know it will be controversial
<Ansuel>
(and quic guy now base evrything on my phy repo soo there is also that)
<robimarko>
There seems to be understanding of the netdev guys that this is kinda needed
<robimarko>
As more and more multi PHY devices are on the market
<Ansuel>
yes main problem is all the reset and clock handling...
<Ansuel>
quic idea is to put them in the phy package node... but that will make rob very angry IMHO
<robimarko>
Which is what I dont understand
<robimarko>
As they quite literaly belong to the whole package
<robimarko>
and not just individual PHY-s
<robimarko>
The only issue Rob has raised is the fact that MDIO bus requires an address but the package itself has none
jeff___m has quit [Ping timeout: 480 seconds]
<Ansuel>
if Rob likes the ranges way to define regs then the package will have one and will reflect just the first PHY package... each subnode will have the reg set to an offset to it... detaching effectively the PHY package from the mdio bus...
<robimarko>
Well, that is another possibility
<robimarko>
You could as well just put the package node outside of any bus definition
<robimarko>
And just reference the bus as the package property
<robimarko>
This is a rather big complication just for the sake of definitions
<robimarko>
Not to mention that most of the DSA and other switch nodes essentially have a fake MDIO adress just to pass validation
goliath has joined #openwrt-devel
<Ansuel>
they probably read PHY and pretend it must be something very dumb... saddly it's not like that anymore from when 2.5g has been introduced
<robimarko>
Take the MV88E6XXX for example, you can put whatever the reg property you want
<robimarko>
As it using the compatible to get the base address
<robimarko>
From which it can read the actual model
<robimarko>
Its quite literaly just to pass validation