From: "Michel Dänzer" <michel@daenzer.net>
To: Roman Fietze <roman.fietze@telemotive.de>
Cc: Bill Gatliff <bgat@billgatliff.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Xorg on Fujitsu "Lime" with MPC5200b?
Date: Fri, 16 Apr 2010 10:30:23 +0200 [thread overview]
Message-ID: <1271406623.4030.43.camel@thor.local> (raw)
In-Reply-To: <201004160814.01037.roman.fietze@telemotive.de>
On Fre, 2010-04-16 at 08:14 +0200, Roman Fietze wrote:=20
>=20
> On Thursday 15 April 2010 18:07:03 Bill Gatliff wrote:
>=20
> > I would love it if you posted your code! Thanks!!
>=20
> In this source file I just added my own routines:
>=20
> Index: programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> --- programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c (revision 6)
> +++ programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c (revision 7)
> @@ -139,8 +139,8 @@
> "shadowInit",
> "shadowSetup",
> "shadowUpdatePacked",
> - "shadowUpdatePackedSwapped16Weak",
> - "shadowUpdatePackedSwapped32Weak",
> + "shadowUpdatePackedSwapped16",
> + "shadowUpdatePackedSwapped32",
> "shadowUpdateRotatePacked",
> NULL
> };
> @@ -619,6 +619,7 @@
> ScrnInfoPtr pScrn =3D xf86Screens[pScreen->myNum];
> FBDevPtr fPtr =3D FBDEVPTR(pScrn);
> VisualPtr visual;
> + ShadowUpdateProc pupdate;
> int init_picture =3D 0;
> int ret,flags,width,height;
> =20
> @@ -794,7 +795,7 @@
> xf86DrvMsg(pScrn->scrnIndex, X_WARNING,
> "RENDER extension initialisation failed.\n");
> =20
> - pupdate =3D pScrn->bitsPerPixel > 16 ? shadowUpdatePackedSwapped3=
2Weak() :
> shadowUpdatePackedSwapped16Weak();
> + pupdate =3D pScrn->bitsPerPixel > 16 ? shadowUpdatePackedSwapped3=
2 : shado
> wUpdatePackedSwapped16;
> =20
> if (fPtr->shadowFB &&=20
> (!shadowSetup(pScreen) || !shadowAdd(pScreen, NULL,
I hope you're aware that this really just hacks around the kernel
framebuffer device not exposing the framebuffer to userspace according
to the fbdev interface (see struct fb_bitfield
in /usr/include/linux/fb.h), and this will affect everything else using
the framebuffer device as well.
It would be better to handle this in the kernel framebuffer device,
either via hardware byte swapping facilities if available, or otherwise
e.g. via FB_DEFERRED_IO.
--=20
Earthling Michel D=C3=A4nzer | http://www.vmware.c=
om
Libre software enthusiast | Debian, X and DRI developer
next prev parent reply other threads:[~2010-04-16 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 3:07 Xorg on Fujitsu "Lime" with MPC5200b? Bill Gatliff
2010-04-15 4:53 ` Benjamin Herrenschmidt
2010-04-15 7:21 ` Roman Fietze
2010-04-15 13:01 ` Bill Gatliff
2010-04-15 13:53 ` Roman Fietze
[not found] ` <v2ma0706c7b1004150906p34b853a0r80e2bb751e034b97@mail.gmail.com>
2010-04-15 16:07 ` Bill Gatliff
2010-04-16 6:14 ` Roman Fietze
2010-04-16 8:30 ` Michel Dänzer [this message]
2010-04-15 20:14 ` Bill Gatliff
2010-04-16 5:48 ` Roman Fietze
2010-04-16 2:51 ` Bill Gatliff
2010-04-16 8:28 ` Roman Fietze
2010-04-16 9:25 ` Gabriel Paubert
2010-04-15 7:44 ` Anatolij Gustschin
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=1271406623.4030.43.camel@thor.local \
--to=michel@daenzer.net \
--cc=bgat@billgatliff.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=roman.fietze@telemotive.de \
/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;
as well as URLs for NNTP newsgroup(s).