Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269761AbUINT5y (ORCPT ); Tue, 14 Sep 2004 15:57:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269708AbUINTxn (ORCPT ); Tue, 14 Sep 2004 15:53:43 -0400 Received: from mail.kroah.org ([69.55.234.183]:35806 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S269760AbUINTx0 (ORCPT ); Tue, 14 Sep 2004 15:53:26 -0400 Date: Tue, 14 Sep 2004 12:52:21 -0700 From: Greg KH To: Chris Friesen Cc: "Giacomo A. Catenazzi" , linux-kernel@vger.kernel.org, Tigran Aivazian Subject: Re: udev is too slow creating devices Message-ID: <20040914195221.GA21691@kroah.com> References: <41473972.8010104@debian.org> <41474926.8050808@nortelnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41474926.8050808@nortelnetworks.com> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 813 Lines: 25 On Tue, Sep 14, 2004 at 01:40:22PM -0600, Chris Friesen wrote: > Giacomo A. Catenazzi wrote: > > >udev + modular microcode: > >$ modprobe -r microcode > >$ modprobe microcode ; microcode_ctl -u > >=> microcode_ctl does NOT find the device > > The loading of the module triggers udev to run. There is no guarantee that > udev runs before microcode_ctl. > > One workaround would be to have microcode_ctl use dnotify to get woken up > whenever /dev changes. Ick, no. Use the /etc/dev.d/ notify method I described. That is what it is there for. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/