From: Mark Hatle <mark.hatle@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] weston: Remove machine specific append
Date: Wed, 24 Oct 2018 11:13:12 +0100 [thread overview]
Message-ID: <dad7a11a-7fc4-27d5-7fc7-ce27bde60585@windriver.com> (raw)
In-Reply-To: <CAJTo0LZsk7V9tSk6APAMOzS_3fkU56bk7V4KqiZW_ieQ80i9GA@mail.gmail.com>
On 10/19/18 11:51 AM, Burton, Ross wrote:
> On Thu, 18 Oct 2018 at 16:39, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> Two questions:
>>> 1) does qemu still need fbdev or does virtio/drm work now? (iirc, we
>>> still have a crippled qemu here)
>>> 2) Can this be overridden in a config file instead
>>
>> I did not understand how to do this. The alternative I see then is to make this
>> a machine_arch package.. since the configuration can change?
>>
>> (I'm not very familiar with this part of the system.)
>
> Looks like Weston supports this in the config file:
>
> [core]
> backend = fbdev-backend.so
>
> Should be easy enough to ship a weston.ini for qemu machines.
>
> Ross
>
I've been fighting this, and (assumign the above is correct), I can't figure out
how to get weston to actually load the ini file. I suspect the problem is
simply I don't know what path to put the config file in.... but since it runs on
boot, I don't have any way to intercept it and strace or similar to see if it's
actually trying to load things.
I'll continue working on them, but if anyone can help tell me where the ini file
belongs or how to debug this -- that would help a lot.
(I've tried putting the file directly in the sysconf [/etc] directory, as well
as /etc/xdg which was mentioned by the man page.)
--Mark
next prev parent reply other threads:[~2018-10-24 10:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:43 [PATCH 0/4] Fix a number of non-machine pkg hash change issues Mark Hatle
2018-10-17 16:43 ` [PATCH 1/4] systemd: Remove items that made this machine (qemu) specific Mark Hatle
2018-10-18 8:53 ` ChenQi
2018-10-18 15:37 ` Mark Hatle
2018-10-18 22:57 ` Richard Purdie
2018-10-20 8:41 ` Richard Purdie
2018-10-20 16:14 ` Mark Hatle
2018-10-17 16:43 ` [PATCH 2/4] mesa: Remove machine specific append Mark Hatle
2018-10-17 16:43 ` [PATCH 3/4] weston: " Mark Hatle
2018-10-18 10:24 ` Burton, Ross
2018-10-18 15:38 ` Mark Hatle
2018-10-19 10:51 ` Burton, Ross
2018-10-24 10:13 ` Mark Hatle [this message]
2018-10-25 8:36 ` Alexander Kanavin
2018-10-25 9:05 ` Martin Jansa
2018-10-25 9:26 ` Richard Purdie
2018-10-17 16:43 ` [PATCH 4/4] gstreamer: " Mark Hatle
2018-10-18 10:28 ` Richard Purdie
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=dad7a11a-7fc4-27d5-7fc7-ce27bde60585@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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