Here's a small patch to add the PCI ID and chip type of the chip in my
Toshiba laptop to the skge driver. I haven't tested it much (just
insmoded it and run ethtool against the corresponding eth1 device), but
it doesn't crash my system, so unless this configuration has already
been tested and is known to have problems, it might be good to add this
patch.
I'll test some more with a real network when I get home.
Thanks,
Jesse
Signed-off-by: Jesse Barnes <[email protected]>
Hi Jesse,
Jesse Barnes wrote:
> Here's a small patch to add the PCI ID and chip type of the chip in my
> Toshiba laptop to the skge driver. I haven't tested it much (just
> insmoded it and run ethtool against the corresponding eth1 device), but
> it doesn't crash my system, so unless this configuration has already
> been tested and is known to have problems, it might be good to add this
> patch.
>
> I'll test some more with a real network when I get home.
The device ID you added (0x4351) is already claimed by the new sky2 driver.
Unless theres a mistake in sky2's device table, your laptop contains a
Yukon-II adapter which is incompatible with the original Yukon chips (skge =
Yukon, sky2 = Yukon-II).
On the other hand, I believe Stephen could do with some extra sky2 testing :)
You can find it in the latest -mm releases.
Daniel
On Wednesday, October 19, 2005 12:43 pm, Daniel Drake wrote:
> The device ID you added (0x4351) is already claimed by the new sky2
> driver.
>
> Unless theres a mistake in sky2's device table, your laptop contains a
> Yukon-II adapter which is incompatible with the original Yukon chips
> (skge = Yukon, sky2 = Yukon-II).
>
> On the other hand, I believe Stephen could do with some extra sky2
> testing :) You can find it in the latest -mm releases.
Oh cool, I'll try that driver instead. Thanks.
Jesse
On Wed, 19 Oct 2005, Daniel Drake wrote:
> Hi Jesse,
>
> Jesse Barnes wrote:
>> Here's a small patch to add the PCI ID and chip type of the chip in my
>> Toshiba laptop to the skge driver. I haven't tested it much (just insmoded
>> it and run ethtool against the corresponding eth1 device), but it doesn't
>> crash my system, so unless this configuration has already been tested and
>> is known to have problems, it might be good to add this patch.
>>
>> I'll test some more with a real network when I get home.
>
> The device ID you added (0x4351) is already claimed by the new sky2 driver.
>
> Unless theres a mistake in sky2's device table, your laptop contains a
> Yukon-II adapter which is incompatible with the original Yukon chips (skge =
> Yukon, sky2 = Yukon-II).
>
> On the other hand, I believe Stephen could do with some extra sky2 testing :)
> You can find it in the latest -mm releases.
What is the name of sky2 driver? I can't to find it in:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/broken-out/
Wrong place?
Best regards,
Krzysztof Ol?dzki
Krzysztof Oledzki wrote:
> What is the name of sky2 driver? I can't to find it in:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/broken-out/
>
>
> Wrong place?
Its pulled in from the netdev tree.
Daniel