mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: "Aleksey Gorelov" <Aleksey_Gorelov@Phoenix.com>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Pete Zaitcev" <zaitcev@redhat.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] RE: [PATCH] Early USB handoff
Date: Thu, 2 Sep 2004 16:44:51 -0700	[thread overview]
Message-ID: <200409021644.51961.david-b@pacbell.net> (raw)
In-Reply-To: <5F106036E3D97448B673ED7AA8B2B6B3016ADED2@scl-exch2k.phoenix.com>

On Thursday 02 September 2004 1:26 pm, Aleksey Gorelov wrote:

>   While still in real mode, BIOS takes care of interrupts from 
> devices. But once OS takes control over and goes to protected 
> mode, there is no easy way for BIOS to detect that and disable HC.

I find myself a bit unsettled at the notion of not really being
able to blame this behavior on BIOS bugs.  What's the world
coming to any more?!


> So, one should either avoid 'sharing' it with other devices (at
> IRQ routing stage), or reprogram HC in native OS mode first (at 
> least disable interrupts).

That sounds like it could explain lots of the init/irq problems we've
had on various systems.  Makes me a lot more interested in seeing
this fix go in ... :)

For backwards compatibility, the early reset should not be the
default.  There aren't many systems where it's a problem.

- Dave

      reply	other threads:[~2004-09-03  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 20:26 Aleksey Gorelov
2004-09-02 23:44 ` David Brownell [this message]

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=200409021644.51961.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Aleksey_Gorelov@Phoenix.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=zaitcev@redhat.com \
    /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

Powered by JetHome