[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <49A7A25A.9050601@s5r6.in-berlin.de>
Date: Fri, 27 Feb 2009 09:20:42 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Ingo Molnar <mingo@...e.hu>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
linux1394-devel@...ts.sourceforge.net, linux-media@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Ben Backx <ben@...ckx.com>, Henrik Kurelid <henrik@...elid.se>
Subject: Re: [git pull] DVB + ieee1394: firedtv driver
Ingo Molnar wrote:
> * Linus Torvalds <torvalds@...ux-foundation.org> 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.
The former seems the better choice to me. Changing the linking order
would just break the next time around.
>> Does this work?
>
> yes, i just tested it and your patch fixes the crash:
>
> mercury:~> uname -a
> Linux mercury 2.6.29-rc6-tip-02011-gb62a1ed-dirty #250 SMP Thu
> Feb 26 19:00:54 CET 2009 i686 athlon i386 GNU/Linux
> mercury:~> uptime
> 19:02:51 up 0 min, 1 user, load average: 3.97, 1.10, 0.37
>
> Tested-by: Ingo Molnar <mingo@...e.hu>
Thanks guys. I'm very sorry that this basic issue escaped my attention.
It's the first time that a 1394 driver lives outside
drivers/ieee1394/Makefile.
(Also shows that even very long exposure in linux-next does not catch
runtime issues like this one.)
Stefan Richter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists