Hi, Bert. Yes, right, I fully agreed what you've said. I also think duplicated codes are silly and evil things for a project.
I'm so sorry not to have enough communications before working. But at first, I didn't have enough confidence to make a working code, There are a few reasons to make a separated driver, but at this time, telling those things are meaningless. What I just want is supporting usbee dx, that's all, merging my patches are not important. Actually, I don't have confidence to modify fx2lafw driver without breaking current elegant style and without any problems. Stuffing two USB devices into the current fx2lafw driver will makes awkward codes. I think this driver is well-maintained, well-working driver. that's one of the reasons. So, I think you're the one of the authors of fx2lafw driver. could you make some changes to fx2lafw driver? As you saw, supporting usbee dx is not so difficult, that's a problem of how manage source codes. As you know, fx2lafwx file is a refactored parts of fx2lafw driver in a quick-and-dirty way. Still looks weird and needs more consideration, but please regard it as my small effort not to make duplicated codes. Best regards, Jong-Jin, Kim ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
