new FM demodulator

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/.

Nikos Balkanas nikos.balkanas at eyeonix.com
Thu Jan 30 16:43:27 UTC 2014


On Thu, Jan 30, 2014 at 6:13 PM, Alexandru Csete <oz9aec at gmail.com> wrote:

> On Thu, Jan 30, 2014 at 4:51 PM, Sdr Guru <sdrguru1 at gmail.com> wrote:
> > On Thu, Jan 30, 2014 at 5:23 PM, Alexandru Csete <oz9aec at gmail.com>
> wrote:
> >>
> >> On Thu, Jan 30, 2014 at 3:45 PM, Sdr Guru <sdrguru1 at gmail.com> wrote:
> >> > Hi
> >> >
> >> > Perhaps you can add a simple performance test to rtl_fm.
> >> > "decoding 100000 samples takes xxx ms" or something like that.
> >> > It helps to compare different CPU and OS families.
> >>
> >> We can already do simple benchmarking using the "time" command, or
> >> more detailed measurements using the "perf" tool that comes with the
> >> linux kernel.
> >
> > You can bring us some examples. Or write a guide.
> > Especially with "time" command.
>
> In a terminal you type:
>
> time rtl_fm
>
> with the rtl_fm parameters you want to use. When you stop the program
> it will print out how much real time has passed and how much time was
> used by the application. See "man time" for options.
>

Not the best way, unless you print #of packets processed and cpu is
limiting. A better choice would be gprof (Linux).

Nikos




> Alex
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20140130/73180f71/attachment.htm>


More information about the osmocom-sdr mailing list