From: Oliver Neukum <oliver@neukum.org>
Organization: NOvell
To: stefan_kopp@agilent.com
Subject: Re: [PATCH] USB: add USB test and measurement class driver - round 2
Date: Fri, 29 Aug 2008 13:33:01 +0200
User-Agent: KMail/1.9.9
Cc: korgull@home.nl, greg@kroah.com, stern@rowland.harvard.edu,
       linux-usb@vger.kernel.org, me@felipebalbi.com,
       linux-kernel@vger.kernel.org
References: <20080827183615.GA15692@kroah.com> <200808291034.09307.oliver@neukum.org> <7D8F552F9FFBAC438A816966BEC4516BFBA3D0@cos-us-mb07.cos.agilent.com>
In-Reply-To: <7D8F552F9FFBAC438A816966BEC4516BFBA3D0@cos-us-mb07.cos.agilent.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200808291333.02113.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 787
Lines: 13

Am Freitag 29 August 2008 11:13:04 schrieb stefan_kopp@agilent.com:
> For large amounts of data (e.g. when downloading a waveform), USBTMC instruments often use a "binblock", a concept taken from the good old GPIB (IEEE488) standard, where the data is preceeded by a header and the header indicates how many bytes are following. So you first read and interpret the header and then you know exactly how many bytes to expect in the body of the message.

Not really ideal. We should tell user space how much really was sent.

	Regards
		Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/