From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264246AbUEDUDP (ORCPT ); Tue, 4 May 2004 16:03:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264500AbUEDUDP (ORCPT ); Tue, 4 May 2004 16:03:15 -0400 Received: from mail.kroah.org ([65.200.24.183]:24501 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S264246AbUEDUDM (ORCPT ); Tue, 4 May 2004 16:03:12 -0400 Date: Tue, 4 May 2004 13:01:47 -0700 From: Greg KH To: "Patrick J. LoPresti" Cc: linux-kernel@vger.kernel.org Subject: Re: Load hid.o module synchronously? Message-ID: <20040504200147.GA26579@kroah.com> References: <408D65A7.7060207@nortelnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, May 01, 2004 at 09:21:31AM -0400, Patrick J. LoPresti wrote: > 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... Um, what is wrong with the proposals I made for how you can detect this? greg k-h