From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206427] go7007 driver fails to handle interrupt
Date: Thu, 06 Feb 2020 10:00:08 +0000 [thread overview]
Message-ID: <bug-206427-208809-k8IbFZcbBS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206427-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206427
--- Comment #9 from Josef Möllers (josef.moellers@suse.com) ---
Created attachment 287159
--> https://bugzilla.kernel.org/attachment.cgi?id=287159&action=edit
lsusb -v output of device, dmesg and hwinfo
This is slightly different from what I remember:
In Ye Olde Days, the device would present itself as 093b:a002 and (through a
udev rule), a script would be run which downloaded the firmware (through
/sbin/fxload some hex file) to the device which would then disconnect and
reconnect as 093b:a102.
Now I see in the journal that this is now handled by go7007-loader.ko loading
/lib/firmware/go7007/px-m402u.fw!
Anyways ... infos attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-06 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 12:24 [Bug 206427] New: go7007 driver fails to handle interrupt bugzilla-daemon
2020-02-05 12:29 ` Greg KH
2020-02-05 12:29 ` [Bug 206427] " bugzilla-daemon
2020-02-05 13:45 ` bugzilla-daemon
2020-02-05 13:57 ` bugzilla-daemon
2020-02-05 15:43 ` bugzilla-daemon
2020-02-06 9:27 ` bugzilla-daemon
2020-02-06 9:33 ` bugzilla-daemon
2020-02-06 10:00 ` bugzilla-daemon [this message]
2020-02-06 15:34 ` bugzilla-daemon
2020-02-06 15:43 ` 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-206427-208809-k8IbFZcbBS@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.