From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: "Jian J Wang" <jian.j.wang@intel.com>,
"Liming Gao" <gaoliming@byosoft.com.cn>,
"Hao A Wu" <hao.a.wu@intel.com>, "Ray Ni" <ray.ni@intel.com>,
"Richard Ho (何明忠)" <RichardHo@ami.com>,
edk2-devel-groups-io <devel@edk2.groups.io>
Subject: USB: reducing/removing EHCI and XHCI logging when bulk transfer requests timeout
Date: Tue, 29 Nov 2022 12:12:04 -0700 [thread overview]
Message-ID: <ef0e3d04-806b-445d-56a9-ac5cba6d7824@quicinc.com> (raw)
I've been working on the UsbNetworkPkg drivers that Richard Ho
submitted. One problem I've run into is that since we poll for bulk
requests, most of the time they will timeout - and currently both EHCI
and XHCI drivers log errors when that happens, which results in log spam
and makes interacting with the system very difficult (e.g. using UiApp).
I was wondering if we might consider adding some mechanism to omit those
messages if the user desires, perhaps on a per-build basis?
--
Rebecca Cran
next reply other threads:[~2022-11-29 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 19:12 Rebecca Cran [this message]
2022-11-29 19:43 ` [edk2-devel] USB: reducing/removing EHCI and XHCI logging when bulk transfer requests timeout Andrew Fish
2022-11-29 19:47 ` Rebecca Cran
2022-11-29 20:51 ` Andrew Fish
2022-11-29 23:05 ` Rebecca Cran
2022-11-30 7:48 ` Chang, Abner
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-list 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=ef0e3d04-806b-445d-56a9-ac5cba6d7824@quicinc.com \
--to=devel@edk2.groups.io \
/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