Could you put your irc history into the 18th? Maybe?
skunkworks: hard :)
[12:51:56] <alex_joni> http://www.embeddedarm.com/epc/wifi-h.htm
alex_joni: no problem :)
skunkworks: check now
time doesn't match (I'm gmt+2-3, logger was on utc I think)
skunkworks: glad alex_joni was able to give it to you
alex_joni: perfect. (I never go by the time anyways)
at what address should the programarea start at when programming avrs?
jepler: I have a computer here that I am going to put head on and see what it does.
same exact hardware
Bo^Dick: usually at 0
because that's the address where it jumps to at reset
Bo^Dick: unless you have a bootloader already programmed in it
or unless you are programming a bootloader...
i know the reset vector is location at adress 0x0000
i was wondering for a suitable start adress for the main routing in the program so it doesn't collide with any interrupt vectors or other memory areas dedicated to other stuff
Bo^Dick: "after the last vector (you will use)" which is dependent on the AVR and prehaps even the interrupts you will enable in your software
when using avr-gcc this all happened behind my back, it placed the first code or data at the right address
some programs tend to look like this: .org 0x0000 rjump RESET; RESET: inc r17; ldi r18,0x14; ...
do you mean that RESET: directly follows the instruction at 0?
that was what i was thinking about
it usually has another .org
that would be appropriate only if the program enables no interrupts. otherwise, some of the other addresses near 0x0 will be used as interrupt vectors as well
the avr datasheets clearly document the number of vectors, and in my recollection they are all sequential starting at 0x0 (except for bootloaders, which have different rules)
Stumpy is now known as dastumster
This nickname is owned by someone else
If this is your nickname, type /msg NickServ IDENTIFY <password>
anyone using nvidia beta drivers?
I used them briefly but they crashed
I use the released nvidia drivers
me too, but nvidia-installer --update gave me a beta last time
not that that's helpful ;)
then X crashed a lot
I'll probably be putting my two computers back together this week/weekend, so I may be able to do some testing then
I snagged a Quadro FX3500 for $430 (and just missed a second one at $375-ish)
those were $1200 3 months ago
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8762
this one is stable
so - I finally deduced that I had two problems with my big machine
1) my firewire card is weird, and causes the system to not boot with most power supplies
2) the PC Power & Cooling silencer series is incompatible with the rev3 SuperMicro H8DCE
all other power supplies seem to work though (including PCP&C turbocool series)
but the only supply that can get the machine to boot with my firewire card is the one cfrom SuperMicro
maybe it has a curse
luckily I had access to 5 power supplies, another firewire card, and several motherboards for this testing
I noticed in a NewEgg comment on the H8DCE that "it doesn't work with the PCP&C supply, but once I switched that, it ws great"
if only I had seen that first ;)
jepler was looking at reviews on that site yesterday, they're very funny
seems there's often not a lot of useful information in there
Cons: THIS ONE SUCKS YOU NEED A CACLE SATA EVEN AFTER LOOKING FOR IT FOR 2 DAYS IT DID NOT WORK THIS SUCKS
wth is a cacle?
yes that's my guess too
reminds me of this bash quote a bit http://www.bash.org/?5300
crap now I have to click "random" a hundred times
[16:20:21] <Lerneaen_Hydra> http://www.bash.org/?699415
I had forgotten about that already
i wonder what really happened with that...
hard to say