X server bug possibly OpenChrome in Jaunty

[Christopher Chan]

David Kuntadi wrote:
> On Wed, Oct 7, 2009 at 9:01 AM, Christopher Chan
> <christopher.chan at bradbury.edu.hk> wrote:
>
>   
>> Okay, so now you are saying that it is VIA's fault even though you have
>> already stated that openchrome is more stable than VIA's own drivers.
>>     
>
> Sure. VIA own driver work very well in MS Windows, but not for its
> linux driver. The fact that the opensource driver could beat the VIA's
> own driver shows that VIA do not have enough commitment to deliver
> good driver:
>
> http://forums.opensuse.org/tech-news/421513-chip-maker-via-joins-linux-foundation.html
>
>   
I fail to see how what VIA does or does not do has anything to do with a 
bug in openchrome.


>> I doubt that a double free error is related to knowing or not knowing
>> stuff about the chip.
>>     
>
> It is the first time I heard we could make driver for hardware without
> the need to know what hardware it is. Could you give me some reference
> of what you are saying? As far as I know, driver maker should know the
> hardware characteristic, and this is one of the most difficult parts
> of the technology i.e. make a piece of metal alive.
>   

What do you think the pioneers of X servers for various chips did? Of 
course, the driver that comes out of such circumstances will be lacking 
in some stuff or even incomplete and even useless. Again, documentation 
from the manufacturer about their chip has nothing to do with a double 
free error since that is not even something to do with communicating to 
the chip. I do not know why you are so keen on 'protecting' the 
openchrome guys.