mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Angelo Archie Amoruso <aamoruso@libero.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3c59x.c Linux driver patch
Date: Thu, 30 May 2002 14:30:15 -0700	[thread overview]
Message-ID: <3CF699E7.1E1FE0E1@zip.com.au> (raw)
In-Reply-To: <20020530230306.7a2caa09.aamoruso@libero.it>

Angelo Archie Amoruso wrote:
> 
> ...
>         { 0x10B7, 0x9050, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CH_3C905_1 },
>         { 0x10B7, 0x9051, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CH_3C905_2 },
>         { 0x10B7, 0x9055, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CH_3C905B_1 },
> +        { 0x00B7, 0x9055, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CH_3C905B_1 },
> 

erm..  0x10B7 is 3Com.  I suspect you've dropped a bit in the
device's EEPROM and it's loading the wrong manufacturer ID
into the PCI config registers.

Grab vortex-diag from http://www.scyld.com/diag/index.html and
run `vortex-diag -aaee'.  Look at the EEPROM section.  I get:

EEPROM contents (64 words, offset 0x30):
 0x000: 2978 6056 0040 8060 0040 0000 0000 0080
 0x008: 0000 0000 0000 0000 0000 0000 0000 0000
 0x010: 0000 0000 0000 0000 0000 0000 10b7 6356
 0x018: 0000 0000 0000 0000 0000 0000 0000 0a0a
 0x020: ff29 2829 0008 0000 0000 0000 0000 0000
 0x028: 0000 ff01 0000 0000 0000 0000 0000 0000
 0x030: 0000 8642 002e 6056 0061 0009 0000 6d50
 0x038: 2970 0009 0000 8642 002e 0010 0000 00aa

See the 10b7 at offset 0x016?  That's the manufacturer ID.

You _might_ be able to fix it with 3com's DOS-based setup
tool ftp://ftp.3com.com/pub/nic/3c90x/3c90xx2.exe or you
can just run with your patch and be happy ;)

-

  reply	other threads:[~2002-05-30 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 21:03 Angelo Archie Amoruso
2002-05-30 21:30 ` Andrew Morton [this message]
2002-05-30 22:41 ` Alan Cox

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=3CF699E7.1E1FE0E1@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=aamoruso@libero.it \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®