Message-ID: <453B385A.60901@drzeus.cx>
Date: Sun, 22 Oct 2006 11:22:34 +0200
From: Pierre Ossman <drzeus-list@drzeus.cx>
User-Agent: Thunderbird 1.5.0.7 (X11/20061008)
MIME-Version: 1.0
To: pHilipp Zabel <philipp.zabel@gmail.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Use own work queue
References: <20061001124240.16996.34557.stgit@poseidon.drzeus.cx>	 <74d0deb30610070717k17079940ybedbf94dc8af8460@mail.gmail.com>	 <452AB97B.5040309@drzeus.cx>	 <20061013075626.GB28654@flint.arm.linux.org.uk> <74d0deb30610150240y16d6ea92mc96705576b8f0824@mail.gmail.com>
In-Reply-To: <74d0deb30610150240y16d6ea92mc96705576b8f0824@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 925
Lines: 25

pHilipp Zabel wrote:
> 
> Thanks, I can work around this by using the rootdelay kernel parameter.
> So does that mean this is the expected behavior, or should I do anything
> in the bootup sequence to make the init process wait for mmc detection?
> 

USB, which has an almost identical problem, usually uses a "sleep" in
initrd.

If you want to be a bit more fancy, you could try to listen to hotplug
events and look for the kernel creating the relevant block device.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org
-
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/