boot from usb flash - wake boot process when disk is ready?

From: David N. Welton (davidw_at_eidetix.com)
Date: 05/28/04

  • Next message: Ingo Molnar: "Re: [RFC][PATCH][2.6.6] Replacing CPU scheduler active and expired with a single array" 
    Date:	Fri, 28 May 2004 11:05:54 +0200
To: linux-kernel@vger.kernel.org

    [ Please CC replies to me - thanks! ]

    Hi,

    We're toying around with the idea of booting an embedded system off of
    USB flash (pros, cons, and advice about this would be appreciated, by
    the way), and I had a look at several of the existing patches to do this
    without going through the process of creating an initrd image. That
    adds complexity and time to the boot process that we would prefer to
    avoid, although it appears that the kernel folks in the first thread
    cited are in favor of initrd....

    http://www.uwsg.iu.edu/hypermail/linux/kernel/0301.3/1182.html

    This mentions a couple of patches, both the "keep looping until it
    works" one, which I couldn't get working with 2.6.6, and Willy Tarreu's
    "wait a given period of time before continuing" patch:

    http://www.uwsg.iu.edu/hypermail/linux/kernel/0405.0/0224.html

    I don't think either of those approaches are particularly elegant...
    although I'm sure my own efforts are good for a snort as well.

    In genhd.c I wake up a waitqueue when the disk comes on line. The
    init process waits on this before going on with prepare_namespace().
    Ideally, this would look and make sure it's the right disk, that
    selected for the root fs:-) Not being very familiar with the 'lay of
    the land' in the kernel, I declared the wait queue as a global in
    genhd.c. The thing I don't like about this approach is that it builds a
    connection between two bits of the kernel that seem separate... maybe
    (ok, quite probably) there is a better/cleaner way of doing this?

    Patch is at: http://dedasys.com/freesoftware/files/usb-wakeup.patch

    Thanks for comments/constructive criticism, and thanks for reading, 

    -- 
David N. Welton
davidw@eidetix.com
-
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/
  • Next message: Ingo Molnar: "Re: [RFC][PATCH][2.6.6] Replacing CPU scheduler active and expired with a single array"

    Relevant Pages

    • Re: Granting some root permissions to certain users
      ... We use a kernel patch called trustees to do just what you're talking ... Unfortunately the patch hasn't really been kept up-to-date. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: RT-V0.7.47-17 build fails
      ... On Monday 06 June 2005 03:41, Ingo Molnar wrote: ... >> I thought maybe I'd exersize this kernel, but a patch I thought ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata
      ... to avoid so we can get this in to the 2.6 kernel ASAP. ... I am pretty certain the patch won't impact the ... > might want to kill the condition depending on the stepping, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.3-rc1-mm1
      ... > This is the first time that anyone told me that it even existed. ... When we're at kernel version 2.6.3! ... without this patch. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Question re the dot releases such as 2.6.12.3
      ... I'll submit a patch to the ... > kernel from the home page. ... Copyright 2005 by Maurice Eugene Heskett, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)