qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ilyes Gouta <ilyes.gouta@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux framebuffer emulation in qemu linux-user
Date: Thu, 9 Sep 2010 22:07:38 +0100	[thread overview]
Message-ID: <AANLkTinyGNmr6Aa0mxKPPCR3eXM0HXPUmcRGnJn8-Pkk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=_bigK_YdHOEw+oedxKyQ5KrQxMTWTyv-HMJGX@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]

Hi,

> No, but it could be possible to convert the DirectFB ioctl structures
> between guest and host. Other ioctls are translated this way. I guess
> nobody has cared about framebuffer support yet.

DirectFB (on the sh4 side) is just a client which is interacting with the
framebuffer. It doesn't have its "own" set of ioctls.

Is handling FBIOGET_FSCREENINFO, FBIOGET_VSCREENINFO and FBIOPUT_VSCREENINFO
enough to abstract a basic Linux framebuffer and emulate it (by not
forwarding these to a native framebuffer)?

-Ilyes

On Thu, Sep 9, 2010 at 9:57 PM, Blue Swirl <blauwirbel@gmail.com> wrote:

> On Thu, Sep 9, 2010 at 8:39 PM, Ilyes Gouta <ilyes.gouta@gmail.com> wrote:
> > Hi,
> > Well, actually I'd like to run sh4 binaries in linux-user mode, where
> these
> > are actually DirectFB applications which rely on the standard Linux
> > framebuffer to display things.
> > In my use case, I'd like to route these ioctl in qemu to be handled by
> the
> > SDL back-end (or even a DirectFB instance running on the host) instead of
> > being dispatched to the native framebuffer driver, running on the host.
> > Is this feature available in the current qemu code base?
>
> No, but it could be possible to convert the DirectFB ioctl structures
> between guest and host. Other ioctls are translated this way. I guess
> nobody has cared about framebuffer support yet.
>
> See linux-user/ioctls.h.
>
> > Thanks,
> > -Ilyes
> >
> > On Thu, Sep 9, 2010 at 9:28 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> >>
> >> On Thu, Sep 9, 2010 at 8:19 PM, Ilyes Gouta <ilyes.gouta@gmail.com>
> wrote:
> >> > Hi,
> >> > Is it possible, as of today, to emulate a classic Linux framebuffer
> when
> >> > using qemu linux-user mode?
> >> > At a first glance, I saw in the code that
> >> > FBIOGET_FSCREENINFO, FBIOGET_VSCREENINFO and FBIOPUT_VSCREENINFO being
> >> > declared by couldn't locate where they're handled. Are these hooked to
> >> > the
> >> > SDL back-end?
> >>
> >> SDL is only used for system emulation. It should be possible to add
> >> conversions (for example, from PPC 32 bit BE to x86_64 64 bit LE) for
> >> FB ioctls in order to pass them to the host FB device. But what would
> >> be the use case for this?
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 3535 bytes --]

      parent reply	other threads:[~2010-09-09 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 20:19 [Qemu-devel] Linux framebuffer emulation in qemu linux-user Ilyes Gouta
2010-09-09 20:28 ` Blue Swirl
     [not found]   ` <AANLkTimrjxo03qskAae7syDcHrq=frqiG5VnbmcSN8K2@mail.gmail.com>
2010-09-09 21:06     ` Ilyes Gouta
2010-09-09 22:57       ` Alexander Graf
2010-09-09 23:42         ` Ilyes Gouta
     [not found]     ` <AANLkTi=_bigK_YdHOEw+oedxKyQ5KrQxMTWTyv-HMJGX@mail.gmail.com>
2010-09-09 21:07       ` Ilyes Gouta [this message]

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=AANLkTinyGNmr6Aa0mxKPPCR3eXM0HXPUmcRGnJn8-Pkk@mail.gmail.com \
    --to=ilyes.gouta@gmail.com \
    --cc=qemu-devel@nongnu.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).