Re: pcnet32 devices with incorrect trident vendor ID

Matthew Wilcox wrote:

It looks to me like there used to be a quirk that knew about this bug
and fixed it.

The reason I say this is that the lspci -x dumps are the same -- both
featuring the wrong vendor ID.

Good catch. I didn't notice this.

> Want to dig through 2.4 and look for

this quirk?

No time for this personally.

Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] Prevent trident driver from grabbing pcnet32 hardware
    • From: Jon Mason <[email protected]>
  • pcnet32 devices with incorrect trident vendor ID
    • From: Daniel Drake <[email protected]>
  • Re: pcnet32 devices with incorrect trident vendor ID
    • From: Matthew Wilcox <[email protected]>

• Prev by Date: Re: 2.6.15-mm2
• Next by Date: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
• Previous by thread: Re: pcnet32 devices with incorrect trident vendor ID
• Next by thread: Re: pcnet32 devices with incorrect trident vendor ID
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]