linux-kernel - Re: [PATCH] [MMC] Use own work queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <453B385A.60901@drzeus.cx>
Date:	Sun, 22 Oct 2006 11:22:34 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	pHilipp Zabel <philipp.zabel@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [MMC] Use own work queue

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/