What is amazing is that when you hit Enter, the operating system is capable of fixing the lock and continuing with boot up. Which says the Raspbian people really don't want you running their OS unattended. They don't give a flying about headless. No, they want you right there in attendance for every...

My question stands, but I did find out no anisometric display on a normal HDMI monitor of 1920 x 1080 pixels. On my Asus monitor of 1920 x 1200, the stretching is very noticeable. Something in pi3d believes a monitor width of 1920 means 1080 units of height. I'll try to contact the author.

Nothing I can think to do corrects the anisotropy I see in my full screen display. Spheres look more like eggs. Any ideas where in the openGL or pi3d code this can be fixed?

Just wanted to say Thank You. Your posts are completely intelligible and helped me save more than the time it took you.

You are not an amateur. This may be late but one way to handle your case is demonstrated by this short script from picamera import PiCamera import sys try: camera = PiCamera() print 'handle normal, non-exceptional case' except: print 'handle exceptional case' finally: print 'join up. On with the sho...

I found pi-blaster was overkill for what I was looking for (accurate clock). I just wanted to post this link: http://panteltje.com/pub/ If you search for freq_pi.c or freq_pi-0.2.c on the page, Jan Panteltje has provide a c-level gpio clock generator that works well and covers a large range of frequ...

examine assembly code - or do a comparative timing of a million SPI transfers. Which is what I should have done rather than speculate here. Good point though, Joan.

*(gpioReg + GPCLR0 + PI_BANK) = PI_BIT;
sounds pretty much like
{*gpioSet = pin17;}
to me. But the former has two additions and two macros evaluated from what I can see. My optimization was trying to cut down on the c code executed. I could still be wrong, but...

In mmapGpio.h is see: void inline writePinHigh(unsigned int pinnum){*(this->gpio + GPFSET0) = (1 << pinnum);} void inline writePinLow(unsigned int pinnum){*(this->gpio + GPFCLR0) = (1 << pinnum);} which sounds real good and fast. I was wondering, if we were trying to achieve speed, perhaps at the ex...

Now I believe gpioTick() from pigpio's minimal_gpio.c (thanks joan) is the hammer that hits all nails. #include <sys/fcntl.h> /* O_RDWR, O_SYNC */ #include <sys/mman.h> /* mmap and options */ #define SYST_BASE 0x20003000 #define SYST_LEN 0x1C #define SYST_CLO 1 static volatile uint32_t *syst_reg; vo...

About 2 years ago Rasadmin may well have posted THE answer for your system. However, I vote for carlhage, because that solution worked for my late model Raspbian system (uname -r says '3.12.22+' with LXDE display manager). Don't put magic xset commands in /etc/rc.local as advised elsewhere. Use the ...

Richard, You have the power (should have the power) to modify your original post to note you no longer provide 'ready built' drivers at your git repository (unless I'm mistaken - still newish to git). That way newishbies won't read 8 pages of replies to be certain such was not already covered. OTOH,...

Regards the two samples I submitted. They were both run under X (I need my UI, man). In the second example callbacks are not involved. The loop only uses gpioTick and the gpioRead's and gpioWrite's. I believe joan is correct that the gpio reads and writes are susceptible to interrupts. That's the pr...

Regrettably I cannot resurrect the exact code nor breadboard setup I was using. However, I can still provide two samples (if I can post code correctly) that show the problem I think petzval is trying to overcome. The first sample is a modification of joan's code. Instead of sleeping while the square...

The pigpio library is certainly a marvel and a huge convenience, and if you stick to gpioRead (no writes) you can even get nearly reliable accuracy (repeatable performance). If you use gpioWrite, however, in even a simple loop, not as in the fast loop in minimal_gpio.c, you will see a very different...