Yes, exactly. It was the reason I asked ASIX for both Sigma2 and Omega analyzers, to be able test both code paths in ASIX driver. According to Uwe we should refactor (update, fix, extend) existing asix-sigma driver instead of creating a new one.
Some code parts will be shared, some will be device dependent. Best regards Jan On Mon, Sep 5, 2016 at 4:23 PM, Gerhard Sittig <[email protected]> wrote: > On Mon, Sep 05, 2016 at 09:43 +0200, jry wrote: > > > > I restarted work on ASIX driver last week and I see sveral > > options: I can continue this week and we will see how it is > > going. If you are in hurry and/or Ondrej Zoubek/ASIX would > > agree, I can send you Sigma2 analyzer (and return Omega to > > ASIX). > > If I understand correctly, those two devices (Sigma2 and Omega) > are rather different. Having operational Sigma2 support does not > result in automatic availability of Omega support. So regardless > of who might continue development, both devices will be required. > > I'd assume that both the firmware as well as the protocol (and of > course the capabilities) will differ between those two models. > Does available documentation agree with this assumption? > Previous experiments suggest that the existing Sigma support > won't operate with Omega, even if the USB VID:PID check gets > adjusted. More than this must be needed, though I can't tell > more precisely in the absence of documentation ... > > > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/sigrok-devel >
------------------------------------------------------------------------------
_______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
