[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1210041628400.9942@pobox.suse.cz>
Date: Thu, 4 Oct 2012 16:36:20 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Greg KH <gregkh@...uxfoundation.org>, Kay Sievers <kay@...y.org>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Lennart Poettering <lennart@...ttering.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kay Sievers <kay@...hat.com>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Michael Krufky <mkrufky@...uxtv.org>
Subject: Re: udev breakages - was: Re: Need of an ".async_probe()" type of
callback at driver's core - Was: Re: [PATCH] [media] drxk: change it to use
request_firmware_nowait()
On Tue, 2 Oct 2012, Linus Torvalds wrote:
> Now, at the same time, I do agree that network devices should generally
> try to delay it until ifup time
Slightly tangential to the ongoing discussion, but still ... I think that
even "all network drivers should delay firmware loading to ifup time"
might be too general.
I would expect that there are network cards which require firmware to be
present for PHY to work, right? On such cards, if you want to have link
detection even on interfaces that are down (so that things like ifplugd
can detect the link presence and configure the interface), ifup is too
late.
I admit I haven't checked whether there actually are such cards out there,
but it doesn't seem to be completely unrealistic to me.
--
Jiri Kosina
SUSE Labs
--
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