[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-10 Thread Oliver Grawert
pitti pointed on IRC to https://android.googlesource.com/kernel/msm/+/57195292 ... which doesnt help for our driver, but the problem does not seem to be uniqe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-10 Thread Oliver Grawert
adjusting bug description, this is sadly a constant condition, not related to movie playback ** Summary changed: - omapfb module floods system with udev events on samsung galaxy nexus when playing mp4 + omapfb module floods system with udev events on samsung galaxy nexus -- You received this

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-09 Thread Ricardo Salveti
We can't disable VSYNC uevent, it's required by the driver. All we can do is to ignore it later on upper layers, such as upstart. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-09 Thread Steve Langasek
So upstart's udev bridge needs to have a capability of filtering events. Adding an upstart upstream task ** Also affects: upstart Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-08 Thread Launchpad Bug Tracker
** Branch linked: lp:~xnox/upstart/workaround-1234743 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-07 Thread Launchpad Bug Tracker
This bug was fixed in the package powerd - 0.13+13.10.20131007.1-0ubuntu1 --- powerd (0.13+13.10.20131007.1-0ubuntu1) saucy; urgency=low [ Seth Forshee ] * Don't reset the activity timer for touch events if the screen is of (LP: #1234743). (LP: #1234743) [ Ubuntu daily

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-05 Thread Colin King
Enabling Mir with VSYNC disabled in the omapfb driver leaves me in a state with just a blank screen. I can login via adb shell, so I need to debug this a bit deeper. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-04 Thread Colin King
Thanks James, I will look into what the driver is doing. ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Colin King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-04 Thread Colin King
After some digging I've found the following: 1. commit a4e449e8a08e727b8160cb4e4a0367c447148d2f enables drivers/video/omap2/omapfb/omapfb-main.c to send VSYNC uevents on each vsync. 2. hwcomposer.omap4.so handles this VSYNC event, and inspecting /proc/$pid/maps it appears this is used by

[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4

2013-10-04 Thread Steve Langasek
I suppose this is a driver that would still be in the picture when switching to Mir, and we can't hope to avoid the issue by changing display servers? You could test this by following the directions at https://wiki.ubuntu.com/Touch/Testing/Mir. -- You received this bug notification because you