Gods... I've found my addiction in full force again...

Me equipped with a Linux computer is... dangerous.

I've been optimizing the same fragment of code cheerfully in my spare time for the last month approximately.

Results? 256KB of lookup tables and another 60KB of object code... is now ~1KB object code... and 204 bytes of lookup tables. Brute force unrolled switch statement, meet hand-packed, hand-picked lookup tables. I still need to get hard figures for the code size, and finish rebuilding it into a state to finish submitting upstreak to zSNES, but for now I'm REALLY happy with myself. :-)

Meh... so close...

...I can get the open-source video-driver for my video-card in my laptop to compile.

It even loads correctly.

The windowing system refuses to activate it. Why? Because it detects the chipset as being in a set that it doesn't support.

Duh, that's why I got the bleeding-edge driver installed, shit-for-brains program.

I truly love software that refuses to do what you tell it to, and does 'what you want it to' instead. Especially when I have every single flag set on my system saying, "Gimme the unstable stuff! GimmeGimmeGIMME! I'll deal with the crashes!"

Then again, some would say that even having an Athlon 64 Linux Laptop should by default set those flags for me. =^.^=

Seperately... I'm still trying to sort out how to install the bleeding-edge wireless drivers. There's a minor glitch in the version that's easilly downloadable in the form of not being able to initialize on Athlon 64 systems that have more than 1GB of memory installed.

Yeah, I have 2GB. The hardware supports it, the software driver just doesn't yet. And there's no simple 'download this file and go' approach I've been able to find yet, unfortunately. They're moving their publically-available source-code repository from one server to another, so I can't get at the patch that fixes this. So... I either run cabled at 2GB, or run wireless at 1GB of RAM available. Meh. :-P