All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Devin Hughes <devin@jd2.com>
Cc: meta-arago@arago-project.org, "'Cooper Jr., Franklin'" <fcooper@ti.com>
Subject: Re: Building meta-arago daisy
Date: Fri, 29 Aug 2014 12:45:37 -0400	[thread overview]
Message-ID: <20140829164537.GH18620@edge> (raw)
In-Reply-To: <000501cfc3a2$080ad680$18208380$@jd2.com>

On Fri, Aug 29, 2014 at 11:58:09AM -0400, Devin Hughes wrote:
> > > [Devin Hughes] Is the daisy configured build stable? I rebuilt the
> > > image yesterday after the servers returned and it seems to run
> > > unexpectedly. No boot errors, but the touchscreen and application
> > > performance seem worse than the SDK release.
> > [Franklin] Can you explain what you mean in terms of application
> performance
> > issues?
> [Devin Hughes] Performance was the wrong choice of words now that I know
> about
> the touchscreen trouble. It's more the permanent title bar and lack of
> screen updates after closing an application. For instance, after running one
> of the 3d demos in matrix gui, the title bar shows the last opengl rendering
> on the top of the lcd.  

3D demos don't talk to Wayland stack and they take over fbdev completely and 
previously Qt4-based refresh-screen app was used to update the screen 
afterwards.


> > I am going to build a customized image as a test next,
> > > and I was thinking arago-base from daisy would be a good starting
> > > point since I would like qt 5.2 or greater.
> > [Franklin] So by default we are using Wayland/Weston and for Qt 5 we are
> using
> > the Wayland compositor. However, there are several touch screen related
> bugs
> > in Weston and Qt 5 that we are working with the Qt 5 and Weston team to
> > address. It will take some time to fix so if acceptable I would recommend
> just
> > using a usb mouse as a work around for now if your running into those
> problems
> > also.
> [Devin Hughes] USB mouse would be fine for me, but libusb is failing to
> initialize. In
> dmesg I can see musb_init_controller failures, and the platform driver
> reports a deferred
> probe. The only similar information I can find on google describes
> improperly configured
> device tree sources, but the fixes are already included in the daisy
> referenced kernel.

Hmm, you said that is with 335x SK, right? I haven't seen this on BeagleBone 
Black or 335x EVM. I'll try to see if I can reproduce it with SK...

-- 
Denys


  reply	other threads:[~2014-08-29 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 13:37 Building meta-arago daisy Devin Hughes
2014-08-26 14:21 ` Denys Dmytriyenko
2014-08-29 14:40   ` Devin Hughes
2014-08-29 14:47     ` Cooper Jr., Franklin
2014-08-29 15:58       ` Devin Hughes
2014-08-29 16:45         ` Denys Dmytriyenko [this message]
2014-08-29 17:42           ` Devin Hughes

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=20140829164537.GH18620@edge \
    --to=denys@ti.com \
    --cc=devin@jd2.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.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 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.