From: David Brownell <david-b@pacbell.net>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-usb-devel@lists.sourceforge.net,
Paul Mackerras <paulus@samba.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: Commit "[PATCH] USB: Always do usb-handoff" breaks my powerbook
Date: Mon, 31 Oct 2005 20:39:46 -0800 [thread overview]
Message-ID: <200510312039.46646.david-b@pacbell.net> (raw)
In-Reply-To: <BC88D0A1-453F-4716-96E6-3C89B915C477@mac.com>
> Why should x86-specific-BIOS-USB-handoff-specific-crap-PCI-quirks be
> even _compiled_ on PowerPC systems that have nothing remotely like
> the affected hardware (BIOS & PS/2 serio chip)?
For starters, none of the controller specs say that the handshaking
is x86-specific. There's a certain amount of "x86 Linux gets the
most testing" going on here. Plus a lot of "nobody really used that
usb-handoff code before, except to fix semi-broken x86 systems".
One requirement coming from x86/DOS legacy support though is that the
system probably expects to "work like DOS" at various boot stages.
Hence the way some systems take kbd/mouse input from USB and jam it
through PS2 serio hardware, so DOS will see it. Which is why x86
hardware generally _does_ need to use these handhaking mechanisms,
to kick the BIOS off the hardware. (And why the USB folk have been
very used to telling folk to disable BIOS support for USB. That's
fine advice unless you've got a USB keyboard or mouse.)
> The difference is, OpenFirmware is nice and clean and stops messing
> with hardware before handing off to the new kernel.
That's a nice design policy (IMO) but sometimes folk also like to
draw the firmware/OS boundary in different ways.
In any case ... let's all just blame this on DOS, and move on to
something that's not as twentieth-century. :)
- Dave
next prev parent reply other threads:[~2005-11-01 4:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 5:23 Commit "[PATCH] USB: Always do usb-handoff" breaks my powerbook Paul Mackerras
2005-11-01 0:16 ` Benjamin Herrenschmidt
2005-11-01 1:41 ` [linux-usb-devel] " David Brownell
2005-11-01 2:41 ` Benjamin Herrenschmidt
2005-11-01 3:09 ` David Brownell
2005-11-01 3:30 ` Benjamin Herrenschmidt
2005-11-01 4:17 ` David Brownell
2005-11-01 4:52 ` Paul Mackerras
2005-11-01 5:08 ` Benjamin Herrenschmidt
2005-11-01 9:28 ` Alan Cox
2005-11-01 13:40 ` Glenn Maynard
2005-11-01 21:09 ` Benjamin Herrenschmidt
2005-11-01 3:39 ` Dmitry Torokhov
2005-11-01 4:06 ` Kyle Moffett
2005-11-01 4:39 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 4:21 Aleksey Gorelov
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=200510312039.46646.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mrmacman_g4@mac.com \
--cc=paulus@samba.org \
--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