linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev@vger.kernel.org
Subject: Re: kdrive vs. xorg rotation on AT91SAM9263 atmel_lcdfb
Date: Tue, 23 Mar 2010 23:02:26 +0000	[thread overview]
Message-ID: <1269385346.16545.288.camel@thor.local> (raw)
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C276323@mail03.cyberswitching.local>

On Sam, 2010-03-20 at 12:25 -0700, Chris Verges wrote: 
> Hi fellow fbdev users,
> 
> I'm seeking help with a migration from kdrive to xorg.  Under
> kdrive-fbdev, I'm able to rotate the X11 output using xrandr in all four
> orientations: normal, left, right, inverted.  However, under
> xf86-video-fbdev, xrandr only reports that it does not support left,
> right, or inverted rotations.  Dynamic rotation is critical for this
> application, so I cannot use the "Rotate" option in xorg.conf.
> 
> The atmel_lcdfb driver that we're using in the kernel does not support
> hardware rotation, so I believe that a software-based Shadow Buffer is
> required.  (Please correct me if I'm wrong on this!)  I added in the
> "ShadowFB" option to xorg.conf for the fbdev device, but xrandr still
> only reports normal rotation possible.
> 
> I've hit a brick wall in my own research on this, so would appreciate
> any help that the community can offer.  Any suggestions?

Support for this simply hasn't been implemented yet in the
xf86-video-fbdev driver.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

  reply	other threads:[~2010-03-23 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 19:25 kdrive vs. xorg rotation on AT91SAM9263 atmel_lcdfb Chris Verges
2010-03-23 23:02 ` Michel Dänzer [this message]
2010-03-24  0:14 ` Chris Verges
2010-03-25  8:57 ` Michel Dänzer

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=1269385346.16545.288.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).