All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 213839] XHCI 7 port usb hub does not work correctly
Date: Sat, 24 Jul 2021 14:45:09 +0000	[thread overview]
Message-ID: <bug-213839-208809-oZJiilxOsf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213839-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=213839

--- Comment #2 from tomas m (tmezzadra@gmail.com) ---
(In reply to Alan Stern from comment #1)
> This could easily be a power issue.  Does either the 7-port hub or the
> device you plug into it have its own power source?

I measured the 5v on both chips and its 5v sharp.

Soldered an additional cap to its vcc too.

Its the same vcc source.

Like i said. Under windows it works

It is being powered by the usb port.

I will test an external suppy just to be safe and report

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-07-24 14:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 13:41 [Bug 213839] New: XHCI 7 port usb hub does not work correctly bugzilla-daemon
2021-07-24 14:30 ` [Bug 213839] " bugzilla-daemon
2021-07-24 14:45 ` bugzilla-daemon [this message]
2021-07-24 15:45 ` bugzilla-daemon
2021-09-15 22:46 ` bugzilla-daemon
2021-12-30 14:30 ` bugzilla-daemon
2021-12-31 16:32 ` bugzilla-daemon
2021-12-31 16:32 ` bugzilla-daemon
2021-12-31 16:35 ` bugzilla-daemon
2022-01-01  1:49 ` bugzilla-daemon
2022-01-01 10:36 ` bugzilla-daemon
2022-01-01 10:37 ` bugzilla-daemon
2022-01-01 10:38 ` bugzilla-daemon
2022-01-01 10:39 ` bugzilla-daemon
2022-01-01 16:26 ` bugzilla-daemon
2022-01-01 18:46 ` bugzilla-daemon
2022-01-01 18:51 ` bugzilla-daemon
2022-01-01 19:53 ` bugzilla-daemon

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=bug-213839-208809-oZJiilxOsf@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.