From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262029AbUEANVe (ORCPT ); Sat, 1 May 2004 09:21:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262101AbUEANVe (ORCPT ); Sat, 1 May 2004 09:21:34 -0400 Received: from mail-ext.curl.com ([66.228.88.132]:46599 "HELO mail-ext.curl.com") by vger.kernel.org with SMTP id S262029AbUEANVd (ORCPT ); Sat, 1 May 2004 09:21:33 -0400 From: "Patrick J. LoPresti" Message-ID: To: linux-kernel@vger.kernel.org Subject: Re: Load hid.o module synchronously? References: <408D65A7.7060207@nortelnetworks.com> Date: 01 May 2004 09:21:31 -0400 In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Bill Davidsen writes: > Patrick J. LoPresti wrote: > > > I see how I can scan for a USB keyboard after loading the USB host > > controller module. I think. But what do I look for, exactly, to > > tell when hid.o has hooked itself up to the keyboard? > > You need to be able to tell "not hooked yet" from "never saw it" for > reliable operation. I don't know how to do that, sorry. So there is no way to load this hardware driver and wait until it either binds or fails to bind to its associated hardware? That seems like a bad bug in the design... I suppose I will just use some arbitrary delay. - Pat