linux-mips-fnet
[Top] [All Lists]

Re: More linker magic..

To: Martin Mares <mj@ucw.cz>
Subject: Re: More linker magic..
From: Ralf Baechle <ralf@uni-koblenz.de>
Date: Thu, 5 Aug 1999 14:23:03 +0200
Cc: Linus Torvalds <torvalds@transmeta.com>, Andi Kleen <ak@muc.de>, David Hinds <dhinds@zen.stanford.edu>, Pete Zaitcev <zaitcev@metabyte.com>, linux-kernel@vger.rutgers.edu, linux@engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
In-reply-to: <19990805105354.A167@albireo.ucw.cz>; from Martin Mares on Thu, Aug 05, 1999 at 10:53:54AM +0200
References: <19990804214327.A736@albireo.ucw.cz> <Pine.LNX.4.10.9908041653300.1313-100000@penguin.transmeta.com> <19990805105354.A167@albireo.ucw.cz>
On Thu, Aug 05, 1999 at 10:53:54AM +0200, Martin Mares wrote:

> > 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

<Prev in Thread] Current Thread [Next in Thread>