On Thu, Sep 9, 2010 at 11:57 PM, Alexander Graf wrote:
>
> On 09.09.2010, at 23:06, Ilyes Gouta wrote:
>
> >
> >
> > On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta
> wrote:
> > Hi,
> >
> > Well, actually I'd like to run sh4 binaries in linux-user mode, where
> these are actually DirectFB applicatio
On 09.09.2010, at 23:06, Ilyes Gouta wrote:
>
>
> On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta 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.
>
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 h
On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta 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
On Thu, Sep 9, 2010 at 8:19 PM, Ilyes Gouta 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 could
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
