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/.
Sipos Csaba sipos.csaba at kvk.uni-obuda.huHi, > Great. I'll see if I can make it part of the mailine code so you don't have to mess around with patch. Great, that would be nice. :-) I tried to compile the benchmark tool to measure what this card can do, but I hit a compilation error: root at TH-SDR1:~/gr-fosphor/gr-fosphor/lib/fosphor# make clean rm -f main *.o resource_data.c root at TH-SDR1:~/gr-fosphor/gr-fosphor/lib/fosphor# make gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o main.o main.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o resource.o resource.c ./mkresources.py fft.cl display.cl cmap_simple.glsl cmap_bicubic.glsl cmap_fallback.glsl DroidSansMonoDotted.ttf > resource_data.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o resource_data.o resource_data.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o axis.o axis.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o cl.o cl.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o cl_compat.o cl_compat.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o fosphor.o fosphor.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o gl.o gl.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o gl_cmap.o gl_cmap.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o gl_cmap_gen.o gl_cmap_gen.c gcc -Wall -Werror -O2 `pkg-config freetype2 glfw3 --cflags` -g -I/opt/AMDAPPSDK-2.9-1/include -c -o gl_font.o gl_font.c gcc -g main.o resource.o resource_data.o axis.o cl.o cl_compat.o fosphor.o gl.o gl_cmap.o gl_cmap_gen.o gl_font.o `pkg-config freetype2 glfw3 --libs` -lm -lOpenCL -lGL -ldl -o main cl.o: In function `cl_init_buffers_gl': /root/gr-fosphor/gr-fosphor/lib/fosphor/cl.c:469: undefined reference to `clCreateFromGLBuffer' cl.o: In function `fosphor_cl_process': /root/gr-fosphor/gr-fosphor/lib/fosphor/cl.c:875: undefined reference to `clEnqueueAcquireGLObjects' cl.o: In function `fosphor_cl_finish': /root/gr-fosphor/gr-fosphor/lib/fosphor/cl.c:938: undefined reference to `clEnqueueAcquireGLObjects' /root/gr-fosphor/gr-fosphor/lib/fosphor/cl.c:958: undefined reference to `clEnqueueReleaseGLObjects' cl_compat.o: In function `clCreateFromGLTexture_alt': /root/gr-fosphor/gr-fosphor/lib/fosphor/cl_compat.c:110: undefined reference to `clCreateFromGLTexture2D' collect2: error: ld returned 1 exit status make: *** [main] Error 1 The application (gr-fosphor) compiles and runs just fine. Maybe you know what am I missing. > I'm not exactly sure what you mean with the above picture. I mean that LTE (and many other RF technology) has a 10ms radio frame lenght, so it would be nice to be able to analyze that (like on the picture) on a radio frame level, rather than a continous stream. I think what you described is pretty much what I am asking for anyway :-) Thanks! Csaba ----- Original Message ----- From: "Sylvain Munaut" <tnt at 246tnt.com> To: "Sipos Csaba" <sipos.csaba at kvk.uni-obuda.hu> Cc: "Sylvain Munaut" <tnt at 246tnt.com>, osmocom-sdr at lists.osmocom.org Sent: Friday, February 27, 2015 2:01:45 PM Subject: Re: gr-fosphor: error: work group size exceeds the maximum default value for the selected device (AMD HD 5450) Hi, > Thanks mate, with your patch its working all right :-) Great. I'll see if I can make it part of the mailine code so you don't have to mess around with patch. > With Tom, we talked about a feature wich would be nice to have: a 10ms trigger so we can see something like this: > > http://tsou.cc/lte/openlte-spectro.png > > What do you think about it? I'm not exactly sure what you mean with the above picture. But something I'm thinking about it to have a return channel from the fosphor block that would basically feedback 'timestamps' of when the real time spectrum went above a given mask. Then I'm also working on another piece of code that's oriented toward "off-line" signal browsing (so it works on a time-limited number of samples rather than a continuous stream). And when a trigger event is hit, it would basically send off that chunk of sample to that other blow for viewing / browsing. I want them to be separate because the architecture of fosphor is oriented toward high rate real time display and so I have to sacrifice some other aspects to meet that. The other signal browsing block would be coded more with flexibility in mind. So in the end you'd have one display that represent the real-time of what's being recorded _right_now_ by your SDR, and then a second display that shows the last trigger event and allows you to browse around it, a bit like a scope does for time signals. Cheers, Sylvain