Hi,
On Sun, Jan 25, 2009 at 12:28:37PM +0200, Pekka Paalanen wrote:
Consider a case where user space is stalled due to excessive load, and
let's think about usability. Much of usability comes from feedback
given to a user.
If cursor updates are done completely inside the kernel, the mouse
On Sunday, January 25, 2009 2:28 am Pekka Paalanen wrote:
On Mon, 5 Jan 2009 18:55:50 -0200
Tiago Vignatti vigna...@c3sl.ufpr.br wrote:
Hi guys,
Under KMS, we can build a feature to update the cursor directly to screen
without the continuous intervention of the userspace application (X
On Mon, 5 Jan 2009 18:55:50 -0200
Tiago Vignatti vigna...@c3sl.ufpr.br wrote:
Hi guys,
Under KMS, we can build a feature to update the cursor directly to screen
without the continuous intervention of the userspace application (X server,
wayland, etc). It's a fastpath for DRM based cursors
Hi,
On Mon, Jan 05, 2009 at 06:55:50PM -0200, Tiago Vignatti wrote:
Under KMS, we can build a feature to update the cursor directly to
screen without the continuous intervention of the userspace
application (X server, wayland, etc). It's a fastpath for DRM based
cursors obtained by
On Mon, 2009-01-19 at 10:03 -0800, Jesse Barnes wrote:
On Friday, January 16, 2009 1:55 pm Rémi Cardona wrote:
Le 16/01/2009 21:21, Jesse Barnes a écrit :
On Monday, January 5, 2009 12:55 pm Tiago Vignatti wrote:
Right now a thing that is annoying me is how others cursors, sw
On Tue, Jan 20, 2009 at 12:47:44AM +0100, Rémi Cardona wrote:
Le 19/01/2009 19:03, Jesse Barnes a écrit :
Gah, yeah forgot about drag drop of big icons... Maybe Kristian was right
that all cursors should be done in software; hardware just doesn't provide
the flexibility desktops want
Le 19/01/2009 19:03, Jesse Barnes a écrit :
Gah, yeah forgot about drag drop of big icons... Maybe Kristian was right
that all cursors should be done in software; hardware just doesn't provide
the flexibility desktops want these days.
Maybe there could be a way to prioritize input events
Le 16/01/2009 21:21, Jesse Barnes a écrit :
On Monday, January 5, 2009 12:55 pm Tiago Vignatti wrote:
Right now a thing that is annoying me is how others cursors, sw rendered,
could be implemented. I want to avoid two differents sets of the same code
in different contexts. IMHO conceptually
Hi guys,
Under KMS, we can build a feature to update the cursor directly to screen
without the continuous intervention of the userspace application (X server,
wayland, etc). It's a fastpath for DRM based cursors obtained by short-circuit
the kernel input layer and DRM module. This would solve all
