Prev: ERROR 'syntax error' at token 'typeattribute'
Next: [PATCH 5/5] VFS: DazukoFS, stackable-fs, file access control
From: Nicolas Ferre on 2 Dec 2008 12:30
Guennadi Liakhovetski :
> Another problem I encountered with my framebuffer is the initialisation
> order. You initialise dmaengine per subsys_initcall(), whereas the only
> way to guarantee the order:
> dma-device driver
> when they are all linked into the kernel was to switch dmaengine to
> arch_initcall, put the dma driver under subsys_initcall, and the
> framebuffer under a normal module_init / device_initcall.
I did not dig much in this but I feel also that dmaengine is initialized
a bit late : it seems to be initialized after atmel-mci is started.
It works but it seems to me that dmaengine has to be initialized very
....my 2 cents.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/