>> if users
>> want the information to be available, and up-to-date. Waiting for
>> somebody else to do it all (and do stuff they don't even know
>> about) won't result in much progress.
I agree. May I have a wiki account to add the TENMA_72_2705_V65 in the
wiki? My point was to say that the devices listed in the Korad KAxxxxP
series page [1] should be in the main supported hardware page [2]
because (presumably a lot of people and) I see no relation between a
Korad product and a Tenma product at a first glance.
Soeren, I like the CLI switch improvement. If I understand it correctly,
all libsigrok/hardware/*/api.c should be modified to comply with it?
[1] https://sigrok.org/wiki/Korad_KAxxxxP_series
[2] https://sigrok.org/wiki/Supported_hardware#Power_supplies
Mickael
On 06/06/2020 12:42, Soeren Apel wrote:
On Sat, 2020-06-06 at 12:27 +0200, Gerhard Sittig wrote:
On Sat, 2020-06-06 at 00:29 +0200, Mickael Bosch wrote:
[ ... yet another compatible ... ]
The "*IDN?" output is:
TENMA 72-2705 V6.5 SN:<8 digits SN>
[ ... ]
BTW, when I bought this device I thought I would have to write a
complete driver. I had a good surprise when I saw that the
korad-kaxxxxp driver already does all the hard stuff. That said, do
you think that listing *all* known compatible devices in [2] would
help sigrok newbies like me and show that sigrok rules?
Here is the trick question: Can you enumerate all known
compatible devices, and tell whether they are operational,
without having access to them? Can you tell how to determine the
devices' capabilities or limits in advance, and how they may or
may not identify themselves? That may answer the question whether
the project is able to provide the support out of the box for
devices they don't know about in the first place ... :)
My take on it is this: how can users verify whether a device works or
not if they *must* alter the source code first and compile everything
from scratch? That's not helping, honestly.
What I would wish for is a command-line switch that allows users to
forego the whitelisting in the drivers and force a particular driver to
use a particular (USB) device to be a particular model. That way, users
wouldn't need to alter the source code.
Alas, none of us have the time to work on that, I reckon.
-Soeren
Which means that it does take the users' reports of their
existance and whether they work, before support can be claimed.
Also users participating in wiki updates is required, if users
want the information to be available, and up-to-date. Waiting for
somebody else to do it all (and do stuff they don't even know
about) won't result in much progress.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
