[PATCH]: Fix GLX crashes on RISC cpus.

[Paulo Cesar Pereira de Andrade]

Daniel Stone wrote:
> On Fri, Dec 28, 2007 at 03:28:35PM -0200, Paulo Cesar Pereira de Andrade wrote:
>>   Yes, the problems are more like a "lack of human resources", or some kind
>> of X Org "janitors" team,
>
> Well, patches welcome.  People have already started tagging bugs
> 'janitor' on Bugzilla.
  Good to know :-)  Now it is only required to have people to work on it.
Basically a work that very few people consider important or even notice,
and that usually doesn't produce copyrightable work. Unfortunately AFAIK,
most "janitors" on OSS are "good samaritans" that work on their free
time.

>> that would work on making sure old drivers still
>> work (usually ISA only cards), that lib*fb*so that isn't libfb.so still
>> is usable,
>
> Well, basically the only thing preventing conversion from cfb et al is
> people with the hardware to actually test that the final result works.
  Or maybe someone implementing things like 1bpp/4bpp/bank switch/whatever
in an extension to libfb; probably would be easier to work on the existing
modules. Anyway, it should be possible to test the vga driver in any x86
computer. And I think it is functional again with X server 1.4

>> and people watching over the commits to not "easily" allow
>> breaking API if an alternate/compat method is doable, etc.
>
> (In these cases, no.)
  Maybe I should have said "people with common sense and some understanding
of the concepts of ABI/API". In, other words, avoid breaking working code.

>>   There is also the problem of symbol clashes, but if I recall corectly, the
>> only case it happens outside Xserver<->libraries is the modes directory,
>> if for some reason a driver that has a copy of this code is compiled using
>> it, while the server compiles with its own version,
>
> 'Don't do that.'
  I know, but it may take some time to find out the cause, when you are
presented to a problem, but doesn't know all details, i.e. discovering this
kind of problems with duplicated symbols. And there isn't a clear way to
find out dependencies or proper "build order" in modular X org.

> Cheers,
> Daniel
Paulo