mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	nut-upsuser@lists.alioth.debian.org, bruce.w.allan@intel.com,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']
Date: Sun, 1 Nov 2009 16:49:40 -0800	[thread overview]
Message-ID: <20091102004940.GD24436@one-eyed-alien.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0911011613270.2767@p34.internal.lan>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

On Sun, Nov 01, 2009 at 04:18:40PM -0500, Justin Piszcz wrote:
> 
> I do not use any hubs in this environment, everything is directly 
> attached to the motheboard.  Per Matthew (noted below) when I
> mention hub I am talking about your typical USB hub one would
> attach to a USB port on the board, not the integrated one on the
> motherboard.  Everything is directly attached from the motherboard
> to each respective device.
> 
> MOBO -> UPS
> MOBO -> KBD
> MOBO -> etc

Just to be clear, the hub isn't "on the motherboard".  It's actually in the
P55 silicon itself.  It's not a separate chip or anything; it's part of the
PCH design.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

You are needink to look more evil.  You likink very strong coffee?
					-- Pitr to Dust Puppy
User Friendly, 10/16/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2009-11-02  0:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 14:58 2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue? Justin Piszcz
2009-10-31 11:59 ` 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS'] Justin Piszcz
2009-10-31 15:18   ` Alan Stern
2009-10-31 23:43     ` Justin Piszcz
2009-11-01  0:07       ` Arjan van de Ven
2009-11-01  8:55         ` Justin Piszcz
2009-11-01 17:11       ` Alan Stern
2009-11-01 17:52         ` Matthew Dharm
2009-11-01 21:18           ` Justin Piszcz
2009-11-01 21:25             ` Justin Piszcz
2009-11-02  0:49             ` Matthew Dharm [this message]
2009-11-02 13:43               ` Henrique de Moraes Holschuh

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=20091102004940.GD24436@one-eyed-alien.net \
    --to=mdharm-kernel@one-eyed-alien.net \
    --cc=ap@solarrain.com \
    --cc=bruce.w.allan@intel.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nut-upsuser@lists.alioth.debian.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

all inboxes | Powered by JetHome®