Re: [PATCH] DAC palette width retrieval

2009-08-04 Thread Robert Millan
Committed. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." ___

Re: [PATCH] DAC palette width retrieval

2009-07-25 Thread Vladimir 'phcoder' Serbinenko
>> *_mask normally shouldn't be used in index color by internal grub >> functions anyway. And if payload needs a special convention for >> passing color info for indexed modes it should be handled by loader > > Ok.  But if we decide that *_mask should go away, this is quite independant > from this

Re: [PATCH] DAC palette width retrieval

2009-07-25 Thread Robert Millan
On Sat, Jul 25, 2009 at 02:24:22PM +0200, Vladimir 'phcoder' Serbinenko wrote: > > Now I'm not completely sure where does this belong.  I think it's somewhat > > generic and we can reasonably expect other OSes to want this information > > too, but I'm not completely sure. > For me putting these val

Re: [PATCH] DAC palette width retrieval

2009-07-25 Thread Vladimir 'phcoder' Serbinenko
> Now I'm not completely sure where does this belong.  I think it's somewhat > generic and we can reasonably expect other OSes to want this information > too, but I'm not completely sure. For me putting these values to *_mask is ok but it may put some limits for future cards but as payloads have no

[PATCH] DAC palette width retrieval

2009-07-25 Thread Robert Millan
When using packed color modes, Linux expects we fill the color sizes with the value obtained from the DAC. If we give it zeroes (like we currently do) it displays a blank screen. This can be reproduced by attempting to boot Linux with a 8-bit color mode (e.g. set gfxpayload=800x600x8). Now I'm