Re: pcnet32 devices with incorrect trident vendor ID
- From: Daniel Drake <dsd@xxxxxxxxxx>
- Date: Thu, 12 Jan 2006 21:03:17 +0000
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 majordomo@xxxxxxxxxxxxxxx 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
- pcnet32 devices with incorrect trident vendor ID
- From: Daniel Drake
- Re: pcnet32 devices with incorrect trident vendor ID
- From: Matthew Wilcox
- [PATCH] Prevent trident driver from grabbing pcnet32 hardware
- Prev by Date: Re: [GIT PATCH] PCI patches for 2.6.15 - retry
- Next by Date: Re: 2.6.15-mm3
- Previous by thread: Re: pcnet32 devices with incorrect trident vendor ID
- Next by thread: Re: pcnet32 devices with incorrect trident vendor ID
- Index(es):
Relevant Pages
|
|
