From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: John Bradford <john@grabjohn.com>
Cc: "Måns Rullgård" <mru@users.sourceforge.net>,
luther@dpt-info.u-strasbg.fr, geert@linux-m68k.org,
jsimmons@infradead.org, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Re: rotation.
Date: Wed, 8 Jan 2003 13:55:30 +0100 [thread overview]
Message-ID: <20030108125530.GC11138@iliana> (raw)
In-Reply-To: <200301081205.h08C5mPv000776@darkstar.example.net>
On Wed, Jan 08, 2003 at 12:05:48PM +0000, John Bradford wrote:
> > > > > I'm about to implement rotation which is needed for devices
> > > > > like the ipaq.
> > > > > The question is do we flip the xres and yres values depending
> > > > > on the rotation or do we just alter the data that will be
> > > > > drawn to make the screen appear to rotate. How does hardware
> > > > > rotate view the x and y axis? Are they rotated or does just
> > > > > the data get rotated?
> > > >
> > > > Where are you going to implement the rotation? At the fbcon or
> > > > fbdev level?
> > > >
> > > > Fbcon has the advantage that it'll work for all frame buffer
> > > > devices.
> > >
> > > But you could also provide driver hooks for the chips which have
> > > such a rotation feature included (don't know if such exist, but i
> > > suppose they do, or may in the future).
>
> It would be nice to have an option to be able to do the rotation
> entirely in software - some desktop users might prefer to have a
> portait-orientated display, when their graphics card doesn't have any
> hardware rotation facilities at all.
Well, that is James plan. I suppose that for hardware that can do
hardware rotation, it will be faster to do it instead of having the
software do it though, and thus it would be nice to have a driver hook
or something.
This way, if rotation is asked, then if the driver supports hardware
rotation, do it, and if not, do it in software.
At first, no driver will support hardware rotation anyway, so it would
be done in software.
And then, you reuse the same stuff to drive a chinese console or
something such.
Friendly,
Sven Luther
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-08 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 22:44 rotation James Simmons
2003-01-08 10:24 ` rotation Geert Uytterhoeven
2003-01-08 10:48 ` rotation Sven Luther
2003-01-08 11:25 ` [Linux-fbdev-devel] " Måns Rullgård
2003-01-08 12:05 ` John Bradford
2003-01-08 12:55 ` Sven Luther [this message]
2003-01-09 19:45 ` [Linux-fbdev-devel] " James Simmons
2003-01-09 19:44 ` rotation James Simmons
2003-01-08 16:56 ` rotation Antonino Daplas
2003-01-09 19:54 ` [Linux-fbdev-devel] rotation James Simmons
2003-01-10 10:26 ` Antonino Daplas
2003-01-10 19:42 ` rotation James Simmons
2003-01-11 5:13 ` rotation Antonino Daplas
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=20030108125530.GC11138@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=geert@linux-m68k.org \
--cc=john@grabjohn.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@users.sourceforge.net \
/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).