public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Engraf <david.engraf@netcom.eu>
To: Greg KH <gregkh@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] USB BIOS early handoff only when the we the driver is configured
Date: Thu, 02 Aug 2007 09:07:24 +0200	[thread overview]
Message-ID: <46B182AC.3080809@netcom.eu> (raw)
In-Reply-To: <20070801202347.GC11551@suse.de>



Greg KH schrieb:
> On Wed, Aug 01, 2007 at 09:21:12AM +0200, David Engraf wrote:
>   
>> At the moment I have a Jetway/VIA Mainboard which seems to have a
>> problem with the handoff.
>> Evenwhen I wait about 20 seconds the EHCI_USBLEGSUP_BIOS flag is not
>> cleared. I think this is a BIOS
>> bug and I will have to talk to Jetway/VIA.
>>     
>
> This sounds like a BIOS bug.
>   
I think so too and I have to talk to Jetway/VIA what there is going wrong.
>   
>> On the other hand, I don't need the EHCI controller in my kernel, so I
>> think the kernel shouldn't take the
>> handover for the EHCI controller like other OS which do not have an usb
>> driver and so don't know that
>> there is a EHCI_USBLEGSUP_BIOS flag which should be cleared.
>>     
>
> We need to do this early to handle a wide range of machines that do very
> nasty things if we do not grab the device as early as possible.  Even if
> we do not ever get around to loading that usb driver.
>
> Yeah, hardware sucks at times :(
>
>   
Ok, but when we don't habe the driver for the usb controller, I think
the BIOS should control it because
maybe the BIOS found for example a keyboard or mouse and emulates it as
an PS2 keayboard/mouse,
so we could use it without the usb driver. I think that's why they
developed the handoff feature.
Are there any known hardware which has problems when we disable the handoff?

> thanks,
>
> greg k-h
>   

Thanks

 
David Engraf

 

 
Netcom Sicherheitstechnik GmbH
Rheinallee 189
55120 Mainz
Tel: 	+49 6131 6305 0
Fax: 	+49 6131 6305 40
Email: 	david.engraf@netcom.eu

 
Sitz der Gesellschaft: Mainz
Registergericht: Amtsgericht Mainz, 14HRB3411
Geschäftsführer: Peter Otto


  reply	other threads:[~2007-08-02  7:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31  8:31 [PATCH] USB BIOS early handoff only when the we the driver is configured David Engraf
2007-07-31 15:04 ` [linux-usb-devel] " Alan Stern
     [not found]   ` <46B03078.5040305@netcom.eu>
2007-08-01  7:21     ` David Engraf
2007-08-01 20:23       ` Greg KH
2007-08-02  7:07         ` David Engraf [this message]
2007-08-01 14:40     ` Alan Stern
2007-08-02  7:14       ` David Engraf
2007-08-02 14:32         ` Alan Stern
2007-08-02 16:43           ` Greg KH
2007-08-03  6:52             ` David Engraf
2007-08-03 15:03               ` Alan Stern
2007-08-07  8:44                 ` David Engraf
2007-08-07 14:37                   ` Alan Stern
2007-08-03 22:24             ` Grant Grundler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B182AC.3080809@netcom.eu \
    --to=david.engraf@netcom.eu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox