> I will do a cleanup and remove debugging. Is there interest in a
> patch? Can't say I understand what the IO instructions do.
>
> Stefan
i'm sure there is.
- erik
Just got this sucker working. I added a bit of initialization magic
from the gPXE VIA Rhine II driver. See "D-Link provided reset code":
http://git.etherboot.org/?p=gpxe.git;a=blob;f=src/drivers/net/via-rhine.c;h=81350091b7d1c6ddc4e3330615833916264ce9ef;hb=HEAD
(This card's revision ID is 0x78.)
On 19/04/2008, Stefan Hajnoczi <[EMAIL PROTECTED]> wrote:
> I initialised the mii struct to use phy 1, as mii() would have if it
> had succeeded. Unfortunately running ip/ipconfig simply sat there,
> running it with the debug flag showed recv timeouts. I could not see
> any packets on the netw
I initialised the mii struct to use phy 1, as mii() would have if it
had succeeded. Unfortunately running ip/ipconfig simply sat there,
running it with the debug flag showed recv timeouts. I could not see
any packets on the network.
Stefan
On Sat, Apr 19, 2008 at 3:10 PM, erik quanstrom <[EMAIL
i don't have this part (that i know of) and the datasheet didn't
immediately pop up, but the linux driver hardcodes the phy_id to 1.
the part you have claims to have an integrated phy.
you may wish to try that.
- erik
p.s. lspci -n will give you vid/did numbers.
> Hi,
> I just installed Plan 9
Hi,
I just installed Plan 9 on a machine using a VIA Rhine II NIC.
Unfortunately the driver is not successfully initializing the device.
Placing print statements in ethervt6102.c shows that vt6102reset() is
failing when mii() returns an empty PHY mask. The mii() function is
probing each PHY from
