Here is a proposed patch for improving building sigrok-test. Mainly, it just
adds support for python 3.5 and updates the README. This fixes a few things
that slowed me down getting the unit tests running.
While I have been developing software for decades, I am new to the code
submission
[resending, looks like sourceforge and hotmail.com have a compatibility issue]
Here is a proposed patch for improving building sigrok-test. Mainly, it
just adds support for python 3.5 and updates the README. This fixes a
few things that slowed me down getting the unit tests running.
While
I
ual processing of the data suddenly becomes a
> lot easier.
>
> Regards,
> -Soeren
>
> On 2016-09-06 05:46, Karl Palsson wrote:
>> Chris Dreher <chrisdre...@hotmail.com> wrote:
>>> I am looking for some advice on the best option to display
>>> overlapping pac
> Date: Thu, 6 Oct 2016 09:23:16 +0200
> From: gerhard.sit...@gmx.net
> To: sigrok-devel@lists.sourceforge.net
> Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
>
> On Wed, Oct 05, 2016 at 11:36 -0700, Chris Dreher wrote:
> >
> > In looki
In looking at how to output files from protocol decoders, I have the following
questions:
1. Once put() is called for OUTPUT_BINARY, is there anyway to go back and
change those bytes? This is especially useful for adjusting file headers based
on sample inputs the come later in the
s if the
currently used format breaks/prevents the specific use case.
Keep decoders simple in the sense that they consume an input
stream and generate an output stream. Don't bother with "file
formats" in a decoder, such a requirement might be a strong hint
that this is the job for an output mod
net
> Subject: Re: [sigrok-devel] Substantial improvement to decoding of MIDI
> messages
>
> Hi,
>
> On Fri, Aug 19, 2016 at 10:26:02AM -0700, Chris Dreher wrote:
>> Here is moderate-sized submission that substantially improves decoding of
>> MIDI messages.
>
>
Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
On Dienstag, 11. Oktober 2016 06:03:55 CEST Chris Dreher wrote:
> Thanks, I really, really do appreciate the answers.
>
>
> It seems the streaming design of sigrok eliminates a lot of file formats.
> Namely, most fil
tig wrote:
> [ summary: use an output module, see srzip for prior art ]
>
> On Tue, Oct 11, 2016 at 06:03 +, Chris Dreher wrote:
> >
> >
> > It seems the streaming design of sigrok eliminates a lot of
> > file formats. Namely, most file formats with a size fiel
?
-Chris
From: Bert Vermeulen <b...@biot.com>
Sent: Monday, October 10, 2016 2:50 AM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Outputting files from Protocol Decoders
On 10/10/2016 01:22 AM, Chris Dreher wrote:
> Here is a brie
I appreciate this being worked on.
There is one scenario I am wondering whether it is handled. I am not familiar
enough with libsigrokdecode's code to know. The question is when a lower-level
PD has its decode_end() called and that PD flushes data with calls to put(),
will the next
:53 PM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] [PATCH 9201/9201] decode session: add optional
decode_end() PD method and send_eof() session call
On Sun, Oct 16, 2016 at 19:14 +, Chris Dreher wrote:
>
> I appreciate this being worked on.
Notice that we are t
> > Wouldn't it be better to invest more time in support for existing
> > logic analyzers? Features like memory compression support for
> > pulseview would help the project a lot more in my opinion.
>
> No, because frankly, what's currently out there is crap.
My 2 cents (for what its worth):
As someone who writes iOS code that interfaces with external hardware, I can
give some feedback on this.
The short answer is that it is unlikely that attaching a logic analyzer to an
iPad or iPhone will be possible.
This is because on iOS, Apple's general philosophy is to only support standard
Very minor correction: HID *may* use CONTROL only transfers and INTERRUPT
IN/OUT is optional (HID does not use BULK). However, this is a little
off-topic from the main point of this discussion.
-Chris
From: Stefan Brüns
Sent: Thursday, March 17, 2022 6:11 PM
Just a heads up that sigrok.org is down. Attempts to connect to either
http://sigrok.org or https://sigrok.org results in ERR_CONNECTION_REFUSED.
This was attempted using different computers, different browsers, and different
networks (i.e. Wi-Fi and cellular).
-Chris
Guys, Paul has been asking for a PR for 3 weeks. Can someone help him?
-Chris
From: Paul Kasemir
Sent: Saturday, October 8, 2022 1:41 PM
To: sigrok-devel@lists.sourceforge.net
Subject: Re: [sigrok-devel] Can we finally merge link-mso19 hardware support
17 matches
Mail list logo
