Bug 1025968
| Summary: | Rigol scope not detected | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Horák <dan> | ||||
| Component: | libsigrok | Assignee: | Alex G. <mr.nuke.me> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | mr.nuke.me | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | libsigrok-0.2.2-1.fc20 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-11-15 20:34:10 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dan Horák
2013-11-02 14:41:34 UTC
Created attachment 818601 [details]
update for upgraded Rigol DS1xx2 scopes
This is a patch to detect Rigol scopes with bandwidth upgraded to 150 MHz, I'm going to submit the patch to upstream.
I'm a provenpackager in Fedora, so if you give me green light, I can do the updates. Yeah, a cherry-pick of da970d24ecfcf67f89a9532f3a53ade8cb1131ed can go in right away. This can be a very frustrating issue. Thanks for reporting it. Green light. I'll have to ask that you submit your patch to upstream first. Upstream has some very funny ideas about modifying patches. Although I'm not a big fan of cherry-picking features, once they commit your patch, I see no reason not to cherry-pick it ourselves. patch sent upstream - http://thread.gmane.org/gmane.comp.debugging.sigrok.devel/659 patch now merged in the new unified rigol driver - https://github.com/martinling/libsigrok/commit/d1255c7f1bdec513c631fd7fbf93965871922200 - and should also go into current master libsigrok-0.2.1-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libsigrok-0.2.1-3.fc19 libsigrok-0.2.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libsigrok-0.2.1-3.fc20 libsigrok-0.2.1-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/libsigrok-0.2.1-3.fc18 and one more thing is needed - http://thread.gmane.org/gmane.comp.debugging.sigrok.devel/674 - discussed on IRC and on the way to git I've built libsigrok-0.2.1-4.fc21 with the fix from comment #9, but libsigrok-0.2.2 is behind the doors, so I'll wait with the other branches for the 0.2.2 release. and all updated to 0.2.2 now, per abi-compliance-checker results it's a safe update Package libsigrok-0.2.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libsigrok-0.2.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20590/libsigrok-0.2.2-1.fc20 then log in and leave karma (feedback). libsigrok-0.2.2-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. libsigrok-0.2.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. libsigrok-0.2.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |