mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrzej Orchowski" <A.Orchowski@softpress.com.pl>
To: <linux-kernel@vger.kernel.org>
Subject: 3c509 driver bug
Date: Fri, 30 Mar 2001 10:39:24 +0200	[thread overview]
Message-ID: <004a01c0b8f4$ec6755a0$0ad1a8c0@softpress.com.pl> (raw)

Hi,
sorry for this non-proffesional way of sending bug report and patch 
(I'm new to Linux, couldn't find utility to create patch). Fix is based
upon of the code analysis rather (and obviosly my working environment)
then 3Com tech docs. Anyway lets start...

1. Bug Summary
Inproper interface setting in 3Com 509 nic driver 1.16 (2.2)

2. Bug Description
Bug exists in 3Com 509 nic driver version 1.16 (2.2) by Donald J. Becker.
Under some circomstances the nic interface (10BaseT, AUI, BNC) is set
inproperly usually causing the card to stop working.
The unwanted and/or strange behaviour occures esspecially with more then
one 509 nics present.

Internally the code sets the interface type in if_port variable. It is set
upon of eeprom value in several places depending on the nic type:
PnP, ISA, EISA. After if_port assigment code flows to found: label
in which the different parameters are gathered together (to dev variable)
to set the nic.
Unfortunatelly in that place if_port is used condidionally which I believe
is inherited from previous driver versions.

/* Fix is simple enough not to include any attachments. Here it is */
The line (around #451)
    dev->if_port = (dev->mem_start & 0x1f) ? dev->mem_start & 3: if_port;
should be replaced simply with
    dev->if_port = if_port;

3. Keywords
networking, kernel, 3Com, 3C509, modules, drivers

4. Kernel version
I checked buggy driver is distributed with kernel version 2.2 and 2.4.2
(and probably all earlier kernel versions dated after Feb 1998).

Cheers
Andrzej Orchowski
andor@softpress.com.pl
> 


                 reply	other threads:[~2001-03-30  8:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004a01c0b8f4$ec6755a0$0ad1a8c0@softpress.com.pl' \
    --to=a.orchowski@softpress.com.pl \
    --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®