All of lore.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>,
	Colin Leroy <colin.lkml@colino.net>,
	Colin Leroy <colin@colino.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [linux-usb-devel] [PATCH] Ohci-hcd: fix endless loop (second take)
Date: Mon, 29 Nov 2004 16:41:51 -0800	[thread overview]
Message-ID: <200411291641.51559.david-b@pacbell.net> (raw)
In-Reply-To: <1101768195.15463.20.camel@gaston>

On Monday 29 November 2004 2:43 pm, Benjamin Herrenschmidt wrote:
> On Mon, 2004-11-29 at 23:34 +0100, Colin Leroy wrote:
> 
> Ok, this is a perfectly normal "out of the schelves" NEC chip, no
> special "Mac" thing in there, it just use normal PCI PM...
> 
> It could be one of the devices not properly dealing with beeing
> suspended, or it could be some delay needing to be increased here or
> there in the resume process, difficult to say at this point.

Or as I said before, it's probably one of the issues fixed
in the USB PM patches in 2.6.10-rc2 ... really, it's not
even worth testing that with straight 2.6.9 kernels.  


  reply	other threads:[~2004-11-30  0:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26 10:30 [PATCH] Ohci-hcd: fix endless loop (second take) Colin Leroy
2004-11-26 17:28 ` [linux-usb-devel] " David Brownell
2004-11-26 17:37   ` Colin Leroy
2004-11-26 17:57     ` David Brownell
2004-11-26 22:12       ` Benjamin Herrenschmidt
2004-11-29  8:04         ` Colin Leroy
2004-11-29 22:26           ` Benjamin Herrenschmidt
2004-11-29 22:34             ` Colin Leroy
2004-11-29 22:43               ` Benjamin Herrenschmidt
2004-11-30  0:41                 ` David Brownell [this message]
2004-11-26 18:46   ` David Brownell

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=200411291641.51559.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=colin.lkml@colino.net \
    --cc=colin@colino.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.