View Single Post
Old 07-18-2012, 12:39 PM   #228
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by twobob View Post
Spoooky weirdness.

For no reason that I can fathom the soundcard decided to play the buffer at the wrong rate.

The next time (after digging around for erronous code) it played at the right rate.
And all subsequent times

Here there may be dragons.
That is why I like talking directly to hardware chip registers (i.e. "bare metal"). You can skip most of that hidden weirdness buried in libraries. But I have been bitten at the low level by hardware initialization workarounds caused by parasitic transistors in the hardware, and you can see "interesting" hardware glitch workarounds in u-boot, and most device driver code too.

Anything with the complexity level of modern hardware devices and software libraries (like alsa) is going to be plagued with hidden weirdness in the seldom explored corners, that clever programming can usually hide from the consumer (in most "general usage" cases). But then again, it is those very weird behaviors that can often be exploited to root a device and add features to it.
geekmaster is offline   Reply With Quote