discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] WX GUI FFT Sink error


From: Josh Blum
Subject: Re: [Discuss-gnuradio] WX GUI FFT Sink error
Date: Tue, 15 May 2012 20:47:40 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1


On 05/15/2012 08:29 PM, Andrew Davis wrote:
> It's up to the driver writer to handle missing components properly,
> Mesa has a full software OpenGL stack, I never thought about it but
> i'll try using that and see what errors I get.
> 

I would like to be wrong, but as I recall, persistence was a non
standard thing. So drivers don't even bother to emulate it.

-josh

> On Tue, May 15, 2012 at 10:30 PM, Marcus D. Leech <address@hidden> wrote:
>>> It's not OpenGL, it's badly designed OpenGL drivers, saying OpenGL
>>> sucks is like saying C is slow, it can with a bad implementation, but
>>> by its self no. Back on topic, I too have had all sorts of problems
>>> like this with WX FFT, but it's a different error on each OS on each
>>> system 0_o. I have to just use Baudline for my FFT ( much more useful
>>> IMHO, but not open source :( )
>>>
>> Well, if OpenGL simple turns every rendering task I ask it to do and defers
>> to the hardware, then it isn't much good as a Graphics API.
>>  If, however, it's intended to simply be a universal API for rendering
>> *hardware*, then perhaps it's not appropriate to use it at all for
>>  simple, uncomplicated, 2D tasks such as those asked of it by Gnu Radio.
>>
>> But if OpenGL is intended to be an environment for rendering various
>> graphical concepts, using whatever optimizations happen to be
>>  available to it, or not, then it fails.
>>
>>
>> --
>> Marcus Leech
>> Principal Investigator
>> Shirleys Bay Radio Astronomy Consortium
>> http://www.sbrac.org
>>
>>
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



reply via email to

[Prev in Thread] Current Thread [Next in Thread]