diff options
| author | Marcin Slusarz <marcin.slusarz@gmail.com> | 2010-05-16 19:29:56 +0400 |
|---|---|---|
| committer | Dave Airlie <airlied@redhat.com> | 2010-05-18 10:19:28 +0400 |
| commit | 06415c564fb98562a4d6b6215615deb2d1cc0dae (patch) | |
| tree | 93982221251bc68eb292a07da72220a0c90d94f0 /fs/xattr.c | |
| parent | 1471ca9aa71cd37b6a7476bb6f06a3a8622ea1bd (diff) | |
| download | linux-06415c564fb98562a4d6b6215615deb2d1cc0dae.tar.xz | |
fbmem, drm/nouveau: kick firmware framebuffers as soon as possible
Currently vesafb/efifb/... is kicked when hardware driver is registering
framebuffer. To do it hardware must be fully functional, so there's a short
window between start of initialisation and framebuffer registration when
two drivers touch the hardware. Unfortunately sometimes it breaks nouveau
initialisation.
Fix it by kicking firmware driver(s) before we start touching the hardware.
Reported-by: Didier Spaier <didier.spaier@epsm.fr>
Tested-by: Didier Spaier <didier.spaier@epsm.fr>
Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Ben Skeggs <bskeggs@redhat.com>
Cc: Peter Jones <pjones@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'fs/xattr.c')
0 files changed, 0 insertions, 0 deletions