linux-kernel - Re: sky2 eth device with Gigabyte 965P-S3 motherboard

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 22 Sep 2006 09:38:47 -0400
From:	"Tom St Denis" <tomstdenis@...il.com>
To:	"Daniel Drake" <dsd@...too.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: sky2 eth device with Gigabyte 965P-S3 motherboard

On 9/22/06, Tom St Denis <tomstdenis@...il.com> wrote:
> This won't be fixed as part of 2.6.18.x?  Looking at the source for
> the latest gentoo-sources in the 2.6.17 stream I don't see ID 4364 in
> the source for sky2.c [sky2_id_table[]].  So why is it detected and
> working there but not in 2.6.18?
>
> I'll try adding the device to the table and see what happens.

Adding the line to the table works now.  [yipee, I get proper SATA and
net now woot!]

May I request that someone insert that one line to drivers/net/sky2.c
before 2.6.19?

--- sky2.old	2006-09-22 21:34:36.000000000 +0000
+++ sky2.c	2006-09-22 21:28:03.000000000 +0000
@@ -121,6 +121,7 @@
 	{ PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4361) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4362) },
 	{ PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4363) },
+	{ PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4364) },
 	{ 0 }
 };

[yeah I know not a normal patch ... I'm also not a kernel developer...]

I'm still confused on how it works in 2.6.17 without the ID?

Thanks,
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/