Re: Exposing ROM's though sysfs
From: Jesse Barnes (jbarnes_at_engr.sgi.com)
Date: 07/30/04
- Previous message: Adrian Bunk: "[2.6 patch] Canonically reference files in Documentation/ code comments part"
- In reply to: Vojtech Pavlik: "Re: Exposing ROM's though sysfs"
- Next in thread: Alan Cox: "Re: Exposing ROM's though sysfs"
- Reply: Alan Cox: "Re: Exposing ROM's though sysfs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Vojtech Pavlik <vojtech@suse.cz> Date: Fri, 30 Jul 2004 13:20:19 -0700
On Friday, July 30, 2004 12:48 pm, Vojtech Pavlik wrote:
> On Fri, Jul 30, 2004 at 12:41:50PM -0700, Jon Smirl wrote:
> > I looked at PCI quirks, they all seem to be fixing chipset issues. Do
> > we want to start including adapter specific quirks along with the more
> > general chipset one?
>
> It's mostly chipsets, but not just chipsets - take a look at the S3
> entries.
I think Martin's suggestion of just caching them all at probe time (or
optionally at driver attach time) is probably the simplest and easiest to get
right. It could be controllable via a boot time parameter. But I'm not
entirely opposed to using pci quirks.
Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Adrian Bunk: "[2.6 patch] Canonically reference files in Documentation/ code comments part"
- In reply to: Vojtech Pavlik: "Re: Exposing ROM's though sysfs"
- Next in thread: Alan Cox: "Re: Exposing ROM's though sysfs"
- Reply: Alan Cox: "Re: Exposing ROM's though sysfs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|