Re: D-Link DGE-350T and if_sk (no go)

On Thu, Dec 14, 2006 at 10:22:06AM +0100, Pascal Hofstee wrote:
 > On Wed, 2006-12-13 at 22:49 +0000, Bruce M. Simpson wrote:
 > > Yes. It looks like (from dmesg) that your card is a Yukon 1. I think I 
 > > managed to get the sk driver to attach to the PCI-e Yukon in my ASUS 
 > > machine and had similar problems, though this was many months ago. The 
 > > msk driver might work for you.
 > 
 > Well .. i got around to trying the msk driver this morning and
 > unfortunately (after adding the pci-id to the msk driver) the card
 > probes, but doesn't attach because of the msk-driver rejecting
 > device-id's that are't Yukon II chips. (the if-section below in
 > if_msk.c)
 > 
 > if (sc->msk_hw_id < CHIP_ID_YUKON_XL ||
 >     sc->msk_hw_id > CHIP_ID_YUKON_FE) {
 > 
 >         device_printf(dev, "unknown device: id=0x%02x, rev=0x%02x\n",
 >              sc->msk_hw_id, sc->msk_hw_rev);
 >         error = ENXIO;
 >         goto fail;
 > }
 > 
 > My DGE-530T however has id=0xb1, rev=0x09 which seems to be what if_msk
 > considers CHIP_ID_YUKON_LITE. So it looks that without further hacking
 > on the msk driver trying to use if_msk instead of if_sk is an excercise
 > in futility, though it was definitely worth a shot.
 > 

Please don't waste time. The msk(4) does not work for your DGE-530T.
Yukon and Yukon II is completly different in hardware. That is main
reason why I have to write msk(4) instead of adding Yukon II support
code to sk(4).

 > I'll be watching the interrupts as soon as i can get a hold of my
 > neighbour which should probably be sometime later today. If in the
 > meanwhile people have other suggestions i might try, send them my way
 > and i'll give it a shot :)
 > 

It could be related with PHY which is under power down/uninitialized
state. I'm still wonder why sk(4) doesn't work at all.

-- 
Regards,
Pyun YongHyeon