This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/simtrace@lists.osmocom.org/.
Dieter Spaar spaar at mirider.augusta.deHello Holger, On Tue, 04 Oct 2011 17:25:01 +0200, "Holger Hans Peter Freyther" <holger at freyther.de> wrote: > > and 9.4.3 Get Descriptor. Its the same rule, all the standard device requests are Control Transfers as described in 8.5.3. > What is a Control Pipe? The 'reserved bandwidth/window' for a control > request? Shall I repeat "Terms and Abbreviations" from the specification ;-) ? Control Pipe: Same as a message pipe. Message Pipe: A bi-directional pipe that transfers data using a request/data/status paradigm. The data has an imposed structure that allows requests to be reliably identified and communicated Think about the Control Pipe as the mechanism which transports the Control Transfers and a such the standard device requests. You can also put your own requests there (vendor specific requests). Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de