Re: [sigrok-devel] asix-sigma fixes: capture and timing issues, multi-device support

2016-10-26 Thread jry 
Please update ASIX SIGMA firmwares to latest versions:
https://gitlab.com/jrysig/sigrok-firmware/commits/asixfix

jr

On Wed, Oct 26, 2016 at 12:52 PM, jry  wrote:

> Another fixed bug:
>
> http://sigrok.org/bugzilla/show_bug.cgi?id=838
>
> jr
>
> On Wed, Oct 26, 2016 at 11:07 AM, jry  wrote:
>
>> Please note that I'm pushing further asix-sigma patches to
>> https://gitlab.com/jrysig/libsigrok/commits/asixfix
>>
>> So feel free to review latest repository version.
>>
>> Have a nice day
>> Jan Rysavy
>>
>> On Sun, Oct 23, 2016 at 4:49 PM, jry  wrote:
>>
>>> First batch of asix-sigma patches is available at
>>> https://gitlab.com/jrysig/libsigrok/commits/asixfix
>>>
>>> Following major problems are fixed:
>>> http://sigrok.org/bugzilla/show_bug.cgi?id=841
>>> http://sigrok.org/bugzilla/show_bug.cgi?id=840
>>> http://sigrok.org/bugzilla/show_bug.cgi?id=839
>>>
>>> Next on my to-do list are broken triggers:
>>> http://sigrok.org/bugzilla/show_bug.cgi?id=359
>>> but it looks like it will take some time, because SIGMA's triggers are
>>> pretty capable:
>>> http://www.asix.cz/download/analyzers/sigma2_en.pdf (Pages 14 - 17) and
>>> even existing
>>> triggers code isn't small.
>>>
>>> Do you prefer to push these patches now, so users could start using
>>> sigrok with SIGMA
>>> (and I must quit using git rebase -i to fix my committed patches :) or
>>> should I finish triggers first?
>>>
>>> Fortunately Ondrej Zoubek from ASIX is very helpful and patiently
>>> answers my dumb questions.
>>>
>>> Best regards
>>> Jan Rysavy
>>>
>>
>>
>
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] asix-sigma fixes: capture and timing issues, multi-device support

2016-10-26 Thread jry 
Another fixed bug:

http://sigrok.org/bugzilla/show_bug.cgi?id=838

jr

On Wed, Oct 26, 2016 at 11:07 AM, jry  wrote:

> Please note that I'm pushing further asix-sigma patches to
> https://gitlab.com/jrysig/libsigrok/commits/asixfix
>
> So feel free to review latest repository version.
>
> Have a nice day
> Jan Rysavy
>
> On Sun, Oct 23, 2016 at 4:49 PM, jry  wrote:
>
>> First batch of asix-sigma patches is available at
>> https://gitlab.com/jrysig/libsigrok/commits/asixfix
>>
>> Following major problems are fixed:
>> http://sigrok.org/bugzilla/show_bug.cgi?id=841
>> http://sigrok.org/bugzilla/show_bug.cgi?id=840
>> http://sigrok.org/bugzilla/show_bug.cgi?id=839
>>
>> Next on my to-do list are broken triggers: http://sigrok.org/bugzilla/sho
>> w_bug.cgi?id=359
>> but it looks like it will take some time, because SIGMA's triggers are
>> pretty capable:
>> http://www.asix.cz/download/analyzers/sigma2_en.pdf (Pages 14 - 17) and
>> even existing
>> triggers code isn't small.
>>
>> Do you prefer to push these patches now, so users could start using
>> sigrok with SIGMA
>> (and I must quit using git rebase -i to fix my committed patches :) or
>> should I finish triggers first?
>>
>> Fortunately Ondrej Zoubek from ASIX is very helpful and patiently answers
>> my dumb questions.
>>
>> Best regards
>> Jan Rysavy
>>
>
>
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Re: [sigrok-devel] asix-sigma fixes: capture and timing issues, multi-device support

2016-10-26 Thread jry 
Please note that I'm pushing further asix-sigma patches to
https://gitlab.com/jrysig/libsigrok/commits/asixfix

So feel free to review latest repository version.

Have a nice day
Jan Rysavy

On Sun, Oct 23, 2016 at 4:49 PM, jry  wrote:

> First batch of asix-sigma patches is available at
> https://gitlab.com/jrysig/libsigrok/commits/asixfix
>
> Following major problems are fixed:
> http://sigrok.org/bugzilla/show_bug.cgi?id=841
> http://sigrok.org/bugzilla/show_bug.cgi?id=840
> http://sigrok.org/bugzilla/show_bug.cgi?id=839
>
> Next on my to-do list are broken triggers: http://sigrok.org/bugzilla/
> show_bug.cgi?id=359
> but it looks like it will take some time, because SIGMA's triggers are
> pretty capable:
> http://www.asix.cz/download/analyzers/sigma2_en.pdf (Pages 14 - 17) and
> even existing
> triggers code isn't small.
>
> Do you prefer to push these patches now, so users could start using sigrok
> with SIGMA
> (and I must quit using git rebase -i to fix my committed patches :) or
> should I finish triggers first?
>
> Fortunately Ondrej Zoubek from ASIX is very helpful and patiently answers
> my dumb questions.
>
> Best regards
> Jan Rysavy
>
--
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive. 
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

[sigrok-devel] asix-sigma fixes: capture and timing issues, multi-device support

2016-10-23 Thread jry 
First batch of asix-sigma patches is available at
https://gitlab.com/jrysig/libsigrok/commits/asixfix

Following major problems are fixed:
http://sigrok.org/bugzilla/show_bug.cgi?id=841
http://sigrok.org/bugzilla/show_bug.cgi?id=840
http://sigrok.org/bugzilla/show_bug.cgi?id=839

Next on my to-do list are broken triggers:
http://sigrok.org/bugzilla/show_bug.cgi?id=359
but it looks like it will take some time, because SIGMA's triggers are
pretty capable:
http://www.asix.cz/download/analyzers/sigma2_en.pdf (Pages 14 - 17) and
even existing
triggers code isn't small.

Do you prefer to push these patches now, so users could start using sigrok
with SIGMA
(and I must quit using git rebase -i to fix my committed patches :) or
should I finish triggers first?

Fortunately Ondrej Zoubek from ASIX is very helpful and patiently answers
my dumb questions.

Best regards
Jan Rysavy
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel