On Wed, 24 Aug 2005 01:14:23 +0200
Francois Romieu <[EMAIL PROTECTED]> wrote:

> Both revisions share the same PCI device ID and vendor ID but revision 2
> of the device uses SysKonnect's chipset whereas revision 3 of the device
> uses Realtek's 8169 chipset.
> 
> Credit goes to Christiaan Lutzer <[EMAIL PROTECTED]> for reporting
> the issue and giving the actual value for the different revisions.
> 
> Signed-off-by: Francois Romieu <[EMAIL PROTECTED]>
> 
> diff -puN drivers/net/r8169.c~r8169-685 drivers/net/r8169.c
> --- a/drivers/net/r8169.c~r8169-685   2005-08-23 23:50:41.477688428 +0200
> +++ b/drivers/net/r8169.c     2005-08-23 23:50:41.505683901 +0200
> @@ -186,8 +186,8 @@ const static struct {
>  static struct pci_device_id rtl8169_pci_tbl[] = {
>       { PCI_DEVICE(PCI_VENDOR_ID_REALTEK,     0x8169), },
>       { PCI_DEVICE(PCI_VENDOR_ID_DLINK,       0x4300), },
> -     { PCI_DEVICE(PCI_VENDOR_ID_LINKSYS,     0x1032), },
>       { PCI_DEVICE(0x16ec,                    0x0116), },
> +     { PCI_VENDOR_ID_LINKSYS,                0x1032, PCI_ANY_ID, 0x0024, },
>       {0,},
>  };
>  
> diff -puN drivers/net/skge.c~r8169-685 drivers/net/skge.c
> --- a/drivers/net/skge.c~r8169-685    2005-08-23 23:56:55.672671977 +0200
> +++ b/drivers/net/skge.c      2005-08-24 00:47:03.130632071 +0200
> @@ -79,8 +79,8 @@ static const struct pci_device_id skge_i
>       { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x4320) },
>       { PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 0x5005) }, /* Belkin */
>       { PCI_DEVICE(PCI_VENDOR_ID_CNET, PCI_DEVICE_ID_CNET_GIGACARD) },
> -     { PCI_DEVICE(PCI_VENDOR_ID_LINKSYS, PCI_DEVICE_ID_LINKSYS_EG1032) },
>       { PCI_DEVICE(PCI_VENDOR_ID_LINKSYS, PCI_DEVICE_ID_LINKSYS_EG1064) },
> +     { PCI_VENDOR_ID_LINKSYS, 0x1032, PCI_ANY_ID, 0x0015, },
>       { 0 }
>  };
>  MODULE_DEVICE_TABLE(pci, skge_id_table);

You probably want to fix sk98lin as well. And you can keep
PCI_DEVICE_ID_LINKSYS_EG1032 since it is same as 0x1032
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to