Re: Exposing ROM's though sysfs

[Vojtech Pavlik <vojtech@suse.cz>]

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.

> 
> --- Vojtech Pavlik <vojtech@suse.cz> wrote:
> 
> > On Fri, Jul 30, 2004 at 12:25:10PM -0700, Jon Smirl wrote:
> > > --- Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> > > > How about this patch?
> > > 
> > > Here's the ROM access code I've been using but it's not in the form
> > > that we need.
> > > 
> > > We do need a standard scheme for the radeon situation of having a
> > bug
> > > in the ROM access logic. Is it ok to put the fix for this in the
> > radeon
> > > driver? So if you read the ROM before the driver is loaded it won't
> > be
> > > there (proabably FFFF's). After the driver loads the fix will run
> > as
> > > part of the driver init and the ROM access functions will work
> > right. 
> > 
> > IMO the fix should go to the PCI quirk logic. That's a place to work
> > around PCI config bugs.
> > 
> > -- 
> > Vojtech Pavlik
> > SuSE Labs, SuSE CR
> > 
> 
> 
> =====
> Jon Smirl
> jonsmirl@yahoo.com
> 
> 
> 	
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail 
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR