linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Mendham <petermendham@computing.dundee.ac.uk>
To: linuxppc-embedded@ozlabs.org
Subject: Some advice needed with Xilinx Framebuffer
Date: Fri, 27 Apr 2007 09:48:46 +0100	[thread overview]
Message-ID: <4631B8EE.10903@computing.dundee.ac.uk> (raw)

Dear all,

Thanks to Andrei, and others, I have a working framebuffer on my device, 
nicely driving a standard VGA screen.  I have just discovered that my 
*actual* target display is rotated VGA, i.e. 480x640.  I would like to 
use it as a 640x480 display.  I would love some advice from you 
knowledgeable people as to how best to go about this.  I have had some 
(rather naive) thoughts:
1. Modify the hardware to read pixels from non-contiguous locations thus 
leaving the framebuffer structure (as far as software is concerned) 
completely intact.  The major problem with this is that the hardware is 
no longer doing burst reads (because locations are not contiguous) so 
will be using the bus a lot less efficiently.
2. Modify the hardware to expect the framebuffer memory to be arranged 
column-wise, rather than row-wise (i.e. as a 480x640 rotated display in 
memory).  Is there a way to get the framebuffer to still present this as 
a 640x480 display?
3. Be honest about the whole thing and make the framebuffer report a 
480x640 display and hope that I can rotate everything else.  I believe 
the console can be rotated(?) I'd also really like to run the Links 
browser in direct framebuffer mode, and/or maybe X.  Don't know if 
that's possible but it certainly sounds like a minefield...
4. Some other secret magic hidden fourth option I don't know about.  
Maybe there's a standard way of doing this?

My feeling is that I should keep the whole nasty rotated business as low 
level as possible without affecting performance too much, but maybe I'm 
wrong.  Anything you can suggest would be greatly appreciated.

Thanks in advance,
-- Peter


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

                 reply	other threads:[~2007-04-27  8:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4631B8EE.10903@computing.dundee.ac.uk \
    --to=petermendham@computing.dundee.ac.uk \
    --cc=linuxppc-embedded@ozlabs.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).