rue/xserver/hw/kdrive/vesa/vesa.c 2008-10-02
11:10:03.0 +0200
@@ -758,7 +758,7 @@
{
bits = *sha++;
vesaInvertBits32(bits);
- *win++ = bits;
+ *win++ = ccpxsswap(bits);
}
On Thu, Sep 11, 2008 at 1:57 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 01:45:25PM +0200, Leon Ljunggren wrote:
>> On Thu, Sep 11, 2008 at 1:00 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
>> > On Thu, Sep 11, 2008 at 11:45:02AM +0200,
On Thu, Sep 11, 2008 at 1:00 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 11:45:02AM +0200, Leon Ljunggren wrote:
>> On Wed, Sep 10, 2008 at 5:19 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
>> > Change fbScreenInit in hw/kdrive/src/kdrive.c to
On Wed, Sep 10, 2008 at 5:19 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 05:06:32PM +0200, Leon Ljunggren wrote:
>> > wfb works everywhere fb does (i.e. everywhere). fb is the normal
>> > software rasterisation code, which takes a bass add
> wfb works everywhere fb does (i.e. everywhere). fb is the normal
> software rasterisation code, which takes a bass address, stride, etc,
> and writes directly to that range. wfb is literally the exact same
> codebase as fb, but instead of writing directly to memory, will issue a
> function call
On Wed, Sep 10, 2008 at 3:09 PM, Daniel Stone <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 03:05:48PM +0200, Leon Ljunggren wrote:
>> I have compiled and got kdrive (Xfbdev), using the latest stable
>> source from git, running on my ARM based system but I'm exp
bits for any one mask.
Anyone that has any idea on what I can do to fix this? I guess I could
swap the byte order of each pixel as they are written to the
framebuffer, but I haven't been able to find where this writing is
done in the server.
Thanks
Leon Ljunggren
__
