Date: Sat, 3 Oct 2009 09:45:02 -0600 From: Scott Long <scottl@samsco.org> To: Scott Long <scottl@samsco.org> Cc: freebsd-current@freebsd.org, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: [PATCH] Fix for USB media not found at boot Message-ID: <3D59CB10-7589-41F7-A00F-73224F16C6A7@samsco.org> In-Reply-To: <F22AB1E4-C293-4825-89BB-9863606F2C60@samsco.org> References: <20091002150931.K35591@pooker.samsco.org> <200910030953.17359.hselasky@c2i.net> <3307DF7C-2FEF-468B-85F4-095BB7E3EE8F@samsco.org> <200910031230.51044.hselasky@c2i.net> <F22AB1E4-C293-4825-89BB-9863606F2C60@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 3, 2009, at 9:05 AM, Scott Long wrote: > On Oct 3, 2009, at 4:30 AM, Hans Petter Selasky wrote: >> On Saturday 03 October 2009 10:19:57 Scott Long wrote: >>> config_intrhook system will sleep after all >> >> Then why do you need the intr hook callback? >> > > The config_intrhook lets you know that interrupts are enabled, the > scheduler is running, and mountroot hasn't run yet. It provides a > very convenient and standard way to do exactly what we want with USB > enumeration. > Now that I'm awake, let me explain more. I'm moving USB from the mount_root_hold() API to the config_intrhook() API because the latter provides proper boot ordering with CAM, which the former does not. Though my published patch doesn't rely on the CAM system in order to function, if you want umass devices to be discovered in time, you need it. What I didn't realize when I published my patch is that my approach is incomplete; I'm working to fix that, but it will likely require some significant work inside of USB. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D59CB10-7589-41F7-A00F-73224F16C6A7>