> > Broken non-updated drivers simply won't compile, but the fixes tend to be
> > rather straightforward. The less straightforward part is if some driver
> > tries to change the start offsets etc, which implies that he really has to
> > unregister the resource and re-register somewhere else. I don't know if
> > anybody actually does that, although I do know that there are drivers that
> > play some silly games with their resource list.
>
> The only case somebody modifies the addresses I know of is fixup for
> broken S3 cards reporting incorrect region sizes. I'll modify the generic
> PCI fixup code to do it automatically.
SGI IOC3 is another case. This card only decodes the first 32 bytes of
the configuration space, so the a few bogus mappings will be detected by
the PCI code. Any generic facility for this or what is your proposed
way of handling such cards?
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/