On Mon, Dec 19, 2016 at 09:14 +0000, Marchel Hooijboer wrote:
> 
> Thanks for the information, i have not used the script yet, but will create
> a new git checkout and try again. Problem was that the script was throwing
> an error and thus I used the manual procedure as described in the readme
> file. For direct development I will use a github repo, where I push mij
> code to. Are you pulling from there then into the libsigrok repo than?

For the record:  If the new-driver script in the past did not accept
how you tried to invoke it, sigrok-util 499931bffdd1 probably fixes
this issue for you.  The script now accepts driver names that consist
of multiple words again, as it did in a previous implementation.

If there is a different issue, please provide details, so we can fix it.


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.

------------------------------------------------------------------------------
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

Reply via email to