mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: guido@kiener-muenchen.de
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: Michal Pecio <michal.pecio@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Steve Bayless <steve_bayless@keysight.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/4] usb: usbtmc: fix undersized high-speed bulk packets on xHCI
Date: Tue, 20 Oct 2026 23:12:18 +0200	[thread overview]
Message-ID: <d702d2b3b66d6229855515c2eed09636@kiener-muenchen.de> (raw)
In-Reply-To: <a642dbc2e4ba0efc381c69e26821762a@tipi-net.de>

Hi Nicolai,

The USBTMC protocol was defined by the IVI Foundation. The purpose of a 
specification is to ensure that manufacturers adhere to the agreed rules 
so that maximum compatibility between T&M instruments and client 
software (e.g. NI‑VISA, Keysight VISA, R&S VISA, etc.) is guaranteed.
The Linux USBTMC kernel driver is a class driver that has been tested by 
members of the IVI Foundation and ensures reliable communication with 
their devices. Therefore every manufacturer of USBTMC devices should 
comply with the specification and cannot expect bugs in device firmware 
to be fixed by patches to the USBTMC driver on Windows, Linux, or macOS.
If such an approach were tolerated, the development costs that one 
manufacturer omitted would be shifted onto and multiplied across all 
other manufacturers. If there is a demonstrable bug in the USBTMC kernel 
driver, we can certainly discuss fixing the driver. Otherwise I cannot 
support adding device‑specific patches to a class driver. Over time that 
would increase the driver’s complexity and encourage other manufacturers 
not to follow the jointly developed specification — something that would 
certainly not be acceptable for the TCP/IP stack either.

Best regards,

Guido Kiener


  reply	other threads:[~2026-10-20 21:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 14:33 Nicolai Buchwitz
2026-10-20 14:33 ` [PATCH 1/4] usb: usbtmc: handle undersized high-speed bulk IN packets Nicolai Buchwitz
2026-10-20 14:33 ` [PATCH 2/4] usb: usbtmc: handle undersized high-speed bulk OUT packets Nicolai Buchwitz
2026-10-20 14:33 ` [PATCH 3/4] usb: usbtmc: add Rigol DP800 and DS1000Z to the packet I/O quirk table Nicolai Buchwitz
2026-10-20 14:33 ` [PATCH 4/4] usb: usbtmc: send a ZLP after a full last packet in packet I/O mode Nicolai Buchwitz
2026-10-20 16:42 ` [PATCH 0/4] usb: usbtmc: fix undersized high-speed bulk packets on xHCI Michal Pecio
2026-10-20 18:33   ` Nicolai Buchwitz
2026-10-20 21:12     ` guido [this message]
2026-10-21  7:46       ` Nicolai Buchwitz
2026-10-21 12:29         ` Guido Kiener
2026-10-20 22:56     ` Michal Pecio
2026-10-21  7:42       ` Nicolai Buchwitz
2026-10-21  9:34       ` Nicolai Buchwitz
2026-10-23 18:26         ` Michal Pecio
2026-10-24 11:17           ` Nicolai Buchwitz
2026-10-24 20:23             ` Michal Pecio

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=d702d2b3b66d6229855515c2eed09636@kiener-muenchen.de \
    --to=guido@kiener-muenchen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michal.pecio@gmail.com \
    --cc=nb@tipi-net.de \
    --cc=stable@vger.kernel.org \
    --cc=steve_bayless@keysight.com \
    /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®