public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: James Henderson <JamesHenderson@ruggedcom.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "bugme-daemon@bugzilla.kernel.org"
	<bugme-daemon@bugzilla.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 38862] New: No support for DGE-530T Rev C1
Date: Wed, 6 Jul 2011 17:48:44 -0400	[thread overview]
Message-ID: <4E14D83C.1090506@ruggedcom.com> (raw)
In-Reply-To: <20110706143709.0f5ab7d6.akpm@linux-foundation.org>

Andrew Morton wrote:
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Wed, 6 Jul 2011 16:05:36 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>   
>> https://bugzilla.kernel.org/show_bug.cgi?id=38862
>>
>>            Summary: No support for DGE-530T Rev C1
>>            Product: Drivers
>>            Version: 2.5
>>     Kernel Version: 2.6.39.2
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: Network
>>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>>         ReportedBy: jameshenderson@ruggedcom.com
>>         Regression: No
>>
>>
>> The kernel support DGE-530T REV B2 through the skge driver.  The PCI device id
>> of REV-B2 is 1186:4302.  Rev C1 has a PCI device id of 1186:4302.  No driver in
>> the current kernel supports this device id/vendor combination.  Furthermore,
>> this device is not even listed in the device database ->
>> http://www.pcidatabase.com/vendor_details.php?id=921 .
>>
>> On the chip is the following information:
>> D-Link
>> DLG10028C
>> A8A34A1
>> GA50 TAIWAN
>>
>> A sticker on the card reads:
>> DGE-530T Rev C1
>>
>> I am including a picture I took of the card.
>>
>>     
>
> Did you test simply adding that device to the driver?
>
> --- a/drivers/net/skge.c~a
> +++ a/drivers/net/skge.c
> @@ -89,6 +89,7 @@ static DEFINE_PCI_DEVICE_TABLE(skge_id_t
>  	{ PCI_DEVICE(PCI_VENDOR_ID_SYSKONNECT, PCI_DEVICE_ID_SYSKONNECT_YU) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, PCI_DEVICE_ID_DLINK_DGE510T) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, 0x4b01) },	/* DGE-530T */
> +	{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, 0x4302) },	/* DGE-530T Rev C1 */
>  	{ 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) },
> _
>
>   
No I haven't tested that change - I don't have a kernel development 
environment setup and unfortunately I don't have any more work time to 
budget to the issue beyond reporting it.

Also, I meant to say that Rev B2 has PCI id 1186:4B01 (although you seem 
to have figured that out).

Thanks,

James

  reply	other threads:[~2011-07-06 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38862-10286@https.bugzilla.kernel.org/>
2011-07-06 21:37 ` [Bugme-new] [Bug 38862] New: No support for DGE-530T Rev C1 Andrew Morton
2011-07-06 21:48   ` James Henderson [this message]
2011-07-06 21:54     ` Andrew Morton
2011-07-06 22:07     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E14D83C.1090506@ruggedcom.com \
    --to=jameshenderson@ruggedcom.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox