dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Cédric Cano" <ccano@interfaceconcept.com>
Cc: tjourdan@interfaceconcept.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Big Endian support for RV730 (Mesa r600)
Date: Wed, 13 Apr 2011 22:05:04 +1000	[thread overview]
Message-ID: <1302696304.28876.82.camel@pasglop> (raw)
In-Reply-To: <4DA406D0.2010208@ic.fr>

On Tue, 2011-04-12 at 10:01 +0200, Cédric Cano wrote:
> Hi
> 
> Here you are a patch that adds big endian support for rv730 in r600 
> classic mesa driver. The BE modifications are almost the same as the DRM 
> / DDX driver modifications 
> (http://lists.freedesktop.org/archives/dri-devel/2011-February/008151.html).
> 
> I used the mesa-demos to test the driver status on big endian platform. 
> Nearly all demos renders the same as on Intel architecture. 
> Nevertheless, there are still some issues in glReadPixels (r600_blit) 
> with some formats. I can't figure out exactly what and when data must be 
> swapped (set_tex_resoures, set_render_target...). Review of the patch 
> would be greatly appreciated.
> 
> It seems that r600g will be the default for Mesa 7.11 so I'll try to 
> enable big endian support for Gallium now.

Cool stuff !

I'll try to test that one of these days on various ppc's

Cheers,
Ben.


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-04-13 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  8:01 [PATCH] Big Endian support for RV730 (Mesa r600) Cédric Cano
2011-04-13 12:05 ` Benjamin Herrenschmidt [this message]
2011-04-13 12:10   ` Benjamin Herrenschmidt
2011-04-14  7:33     ` Cédric Cano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1302696304.28876.82.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=ccano@interfaceconcept.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tjourdan@interfaceconcept.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox