resulting binary,
and the runtime traversal of that list whatever it may look like.
Sort order isn't an issue either. Only termination is, unless we
can tell the start and end by other means.
virtually yours
Gerhard Sittig
--
If you don't understand or are scar
ge, etc). So
that needs verification (re-execution after cable and port
checks, checks for power drops, etc).
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.
similar), but
could not verify, and still can't. Maybe check if Kingst LA1010
is actually a "clone" of something else, or speaks the same
protocol. To me it looked very similar to Saleae Logic 16, but I
don't have that device either, so can't tell with certainty.
virt
models. But these are easy to add after getting
identified.
https://sigrok.org/gitaction/libsigrok.git/0db1b18..e7c7aa1
Guess you will tell here when the Kingst LA1010 works for you. So
that the wiki page can get updated after all models were verified.
virtually yours
Gerhard Sittig
On Mon, 2022-12-19 at 07:01 +0100, Markus Heidelberg wrote:
>
> Am Sonntag, 18. Dezember 2022, 05:40:38 CET schrieb Gerhard Sittig:
> >
> > Have pushed 2e379708554e to my binding-u32 branch. That hopefully
> > better fits what's currently in mainline.
>
> A se
est to ping here if you got an update on that PR. As I'm
not scanning github, and others may be interested and are not
subscribed either. Thank you for working on that subject!
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
elieving that it'd be my job to help them personally or even do
their homework when nobody else would respond. Or even starting
that way without ever trying public channels first. I like to
help when I can, but I don't feel like "servicing for free"
just because they expect me to.
v
r willingness to do it. Not
using git at all, piling up dirty commits and not cleaning them
up, not providing a minimum of essential information, etc etc all
reduces the probability of having the submission taken. But that
shall not be a surprise either.
Need I repeat it? This is my personal perspective a
On Sun, 2022-12-18 at 02:29 +0100, Markus Heidelberg wrote:
>
> Am Samstag, 17. Dezember 2022, 20:26:42 CET schrieb Gerhard Sittig:
> >
> > The other issue that you noticed is that current bindings seem to
> > completely lack u32 conversion support. Haven't check
On Sun, 2022-12-18 at 02:29 +0100, Markus Heidelberg wrote:
>
> Am Samstag, 17. Dezember 2022, 20:26:42 CET schrieb Gerhard Sittig:
> > On Fri, 2022-12-16 at 19:37 +0100, Gerhard Sittig wrote:
> > >
> > > On Sun, 2022-12-11 at 02:30 +0100, Markus Heidelberg wrote
On Fri, 2022-12-16 at 19:37 +0100, Gerhard Sittig wrote:
>
> On Sun, 2022-12-11 at 02:30 +0100, Markus Heidelberg wrote:
> >
> > I found some crashes using PulseView with specific command line options.
> >
> > https://github.com/sigrokproject/libsigrok/pull/202
>
lerates should be u64 everywhere, no
questions asked.
Am more reluctant on the bindings, since I don't know and don't
use most of them. Would be good to have more eyes on this part of
your submission.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by a
t
caught their attention. They are over at IRC, many seem to not
be in the mailing list.
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.
___
s
git/commitdiff/49c45a5c64a031c4371710cad1e7a63c9d67c318
Notice that it has your name on it. If you ACK then I can push
it. If you NAK then I suggest you provide something different.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your par
parse. And all of
this just to save a few key strokes? No. Not desirable.
There is more to this style guide than mere cosmetics or personal
preference on alternatives that all are equal. The preferences
that are documented are reasoned, not arbitrary. Usually. Often.
Projects may differ, as do hum
On Sat, 2022-12-03 at 00:24 +0100, Markus Heidelberg wrote:
>
> Am Freitag, 2. Dezember 2022, 20:56:45 CET schrieb Gerhard Sittig:
> >
> > Got example data to reproduce? Helps others review that change,
> > improves the odds of having it go mainline. Could even be part o
e is prior art in some of the src/input/ modules.
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.s
ers can join and help, and also can benefit from
information that was given. Thank you.
And if public channels with many more participants cannot get
you an answer, then I'm as unable to help you in private. Such
a request would only eat into my personal resources yet help
nobody. I'd rath
ss.
Or wait until somebody else gets around to it. At the pace that
the few active people can keep who are currently left to the
project. Whatever works for you.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents o
that. If you feel that waiting is
OK, then what would you complain about if others wait, too?
Or (that's my take) complain to everybody equally who still would
not respond although they could have. After all those requests
and the time that has passed. Your pick.
virtually yours
sider doing something
helpful. Support your fellow users when they ask for help, don't
wait for a developer to do it, all of it, and every time, while
everbody else watches. Support developers if they ask for help,
don't watch and wait for them to "somehow manage" while th
t a field of expertise, and
think that it is not ubiquitous? Do you seriously expect one or
two developers to intimitely know _all_ of what's covered by the
sigrok project? Every version of every device, every transport,
every file format, every decoder protocol, every programming
language, every bui
nt that tool, too, then join forces
and create one. Whatever you do, there still is no need to wait
for a developer to do it.
Need I explicitly state that this is a personal view of mine as
one of the active sigrok users? And that I'm not a maintainer?
Because some (many?) still ha
I've been asking for some sharing of the work for so long.
Take a few minutes, and do look at the submission which the
author wants to get feedback on. There is no need to wait. Do it!
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
hat the current userbase would neither discuss nor
check or test nor extend the current compile time registration of
device drivers? Not very probable.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or
the project. Does for me.
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:
own the hardware can reliably verify the
driver's proper operation.
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-
ant if
others want to check drivers which they care about whether they
suffer from similar issues.
Your submission was taken, thank you for providing it.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
osity raised, to have your
attention attracted to the spot of interest.
$ ctest -N
$ ctest -N -V
$ ctest -VV
I think cmake generated Makefiles (which pulseview probably uses
when built with the script) support this invocation, which
explains how "make test" is related to ctest(1) outs
hat you are "missing" is
the ir_irmp decoder. I know from first hand experience that it
works with local builds. It's an AppImage specific issue that
_ctypes would not be found, or considered to fail loading.
virtually yours
Gerhard Sittig
--
If you do
. Neither said that, nor wrote it,
nor meant it. All I said is: I haven't used your firmware in the
few weeks that I worked on the PC side of Kingst LA since vendor
firmware was required anyway. Haven't looked at implementation
details of your submission when I commented on the choice of a
g
ew calls config_set() with SR_CONF_ENABLED when
the channels get enabled/disabled. Who's familiar with that API?
In theory smuview should also be able to control the PWM channels
and their properties. Though it may be unusual to use smuview to
control a device with logic input channels ...
r may not have
hiccups, these would be indenpendent from Kingst LA support).
When in doubt then run Linux for comparison or build Windows
binaries from sources. Use any libusb version that's desired.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the ab
It's "just" the web server which is down.
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-d
On Sun, 2022-01-09 at 08:22 +0100, Gerhard Sittig wrote:
>
> On Mon, 2022-01-03 at 08:32 +0100, Fabrice Fontaine wrote:
> >
> > --- a/configure.ac
> > +++ b/configure.ac
> > @@ -407,9 +407,14 @@ AS_IF([test "x$HAVE_CXX11" != x1],
> >
On Sun, 2022-01-09 at 10:43 +0100, Fabrice Fontaine wrote:
>
> Le dim. 9 janv. 2022 à 08:27, Gerhard Sittig a écrit
> :
> >
> > Mention preferred versions before "also acceptable" fallbacks
> > perhaps? Checks probably also should reflect preference.
>
ad know this decoder is about model
railways. The "DCC" term is also used in the ARM hardware
context, where it refers to a debug channel. That's why I feel
that even the "short name" of the decoder should reflect model
railroad to reduce ambiguity.
virtually yours
Gerhard S
ng is assigned
before the check actually happens is surprising. How robust is
that phrase, have you checked it in different configurations,
with new and with old libs and with none at all available? Some
machines could provide both versions while you seem to prefer the
newer implementation.
virtually
reduce the probability of being taken.
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.sourcefor
anks,
> Andreas
>
> [1]
> https://github.com/python/cpython/commit/0a8e57248b913851640c64375600f05157c997df
> [2] https://www.python.org/dev/peps/pep-0394/
Have rebased the commit provided by Evangelos Foutras, see
libsigrokdecode a6a5e2c8b0e9. Hope this will transparently
cover 3.11 and other Python versions.
Than
On Sat, 2021-07-03 at 19:16 +0100, Martin Ling wrote:
>
> On Sat, Jul 03, 2021 at 04:49:34PM +0200, Gerhard Sittig wrote:
> > On Thu, 2021-07-01 at 23:44 +0100, Martin Ling wrote:
> > >
> > > The current architecture of libsigrok makes this difficult at the
> >
, as well as in the archives at
https://sourceforge.net/p/sigrok/mailman/message/37297430/
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.
___
si
to face the same issue and have to
guess again, or give up. :( That wiki comment is just a nice
addition, but totally not the solution.
If anyone knows how to communicate to Stuart that making the log
available that he has is the most important help he can provide,
PLEASE go ahead and help getting
t mainline today. Your issue should be fixed in current
master. See commit 020df861e0eb. I gave you a Reported-By to
acknowledge your contribution. Thank you!
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the
vailable information at the time
strongly suggested that automatic detection would not be
possible. Would be nice if we could have the best of all: other
devices unaffected, _and_ reliable operation for the fluke-45
device, _and_ helpful diagnostics to users when a known fatal
condition is seen. Can we g
e.
Is unusual end-of-line involved which affects the MQ detection?
Do you have other cables that you can try? Would not be the first
time that individual USB to UART adapters get in the way, while
others work fine. Is the communication 8bit clean, or is some
ASCII plus parity scheme involve
ble. No amount of delay that I added after INIT
helped in my local setup. While every addition of delay degrades
the perception of the driver's operation. :( Not delaying at all
made me lose USB connections, not able to recover from that for
minutes. So the current mainline implementa
ev rule. Did
rebase and squash, and specified delays that worked with the
Keysight 34465A. Can you check recent master whether 34460A works
for you? Thank you!
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your parents or an
On Thu, 2021-03-11 at 08:26 +0100, Helge Kruse wrote:
>
> Am 10.03.2021 um 14:15 schrieb Kevin Grant:
> >
> > Hello Gerhard,
> >
> > On 2021-03-08 18:25, Gerhard Sittig wrote:
> >
> >> Is the basic operation fundamentally broken, or are just not all
&
R relate to other PRs? Is it
similar, or identical, or different and how so? Can you
coordinate these changes with other submitters, or at least
communicate when there is a duplication or what its motivation
may be? Tell when there are dependencies on other PRs? Ideally
combine them and not duplicate them?
sigrok applications.
> I may not be able to run any decoders on output from the
> 'scope. But running them and looking at the operations against
> LA data, I should be able to figure out how to do my DFFT.
Maybe you are not looking for protocol decoders as such, but
something diffe
rates how slippery a slope it is to weaken tools
for everybody instead of helping new users to use these tools
properly.
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.
private or public? What the? No, that's up to each
individual themselves, whom they talk to, and how they do it. As
well as how to respond to being approached. Has been, and should
remain so. Everything else is weird, and not an improvement.
virtually yours
Gerhard Sittig
--
If you don't
how it works.
If you want to reply to the list, then hit list reply, or reply
to all. Good user agents know how to do that. Unfortunately bad
user agents are so popular. Reason? See above. It's not just
users, these days even MUA authors appear to not be aware.
virtually yours
Gerhard Sittig
trying to help the project. Which isn't desirable
either, for several reasons. Also adds extra work on those who
try to accept this contribution, again reducing the odds of
seeing it happen. The time could have been spent on something
useful instead.
virtually yours
Gerhard Sittig
--
If y
al version
dependency, etc. Or where the sort order originates (3.9 3.8 3
3.8 3.7 ... above).
Did see the https://bugs.python.org/issue36721 report but have
trouble parsing it, or seeing what the outcome is, or where it's
on record for others to see without sifting throug a lengthy bug
t mainline in commits
051d85f28d2e..955ab60455d3 after squashing more maintainability
and style improvements and getting your ACK on those additions.
This shall fix the portability issues in the Windows builds.
virtually yours
Gerhard Sittig
--
If you don't understand or are
On Fri, 2021-03-12 at 17:59 +0100, Rene Kita wrote:
>
> On Fri, Mar 05, 2021 at 07:55:36PM +0100, Gerhard Sittig wrote:
> > This is a call for testers. Especially on those platforms which
> > are not exactly mainstream. That is: anything outside of one of
> > the popula
On Sun, 2021-03-14 at 11:03 +0100, Helge Kruse wrote:
>
> Hello Gerhard,
>
> Am 05.03.2021 um 19:55 schrieb Gerhard Sittig:
> > This is a call for testers. Especially on those platforms which
> > are not exactly mainstream. That is: anything outside of one of
> > th
ths, magic incantations due
to lack of a protocol spec), but again without access to the
hardware I could not test anything in a useful manner. And some
of these issues are next to impossible to address with these
closed devices. That's when I just went for the low hanging fruit
now. In addition t
t; list end
> driver1, do something
> driver2, do something
> driver3, do something
Drivers 4 and 5 don't show up because of my mistake mentioned
above.
But when driver 2 is disabled, it should not be part of the build
and thus should not be par
here
some other approach that is as promising as the constructors are?
Thank you for helping improve portability and maintenance!
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ttps://sigrok.org/wiki/File:Kingst_la2016_mugshot.png
on the device wiki page https://sigrok.org/wiki/Kingst_LA2016
which suggests that the notch is on the connector's "top" and
pointing to the cover of the device.
virtually yours
Gerhard Sittig
--
If you don't underst
ree. But
I'd give you the benefit of a doubt on first occurance, and
assume that you just may not be aware. Thus wanted to let you
know. Hope this helps.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask y
nd if there was a review, it missed this issue.
Would be good to get more eyes on such stuff, and more hands
helping out.
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.
On Sun, 2021-01-24 at 13:51 +1100, Peter Skarpetis wrote:
>
> On 23/1/21 10:52 pm, Gerhard Sittig wrote:
> >On Sat, 2021-01-23 at 08:43 +1100, Peter Skarpetis wrote:
> >>
> >>I have recently added support for the MHINSTEK MHS-5200A function
> >>generat
thing about "vectors") that led to what's
"numbers and state" now. Compare the original submission to what
ended up in mainline. Really a tough call to make. In that
specific case, I thought that one PD would be more usable than a
set of stacked micro PDs would be. But
re too
many or too severe.
(We can also discuss this in IRC when you are around there.
Results in a more fluent conversation than mail exchange.)
Who else has got devices of that MHS series and can test?
virtually yours
Gerhard Sittig
--
If you don't understand or are sca
ged a little more). Thank you.
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
whether you want me to shuffle the order. The "show
unknown" option also looks useful to me. And I'd pick all of it
(the segments comment, too, very useful). Assuming that the test
passes, haven't run it yet. PD output shouldn't change when the
implementation changes the l
too. And renamed the identifier such that all of the
info struct and packet length and routine names show up in the
same text search (consistent prefix).
Your driver went mainline. See libsigrok 4c29bba1f076. Thank you.
virtually yours
Gerhard Sittig
--
If you don't understand or are
in the packet" :-] ).
Of course you get credited as the author who did the work of
creating the driver. If something was broken, that's my fault and
can get fixed. Just provide a followup commit. Thank you for
contributing the driver, and for updating the wiki. That's very
tion as
cpp macros suffered from robustness issues. Other bug fixes in
the past revealed that redundant local copies are not always
right, e.g. get signedness wrong. That's another reason to not
re-invent this stuff in calling code. The use of common helpers
transparently benefits al
libsigrok aa8e4959e24a. Thank you for reporting and addressing
the issue!
Who's got FTDI based setups where scans failed before, and can test?
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
thing local" is not recommended, and
not supported. Either use all vendor's packages, or all local
builds. The versions need to match since the components highly
interact with each other. Other setups may or may not work, you
are on your own in that case (should not be the case here with an
Ap
instead at the top of
the file? To execute the script in the location that it resides
in (as seems to be assumed in the script's implementation),
regardless of where it was invoked from. Seems more robust than
hunting down more paths during maintenance.
virtually yours
Gerhard Sittig
--
port is implemented in the
library which is shared by all applications. Behaviour should be
the same across all of them.
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.
___
R_ERR_DEV_CLOSED, a device is
expected to be opened for an activity but isn't.
A quick look at the scan related parts of
src/hardware/ftdi-la/api.c suggests that neither the scan()
routine nor its descendents open the device at this time.
Only for later use after the scan has completed.
Can som
operation. Or getting an
ACK from other people's review can help apply the fix in mainline
and thus show up in nightlies.
Also please state if you want your name on the commit message as
the user who helped improve the software by reporting the issue.
virtually yours
Gerhard Sittig
--
If you
If sigrok could add an option to save only samples in between the currently
> > displayed marker, that would already go a long way.
>
> Pulseview has that option for well over a year.
Release doc says 2016-01, version control says 2015-12. Yep,
has been around for more than a year.
s-bticino-decoding/#captured-scs-telegrams
>
> Is there a better way to extract only certain ranges of data from a sigrok
> capture?
You mean like using cursors and saving the range as a file?
Yes, that'd probably be easier, but not as interesting. :-P
virtually yours
Gerh
afted to me. :)
Never got the idea that _not_ having a samplerate would be the
normal condition, after your initial capture must have had one,
and all the import formats support a respective option when the
file content lacks the information. :-]
virtually yours
Gerhard Sittig
--
If you d
le to other home automation setups
like KNX or EIB? Searching the 'Net suggests that "simplified
wiring" is rather generic a term, brings up boats, motor bikes,
and houses.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of
;
> To match the intent captured in the comment, the HUPCL bit should be
> cleared.
Merged in 1b011060df55, thank you.
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.
__
to
improve robustness, yet kept your individual commit to give you
more credit than a Reported-By: attribute.
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.
___
27;s why a public repo is
much preferred over sending copies of files of unknown state
around.
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.
___
plerate, captures said 4MHz). Curious
users can already make use of these even without a decoder.
The decoder remains to be done (review and pickup), and will
follow later.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any of the above
ask your
onsider
helping those users who see the files and would like to know what
to expect of them.
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.
___
st go to the directory they
install to (it's likely to be something isolated and local
specific), and decide when to remove and what to remove. Lets
them keep what's important to them, and can be as simple as just
removing the single directory, or can selectively remove a few
decoders which
n inefficiency if you will.
But is the operation of the code in question flawed, or was the
implementation just unexpected to you? Got more information?
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 y
d everything. Have pushed the commits that I
prepared two weeks ago instead. Which also covers the RLB, REEM,
RP, LPMP, WP annotations (EEPROM address calculation needed a
fix, please check recent master for correctness).
virtually yours
Gerhard Sittig
--
ork, I wanted to give you more than a Submitted-By:
attribution. So I created a commit to make you the author and get
the recognition. Hope that's OK for you.
https://sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=588295b8b9cd9b3c7e67ccd3bfd74e05c513c0fb
virtually yours
Gerhard
sigrok.org/gitweb/?p=libsigrok.git;a=commitdiff;h=9dde746023c99a9cd8a34ef7c4b60bad4f78f283
It was my fault, I tested with logic data and with mixed signals,
but analog-only escaped me (and everybody else who ran the code
and reported success).
Thank you for checking, and coming up with a fix!
virtually yours
Gerhard Sittig
--
On Wed, 2020-06-24 at 21:09 +0200, Gerhard Sittig wrote:
>
> Out of interest I whipped up a decoder implementation. Looks
> pretty usable to me, and is assumed to be operational. But hasn't
> seen much test yet, mostly due to lack of example captures. [ ... ]
Status up
. Of couse tests only become
applicable after PD creation or fixes/extension. But I do suggest
to submit test captures first, and early on. The PD itself and
its test can follow later.
virtually yours
Gerhard Sittig
--
If you don't understand or are scared by any o
he feature, and future users may want to contact you
since you are the author of or a contributor to a significant
feature). Can I use the mail address that you used here in the
mailing list, for proper attribution of your work?
virtually yours
Gerhard Sittig
--
If you don't understand or
se and keep
the other features? There are lots of comments, the logic should
be straight forward to follow. Up to you to either start from the
existing decoder (which could be incomplete) or to start from a
clean state (the spec, which is _the_ reference) to come up with
a set of w
On Mon, 2020-07-06 at 01:20 +0400, JULIO AGUIRRE wrote:
>
> On Thu, Jul 2, 2020 at 9:58 AM Gerhard Sittig wrote:
>
> > Well, open the file, look at the signal's timing, do the math. Do
> > you remember when I asked you to come up with a set of rules on
> > paper
ates the
traffic and acquisition hardware. Want to provide something so
that other users can benefit?
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.
_
al names, out of the box and without manual
intervention. Just requires that the sniffer device identifies as
one, and won't pretend it'd be something generic. Ask artag, he's
been there. ISTR the experiment got stuck when an individual USB
ID was required to get there. Maybe you can help
1 - 100 of 226 matches
Mail list logo
