All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Mesa and Wayland updates
Date: Wed, 5 Jun 2013 15:51:02 +0200	[thread overview]
Message-ID: <20130605135102.GG30727@jama> (raw)
In-Reply-To: <CAJTo0LZjJhHrSEXmA==qGDgWbSRDdXQh0_ocwVsFb=wsyVPeTQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

On Fri, May 31, 2013 at 10:52:07AM +0100, Burton, Ross wrote:
> On 31 May 2013 10:30, Burton, Ross <ross.burton@intel.com> wrote:
> >> At the time of writing that weston didn't support runtime detection or config files entries for selecting the backend, only commandline arguments. So whatever is getting picked at build time, you're stuck with that. Does 1.1.x address that situation?
> >
> > Sadly, not as far as I'm aware.  I have 1.1 in another branch but it
> > totally broke GTK+ 3 applications (which didn't repaint after the
> > initial creation), which is pretty sad.  Relevant developers harassed.
> 
> In a massive shock, the weston man page is actually useful.  Sadly
> it's clear that the backend choice is either x11 if DISPLAY is set,
> wayland-over-wayland if WAYLAND_DISPLAY is set, otherwise the command
> line argument finally falling back to the "default" (drm out of the
> box).
> 
> So if we want a single binary that supports both DRM and fbdev, then
> we need to use command-line options.   I guess our startup script
> should handle this and we can add another optional machine-specific
> config file.

Is x11 backend working for you (e.g. in qemux86-64)?

I'm testing it with core-image-weston and modified mesa (to allow
llvmpipe) and with -Bx11-backend.so added to /etc/init.d/weston:

root@qemux86-64:~# /etc/init.d/weston start
Date: 2013-06-05 UTC
[13:47:50.300] weston 1.1.0
               http://wayland.freedesktop.org/
               Bug reports to:
https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.1.0
               Build:  
[13:47:50.308] OS: Linux, 3.8.13-yocto-standard, #1 SMP PREEMPT Tue Jun
4 22:29:53 CEST 2013, x86_64
[13:47:50.311] Loading module '/usr/lib/weston/x11-backend.so'
[13:47:50.317] initializing x11 backend
[13:47:50.318] fatal: failed to create compositor

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-06-05 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 14:00 [PATCH 0/4] Mesa and Wayland updates Ross Burton
2013-05-30 14:00 ` [PATCH 1/4] mesa: upgrade to 9.1.2 Ross Burton
2013-05-30 14:03   ` Jonathan Liu
2013-05-30 14:06   ` Jonathan Liu
2013-05-30 14:27     ` Burton, Ross
2013-05-30 14:00 ` [PATCH 2/4] wayland: update to 1.1.0 Ross Burton
2013-05-30 14:00 ` [PATCH 3/4] weston-init: basic init script to start Weston on KMS/DRM Ross Burton
2013-05-30 14:00 ` [PATCH 4/4] core-image-weston: basic image that boots directly to Weston Ross Burton
2013-05-31  7:18 ` [PATCH 0/4] Mesa and Wayland updates Koen Kooi
2013-05-31  9:30   ` Burton, Ross
2013-05-31  9:52     ` Burton, Ross
2013-06-05 13:51       ` Martin Jansa [this message]

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=20130605135102.GG30727@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.