This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-sdr@lists.osmocom.org/.
Nick Foster bistromath at gmail.comI've been letting it autodiscover. --n On Mon, Mar 3, 2014 at 2:14 PM, Alexandru Csete <oz9aec at gmail.com> wrote: > I must be completely missing something... When you create your source > now, don't you already pass it a string with a device descriptor? > > On Mon, Mar 3, 2014 at 11:04 PM, Nick Foster <bistromath at gmail.com> wrote: > > Sure. I could explicitly set this, but it means now I need a separate > menu > > item or configuration switch for each Osmo source -- and there are a > bunch. > > Not the end of the world, just hoping for something easier. > > > > --n > > > > > > On Mon, Mar 3, 2014 at 2:02 PM, Alexandru Csete <oz9aec at gmail.com> > wrote: > >> > >> On Mon, Mar 3, 2014 at 10:35 PM, Nick Foster <bistromath at gmail.com> > wrote: > >> > Hi, > >> > > >> > gr-osmosdr is great at abstracting the device type, but now I find > >> > myself > >> > wishing to de-abstract. For instance: HackRF has large DC offset, so > I'd > >> > like the option to switch in a DC blocking filter when using that > >> > source. > >> > RTL dongles can't support more than 2.4Msps reliably, so I'd like to > be > >> > able > >> > to cope accordingly at initialization time. > >> > > >> > Is there a good way to retrieve, say, a string descriptor telling me > >> > which > >> > particular source I'm using? > >> > >> None that I know of, but aren't you the one who decides what device is > >> in use by passing e.g. "hackrf=0" as argument to the constructor? > >> > >> Alex > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20140303/0646a634/attachment.htm>