public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	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:17:39 -0800	[thread overview]
Message-ID: <200510312017.39915.david-b@pacbell.net> (raw)
In-Reply-To: <1130815836.29054.420.camel@gaston>


> > > "ppc" doens't do anything fancy that other archs don't do too, please
> > > stop with your "ppc specific" thing all over the place.
> > 
> > When the only problem reports come from PPC hardware, it sure looks
> > PPC-specific to me.
> 
> Bla bla bla bla... can you stop the crackpipe please ?

Maybe you should first pay attention to what I pointed out:  that
the problem reports I've seen have ONLY been on PPC systems.

Like the powerbook in $SUBJECT ... people without PPCs are unlikely
to hit such issues, judging by the evidence so far.  (Though of course
it'd be possible...)


> >                   If such issues get reported on non-PPC hardware
> > (with those unique-to-ppc changes to PCI enumeration) then I'll stop
> > thinking of it as PPC-specific.  Until then ... ;)


I guess one point to be made is that although x86 gets the most testing
right away, PPC lately isn't far behind.  Latent bugs in usb-handoff
logic got surfaced by this patch ... there could be others.  I suspect
nobody except x86 users have been running that code much at all.

- Dave


  reply	other threads:[~2005-11-01  4:17 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 [this message]
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
  -- 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=200510312017.39915.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=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