From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: airlied@linux.ie, dri-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5]: drm: ati_pcigart: Do not access I/O MEM space using pointer derefs.
Date: Fri, 13 Feb 2009 08:29:27 +1100 [thread overview]
Message-ID: <1234474167.29851.66.camel@pasglop> (raw)
In-Reply-To: <1234473963.29851.65.camel@pasglop>
On Fri, 2009-02-13 at 08:26 +1100, Benjamin Herrenschmidt wrote:
> > 1) The kernel radeon framebuffer driver doesn't mess with
> > the framebuffer endianness setting.
> >
> > 2) On >= R300 (which my chip is), Xorg leaves it alone too.
>
> They leave alone the swapper of the engine, not the fb one
> (SURFACE_CNTL) afaik.
Though actually if you stick to 8bpp, the default, the swapper will be
off in radeonfb.
> I dbl checked the other day and it seems that we setup the GART before
> we whack it tho but it might be an issue in conjunction with radeonfb
> (ie, I don't have radeonfb on my test embedded boards as I rely on X to
> POST the cards using ATOMBIOS).
>
> Cheers,
> Ben.
>
next prev parent reply other threads:[~2009-02-12 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 10:15 [PATCH 1/5]: drm: ati_pcigart: Do not access I/O MEM space using pointer derefs David Miller
2009-02-12 10:35 ` Benjamin Herrenschmidt
2009-02-12 11:09 ` David Miller
2009-02-12 11:23 ` Dave Airlie
2009-02-12 22:17 ` David Miller
2009-02-12 21:26 ` Benjamin Herrenschmidt
2009-02-12 21:29 ` Benjamin Herrenschmidt [this message]
2009-02-14 6:09 ` David Miller
2009-02-14 7:42 ` Dave Airlie
2009-02-14 8:58 ` David Miller
2009-02-14 9:09 ` Benjamin Herrenschmidt
2009-02-14 9:07 ` Benjamin Herrenschmidt
2009-02-14 9:11 ` David Miller
2009-02-14 9:51 ` David Miller
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=1234474167.29851.66.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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