Absolutely. Developers only know what their own systems and those they have tested software on do. That is one of the major headaches with trying to debug software. Hardware has an untold number of revisions, combinations and timing considerations. Add those uncertainties to those introduced by the operating system, it's revisions and patches and all the programs on the computer and you have quite a difficult task to debug it all.
Feedback on what doesn't work and in depth debugging info (when available) can be a major help to the developers. Dave KU4B On Sun, 2010-04-25 at 21:12 -0400, Drax Felton wrote: > > Raspy audio: OK Subject dropped. I didn't intend to be a nuisance. > > > > Should I continue to report other bugs I find in Power SDR 2.x and the new > drivers? > > > > > > Drax, KB3X > > > > _______________________________________________ > Flexedge mailing list > [email protected] > http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz > This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used > for posting topics related to SDR software development and experimentalist > who are using alpha and beta versions of the software. _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
