diff options
| author | Alexander Kanavin <alex.kanavin@gmail.com> | 2020-02-16 16:50:08 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-02-18 23:53:54 +0000 |
| commit | ec7beb650fd3ad445e77d2c3c8fde27556d9d0c9 (patch) | |
| tree | d2b56ef92514f1eaa2f3105f12277e1fae1c863d /meta/classes | |
| parent | e88fe83014b771b1868ee1159672c80f7710f41d (diff) | |
| download | poky-ec7beb650fd3ad445e77d2c3c8fde27556d9d0c9.tar.gz | |
qemux86: drop resolution setting via uvesafb
I am not sure if this has ever worked, but uvesafb is a really
outdated (VBE from the 1990s), awkward (needs v86d) and limited
(no support for high resolutions) way to do it.
The specific reason 640x480-32 was introduced (ages ago) was
to force 32 bit mode with vmware driver, as 16bit had rendering issues.
The modern, supported option is video=... kernel parameter documented here:
https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID
https://github.com/torvalds/linux/blob/master/Documentation/fb/modedb.rst
which can be passed directly to runqemu and doesn't require special
kernel modules.
Sato under X will continue to use 640x480 as that is hardcoded into
xorg.conf under qemu.
(From OE-Core rev: 1cf26f69fd89b43be24cd1232c43e5050b9d718a)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes')
0 files changed, 0 insertions, 0 deletions