ce4d26ddf9
Various cosmetics, whitespace, consistency fixes.
2013-07-31 13:09:48 +02:00
29a27196a1
s/DRIVER_LOG_DOMAIN/LOG_PREFIX/.
...
This is more correct anyway, and also a bit shorter and more readable.
2013-05-03 21:59:32 +02:00
50985c2019
GPL headers: Use correct project name.
2013-04-23 22:24:30 +02:00
c118080b1d
hantek-dso: Store USB connection in sr_dev_inst
2013-04-17 00:49:41 +02:00
034accb512
hantek-dso: move buffer sizes to device context
...
There are only two sizes for every device: 10k and the complete
per-channel buffer size. This can be doubled if one channel is disabled.
2013-04-11 18:32:08 +02:00
8c971b6e5c
hantek-dso: cosmetics
2013-04-07 14:01:03 +02:00
cbc6f3b253
hantek-dso: Use message logging helpers.
2013-01-29 12:56:02 +01:00
69e19dd769
Always interleave analog data with all enabled probes.
...
The new "probes" field in sr_datafeed_analog contains a copy
of all enabled struct sr_probe.
2013-01-23 03:40:44 +01:00
1987b8d63e
drivers: use new sr_config struct
...
Sending an SR_DF_META packet at the start of every stream is not
mandatory; the frontend should ask for what it needs, and any extra
information the driver wants to send will come in due time.
2013-01-21 23:32:49 +01:00
e98b7f1be0
hantek-dso: Use message logging helpers.
2012-11-10 19:42:37 +01:00
e9022f596d
sr: make struct drv_context global
2012-09-11 21:27:26 +02:00
19b0cce312
hantek-dso: use default libusb context
2012-09-11 21:16:16 +02:00
a3508e33f9
hantek-dso: remove sources from session when done
2012-08-03 11:29:01 +02:00
269971ddce
hantek-dso: use driver-private storage for instances and libusb_context
2012-08-03 11:29:00 +02:00
25a0f108f4
sr/drivers: change driver dev_open/dev_close calls to use sdi
2012-08-03 11:27:31 +02:00
88a13f30bd
hantek-dso: add profiles for all five models in the series
...
Also cleaned up profile struct, and use the new firmware filenames.
2012-06-27 19:36:30 +02:00
fc8fe3e314
hantek-dso: get rid of broken GTV_TO_MSEC firmware upload timeout
2012-06-27 01:02:06 +02:00
e749a8cb50
hantek-dso: start sending the frame only from the trigger point
...
Samples received before the trigger point are stored. From the
trigger point on, every chunk received from the device is sent
up the session bus. After the device has finished sending, the
stored samples are transmitted.
2012-06-26 23:26:55 +02:00
6e6eeff47a
hantek-dso: capturestate packet also contains the trigger point
...
Not yet used, but it's the key to knowing where in the frame to
start displaying; the frame is used as a circular buffer, and what
is sent is effectively a snapshot.
2012-06-18 23:09:37 +02:00
a10c805636
hantek-dso: default to DC coupling
2012-06-05 18:18:23 +02:00
62bb8840e1
sr: hantek-dso: Consistency renames, constification.
2012-06-01 01:12:09 +02:00
2715c0b86b
hantek-dso: hopefully handle endianness in voltage setting
2012-05-30 23:56:13 +02:00
b58fbd99c8
hantek-dso: support for SR_HWCAP_COUPLING
2012-05-30 23:56:13 +02:00
313deed219
hantek-dso: support SR_HWCAP_VDIV
2012-05-30 23:56:12 +02:00
a370ef1916
hantek-dso: support for setting all CMD_SET_TRIGGER_SAMPLERATE params
2012-05-30 23:56:12 +02:00
bc79e906a0
hantek-dso: proper protocol implementation of trigger/samplerate setting
2012-05-30 23:56:12 +02:00
6e71ef3b6f
hantek-dso: fix channel selection
2012-05-30 23:56:12 +02:00
ae88b97ba2
hantek-dso: delimit frames with SR_DF_FRAME_* packets
2012-05-30 23:56:12 +02:00
3b533202c8
sr: initial support for Hantek 2xxx/5200 USB oscilloscopes
2012-05-30 23:56:12 +02:00
Uwe Hermann
Bert Vermeulen