Ingo Molnar wrote:
* Linus Torvalds wrote:
Two choices that I can see:
- do the ieee1394_init() as a fs_initcall(), earlier
- move drivers/ieee1394 linking up to before drivers/media
but I suspect that drivers/media wants to be early, in order to do the
_media_ layer initialization early.
* Linus Torvalds wrote:
> Two choices that I can see:
>
> - do the ieee1394_init() as a fs_initcall(), earlier
>
> - move drivers/ieee1394 linking up to before drivers/media
>
> but I suspect that drivers/media wants to be early, in order to do the
> _media_ layer initialization early.
>
On Thu, 26 Feb 2009, Stefan Richter wrote:
>
> Alas I have no Linux box at hand before Saturday. I wonder, was
> ieee1394_bus_type not yet registered (i.e. ieee1394's ieee1394_init() not yet
> called) at the moment when fdtv_init is executed?
>
> Or what else could have been the NULL pointer d
Ingo Molnar wrote:
[ 13.756029] calling fdtv_init+0x0/0xf @ 1
[ 13.760074] BUG: unable to handle kernel NULL pointer dereference at 0054
[ 13.764023] IP: [] driver_find+0xf/0x24
[ 13.764023] *pde =
[ 13.764023] Oops: [#1] SMP
[ 13.764023] last sysfs file:
[ 13.
Linus,
if you don't mind receiving yet another new driver this late in the
game, then please pull from the firedtv-merge branch at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6.git
firedtv-merge
to receive the following IEEE 1394 + DVB updates. More information
after
