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/.
Raj Bhattacharjea raj.b at gatech.eduI know this thread is a bit old, but it's worth mentioning that CL/GL sharing being enabled causes fosphor to be broken altogether on my setup as of the latest master commit (possibly earlier). Everything builds, but the following runtime error occurs: [!] CL Error (-5, /home/user/gr-fosphor/lib/fosphor/cl.c:480): Unable to share spectrum VBO into OpenCL context As previously mentioned, everything works okay if I change the value of FLG_FOSPHOR_USE_CLGL_SHARING in private.h to 0. Sylvain, do you always have the value of this flag as zero in your building and testing? Or do you leave it as 1 and fosphor works because you're using Intel CPU OpenCL or something? Maybe check in "#define FLG_FOSPHOR_USE_CLGL_SHARING (0<<0)" into the source repo until you can verify that this code path works correctly? Details of my setup: x86_64 (Xeon D) Ubuntu 16.04 NVIDIA Titan Xp NVIDIA Driver 375.66 from the standard Ubuntu (xenial-updates) nvidia-opencl-icl-375 from the standard Ubuntu repos I'm happy to test things out and will do some of my own debugging. On Tue, Feb 7, 2017 at 3:52 PM, Raj Bhattacharjea <raj.b at gatech.edu> wrote: > Sylvain, > > >> Ok, good to know. >> >> I need to come up with a good way to pass "options" to fosphor to be >> able to configure theses things at runtime. >> >> > That would be useful! Given how much I use your tool for real work, I'm > willing to contribute; do you look at pull requests on the github mirror? > Here are some other things I have often considered plumbing through as > options: > 1. FFT length. It looks like you have a length 512 FFT kernel in fft.cl > already, but I think its unused. A few other FFT sizes might be useful too > for adjusting resolution bandwidth. With what you have, several other > powers of two should be implementable simply. > 2. Waterfall time length. Requires some GL tricks to change the texture > size, or internally render at some fixed size and always crop and/or > downsample the texture to show the amount of time the user requested. > > Thanks for the tips that resolved the issue! > > -- > Raj Bhattacharjea, PhD > Georgia Tech Research Institute > Information and Communications Laboratory > http://www.prism.gatech.edu/~rb288/ > 404.407.6622 <(404)%20407-6622> > -- Raj Bhattacharjea, PhD Georgia Tech Research Institute Information and Communications Laboratory http://www.prism.gatech.edu/~rb288/ 404.407.6622 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20170620/80d52c06/attachment.htm>