From: Dave Airlie
Since module loading was happening under the BKL, and the drm open path took
the BKL you couldn't race between them. The drm adds the sysfs node before it
really probably should, i.e. before driver load has completed. Then udev
creates the device node, and plymouth opens the dev
On Tuesday 14 September 2010, Dave Airlie wrote:
> Since module loading was happening under the BKL, and the drm open path took
> the BKL you couldn't race between them. The drm adds the sysfs node before it
> really probably should, i.e. before driver load has completed. Then udev
> creates the de
On Tuesday 14 September 2010, Dave Airlie wrote:
> Since module loading was happening under the BKL, and the drm open path took
> the BKL you couldn't race between them. The drm adds the sysfs node before it
> really probably should, i.e. before driver load has completed. Then udev
> creates the de
From: Dave Airlie
Since module loading was happening under the BKL, and the drm open path took
the BKL you couldn't race between them. The drm adds the sysfs node before it
really probably should, i.e. before driver load has completed. Then udev
creates the device node, and plymouth opens the dev
