On 12 February 2013 15:52, Ander Conselvan de Oliveira <[email protected]> wrote: > Input device initialization takes several microseconds to complete. Two > things causes this: compiling the XKB keymap and reading the properties > database from the udev daemon. The user can't really interact with > anything on the screen until something is displayed, so this can be > delayed. > > On my system, this patch saves ~50ms from launching Weston to have the > first frame displayed.
Hey Ander, I like the idea of this :-) However can I raise the concern that although you're going to be starting weston fast - and getting to that first frame fast!. Won't we then miss the opportunity to do the next 3 frames on the vblank - since we'll be be blocked doing the device setup. Can we be clever about this and split the device setup into some separate blocks of idle code so that we never block for that solid period? e.g. xkbcommon compilation (could we even cache this compiled data?) in one idle, udev interaction in another. Cheerio, Rob _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
