Re: FX and PiTFT on Raspberry

2014-05-04 Thread Marco Wiorek
Hello Daniel,

it is basically the same problem you've answered here:
http://www.raspberrypi.org/forums/viewtopic.php?f=81&t=52025
According to the 4th post here:
http://www.raspberrypi.org/forums/viewtopic.php?f=67&t=58952 it is supposed to
just work on the first
display_id. For now I am using fbcp to copy the framebuffer from fb0 to fb1 but
a more native alternative would be better.


Regards,
Marco


> Daniel Blaukopf  hat am 4. Mai 2014 um 13:20
> geschrieben:
>
>
> Hi Marco,
>
> Is it the parameter to vc_dispmanx_display_open that you want to change?
> Currently this is fixed at 0 in dispmanCursor.c but we could make that
> configurable. Is the problem that JavaFX is drawing to the wrong screen, or
> getting the wrong screen size? Would you open a JIRA describing what you need?
>
> Thanks,
> Daniel
>
> On May 4, 2014, at 1:01 PM, Marco Wiorek  wrote:
>
> > Hello guys,
> >
> > I wonder if it is possible to redirect the eglfb output to /dev/fb1 instead
> > of
> > fb0.
> > An older revision of
> > modules/graphics/src/main/native-prism-es2/eglfb/wrapped_egl.c
> > (19ca9150cb33)
> > seem to had it hard coded but in newer versions it is not.
> >
> > The touch events are perfectly catched but the frame buffer unfortunately is
> > wrong.
> >
> > Regards and thanks in advance,
> > Marco
>


Re: FX and PiTFT on Raspberry

2014-05-04 Thread Daniel Blaukopf
Hi Marco,

Is it the parameter to vc_dispmanx_display_open that you want to change? 
Currently this is fixed at 0 in dispmanCursor.c but we could make that 
configurable. Is the problem that JavaFX is drawing to the wrong screen, or 
getting the wrong screen size? Would you open a JIRA describing what you need?

Thanks,
Daniel 

On May 4, 2014, at 1:01 PM, Marco Wiorek  wrote:

> Hello guys,
> 
> I wonder if it is possible to redirect the eglfb output to /dev/fb1 instead of
> fb0.
> An older revision of
> modules/graphics/src/main/native-prism-es2/eglfb/wrapped_egl.c (19ca9150cb33)
> seem to had it hard coded but in newer versions it is not.
> 
> The touch events are perfectly catched but the frame buffer unfortunately is
> wrong.
> 
> Regards and thanks in advance,
> Marco