From: Khem Raj <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 05/10] weston-init: use the drm backend rather than fbdev one
Date: Wed, 19 Feb 2020 10:37:57 -0800 [thread overview]
Message-ID: <30085196-1dc5-d64e-73ca-416f52291a9e@gmail.com> (raw)
In-Reply-To: <CANNYZj-gvCsW2XzuddVaZTegS81VnHZXXTm2L0jHyG9vcXK-RA@mail.gmail.com>
On 2/19/20 10:06 AM, Alexander Kanavin wrote:
> Will that take precedence over qemuall though? Sounds brittle. Another
> option is to make the fbdev configuration specific to mips and arm, as
> using kms does not need a configuration at all.
>
I think it will. arch specific overrides should come before generic ones.
> Alex
>
> On Wed 19. Feb 2020 at 18.21, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
>
> On Wed, Feb 19, 2020 at 1:45 AM Alexander Kanavin
> <alex.kanavin@gmail.com <mailto:alex.kanavin@gmail.com>> wrote:
> >
> > On Tue, 18 Feb 2020 at 02:56, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> wrote:
> >>
> >>
> >>> but I'll get to it, or you are welcome to try and report.
> >>> Mips can be either fixed like suggested, or be a specific
> exception.
> >>>
> >>> For the rest of the targets, I see that you have extended the
> fbdev fallback to qemuall only on Jan 9 this year. So it's very
> unlikely anyone is using them to run weston (not to mention how
> painfully slow that would be), and so it would just be wasteful to
> test or fix them.
> >>
> >>
> >> We should be only applying tested part debugging these breakages
> is very hard so when we know it will break we should be careful as
> with this patch
> >
> >
> > I have tested these things now:
> >
> > 1. Switching mips from cirrus to std vga works fine, as long as
> xorg.conf is also deleted (it's written specifically for cirrus and
> isn't working or needed with std vga). Both weston and sato boot and
> look right. I'll send a patch for it.
> >
> > 2. Switching weston to kms backend degrades performance to
> unusable level, as neither kvm nor virtio/virgl are available for
> non-x86 qemu, and kms backend is using software renderer in mesa. So
> fbdev is the only realistic option there. But for x86 qemu kms is
> still viable. I'm not sure how to best configure it though.
>
> copy qemuall/weston.ini new folders qemux86 and qemux86-64 and point
> to backend it should be using.
>
> >
> > Alex
>
next prev parent reply other threads:[~2020-02-19 18:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 15:50 [PATCH 01/10] core-image-sato-sdk-ptest: do not pull in ptest-pkgs Alexander Kanavin
2020-02-16 15:50 ` [PATCH 02/10] procps: upstream has switched to gitlab Alexander Kanavin
2020-02-16 16:53 ` Khem Raj
2020-02-16 16:56 ` Alexander Kanavin
2020-02-16 20:06 ` Khem Raj
2020-02-16 20:45 ` Alexander Kanavin
2020-02-17 2:35 ` Khem Raj
2020-02-17 8:12 ` Alexander Kanavin
2020-02-17 18:39 ` Khem Raj
2020-02-16 15:50 ` [PATCH 03/10] qemux86: do not add vga=0 to kernel parameters Alexander Kanavin
2020-02-16 15:50 ` [PATCH 04/10] qemux86: drop resolution setting via uvesafb Alexander Kanavin
2020-02-16 16:01 ` Martin Jansa
2020-02-16 16:10 ` Alexander Kanavin
2020-02-16 16:15 ` Alexander Kanavin
2020-02-16 15:50 ` [PATCH 05/10] weston-init: use the drm backend rather than fbdev one Alexander Kanavin
2020-02-16 17:00 ` Khem Raj
2020-02-16 17:07 ` Alexander Kanavin
2020-02-16 20:09 ` Khem Raj
2020-02-16 21:03 ` Alexander Kanavin
2020-02-17 2:30 ` Khem Raj
2020-02-17 8:22 ` Alexander Kanavin
2020-02-17 13:16 ` Alexander Kanavin
2020-02-17 18:44 ` Khem Raj
2020-02-17 19:29 ` Alexander Kanavin
2020-02-18 1:56 ` Khem Raj
2020-02-19 9:45 ` Alexander Kanavin
2020-02-19 17:20 ` Khem Raj
2020-02-19 18:06 ` Alexander Kanavin
2020-02-19 18:37 ` Khem Raj [this message]
2020-02-16 15:50 ` [PATCH 06/10] webkitgtk: x11 and wayland are not mutually exclusive Alexander Kanavin
2020-02-16 15:50 ` [PATCH 07/10] weston: add a basic runtime test Alexander Kanavin
2020-02-16 15:50 ` [PATCH 08/10] webkitgtk: unbreak wayland build Alexander Kanavin
2020-02-16 16:09 ` Martin Jansa
2020-02-16 16:14 ` Alexander Kanavin
2020-02-16 18:06 ` Richard Purdie
2020-02-16 20:14 ` Khem Raj
2020-02-16 20:51 ` Alexander Kanavin
2020-02-23 14:33 ` Joshua Watt
2020-02-27 15:49 ` [wpe-webkit] " Carlos Alberto Lopez Perez
2020-02-27 16:04 ` Joshua Watt
2020-02-16 15:50 ` [PATCH 09/10] wayland: convert to meson build Alexander Kanavin
2020-02-17 14:35 ` Richard Purdie
2020-02-17 14:50 ` Alexander Kanavin
2020-02-17 14:52 ` Richard Purdie
2020-02-17 14:53 ` Alexander Kanavin
2020-02-16 15:50 ` [PATCH 10/10] ptest-packagelists: mention ifupdown ptest in a comment Alexander Kanavin
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=30085196-1dc5-d64e-73ca-416f52291a9e@gmail.com \
--to=raj.khem@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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