mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Guido Guenther <agx@sigxcpu.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jonmason@us.ibm.com
Subject: Re: pcnet32: 79c976 with fiber optic
Date: Thu, 25 Nov 2004 22:03:36 +0000	[thread overview]
Message-ID: <1101420214.18354.69.camel@localhost.localdomain> (raw)
In-Reply-To: <20041124171427.GA29693@bogon.ms20.nix>

On Mer, 2004-11-24 at 17:14, Guido Guenther wrote:
> it works fine. Any idea what exactly causes the problem?

I've no idea whether the workaround is simply not supposed to be used on
fibre devices (I'm suprised the driver works on fibre full stop 8)). Its
certainly possible to do a cleaner change though even if nobody can work
out why.

Use lspci -v to find the subvendor/subdevice ID for the particular board
assembly and then skip the fixup for that device alone. That should let
you produce a diff that is safely mergable


  reply	other threads:[~2004-11-26 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 17:14 Guido Guenther
2004-11-25 22:03 ` Alan Cox [this message]
2004-11-26  9:21   ` Guido Guenther

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=1101420214.18354.69.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=agx@sigxcpu.org \
    --cc=jonmason@us.ibm.com \
    --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®