From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Brownell <david-b@pacbell.net>,
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: Tue, 01 Nov 2005 09:28:14 +0000 [thread overview]
Message-ID: <1130837294.9145.80.camel@localhost.localdomain> (raw)
In-Reply-To: <1130815836.29054.420.camel@gaston>
On Maw, 2005-11-01 at 14:30 +1100, Benjamin Herrenschmidt wrote:
> Damn, those quirks should really be either more careful or be made
> platform specific if they are x86 junk workarounds.
USB handoff is fairly x86 specific. The x86 folks took great care to
handle back compatibility while Apple was content to just dump the users
and machines.
> > > It is illegal, whatever the platform is, to tap a PCI device MMIO like
Not "illegal" -> "invalid".
Please get that right as we have far too many incorrect uses of
"illegal" in publically visible printk calls. Illegal means "prohibited
by law".
next prev parent reply other threads:[~2005-11-01 8:59 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 [this message]
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
-- 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=1130837294.9145.80.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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