From: Alan Stern <stern@rowland.harvard.edu>
To: ValdikSS <iam@valdikss.org.ru>
Cc: linux-usb@vger.kernel.org
Subject: Re: USB 1.1 Full Speed OHCI slow/high latency
Date: Fri, 15 Aug 2025 22:04:07 -0400 [thread overview]
Message-ID: <4e83d098-19e8-45aa-94e7-9ef005a0c8ab@rowland.harvard.edu> (raw)
In-Reply-To: <9013fce0-6764-49b1-9e54-68e915e12d7c@valdikss.org.ru>
On Fri, Aug 15, 2025 at 09:13:09PM +0300, ValdikSS wrote:
> I *buy* these legacy devices to improve them in Linux :)
>
> I'm making an open-source print server hardware for older printers, that's
> why for me this issue is worth researching, at least to document such
> hardware heisenbugs.
> There've been different USB behavior and incompatibilities with scanners
> (fixed it in SANE) and printers (fixed by CUPS quirks file), but this is the
> first time I'm going down to USB HC level.
>
> This printer (Canon LBP1120) does not have drivers for 64-bit Windows or
> recent macOS, that's why for many it's a paperweight device you can't use or
> sell, unless fixed by other means (usually a VM with 32-bit Windows, and now
> my print server as well).
>
> You gave me directions where I should look for, because I didn't know how to
> start debugging without the logic analyzer.
> Usbmon captures only USB communication packets and some of USB HUB
> controlling packets (such as TT related), but does not include
> device-controlling MMIO registers, which was the case here.
>
> I'll add debug prints to everything related to MMIO and take a look what
> could be improved. Thanks!
Good luck!
> If you have other ideas I could try right away, please share them!
You might compare the usbmon traces for your patched OHCI against a UHCI
system. They should run at approximately the same speed, so it's not
clear why the printer would work with one but not the other.
Alan Stern
next prev parent reply other threads:[~2025-08-16 2:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 1:56 USB 1.1 Full Speed OHCI slow/high latency ValdikSS
2025-08-14 6:01 ` Greg KH
2025-08-14 14:24 ` Alan Stern
2025-08-14 15:11 ` ValdikSS
2025-08-14 16:40 ` Alan Stern
2025-08-15 8:39 ` ValdikSS
2025-08-15 14:52 ` Alan Stern
2025-08-15 15:53 ` ValdikSS
2025-08-15 17:07 ` Alan Stern
2025-08-15 18:13 ` ValdikSS
2025-08-16 2:04 ` Alan Stern [this message]
2025-09-21 23:11 ` ValdikSS
2025-09-22 14:16 ` Alan Stern
2025-09-22 14:38 ` ValdikSS
2025-09-22 14:43 ` Alan Stern
2025-09-22 14:48 ` [PATCH] usb: ohci: delay endpoint descriptor unlinking to reduce transfer latency ValdikSS
2025-10-01 19:27 ` Alan Stern
2025-10-01 22:34 ` [PATCH v2] " ValdikSS
2025-10-02 17:05 ` Alan Stern
2025-10-22 13:39 ` [PATCH v2 RESEND] " ValdikSS
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=4e83d098-19e8-45aa-94e7-9ef005a0c8ab@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=iam@valdikss.org.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox