Re: AGL 10.0.0 with Raspberry Pi4 1020x600 display issue

["Stefan Gudmundsson" <exologic@xxxxxxxxx>]

Thanks for the quick feedback.

There is indeed a "wayland.ini" file, but perhaps it's ignored by the
system. It's in the QT recipes as well. 

It seems to me that not using more common touchscreens (that fits the PI) is
a mistake. Small/embedded 1080p touchscreens are unobtainium. Supporting a
more common panel would encourage more PoCs and tests, that's my take
anyway.

Most real implementations would use their own UX anyway, but as a PoC
vehicle using PI's and common Touch panels would be of value, my 2c....

/Stefan


-----Original Message-----
From: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
[mailto:agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Marius
Vlad
Sent: Thursday, November 5, 2020 9:56 AM
To: agl-dev-community@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  AGL 10.0.0 with Raspberry Pi4 1020x600
display issue

On Thu, Nov 05, 2020 at 09:36:20AM -0800, Stefan Gudmundsson wrote:
> Hello,
Hi,
> 
>
> 
> AGL 9.0.0 works well with a Raspberry Pi4 HDMI touchscreen with 
> resolution of 1024x600.
> 
> But in 10.0.0, the display appears up scaled many times, you only see 
> upper quadrants of images and HMI is at least 4x too large, including 
> text etc. A regular HDMI monitor works, as does a HD TV.
> 
>
> 
> I have tried setting mode in wayland.ini, but that does nothing. 
There's no wayland.ini configuration file.
> 
>
> 
> Considering it worked in 9, something changed/broke to 10.
> 
>
> 
> Any ideas? Where can I find adjustments to screen resolution? 
Long story short is that you need a 1080 resolution for your display to work
with the demos.
> 
> Will it only honor "standard" resolutions?
It will honor whatever resolution you use in your weston.ini file, but the
applications are expecting a 1920x1080 resolution. With the lastest release
(10) a 1080 (HD) display will be needed to work out-of-the box. 
Any other resolutions will need modification to the demos.

Previously this was possible by letting the toolkit handle that, so there's
nothing in the way of doing the same thing, as a work-around (and you can
find examples from previous versions on how to do that).
Either way, by using adjusting the applications to handle multiple
resolutions, or by using the toolkit to perform the upscale/downscale for
you, you'll need to operate modifications for every application.
> 
>
> 
> Stefan
> 
>
> 
> 
> 
> 
> 
> 








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8816): https://lists.automotivelinux.org/g/agl-dev-community/message/8816
Mute This Topic: https://lists.automotivelinux.org/mt/78056612/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-