Back
[12:37:50] <skunkworks> Could you put your irc history into the 18th? Maybe?
[12:50:14] <alex_joni> skunkworks: hard :)
[12:51:56] <alex_joni> http://www.embeddedarm.com/epc/wifi-h.htm <- yumm
[12:54:26] <skunkworks> alex_joni: no problem :)
[12:56:24] <alex_joni> skunkworks: check now
[12:56:38] <alex_joni> time doesn't match (I'm gmt+2-3, logger was on utc I think)
[13:02:44] <jepler> skunkworks: glad alex_joni was able to give it to you
[13:05:06] <alex_joni> hi jeff
[13:07:53] <skunkworks> alex_joni: perfect. (I never go by the time anyways)
[13:08:46] <Bo^Dick> at what address should the programarea start at when programming avrs?
[13:09:20] <skunkworks> jepler: I have a computer here that I am going to put head on and see what it does.
[13:09:40] <skunkworks> same exact hardware
[13:11:35] <alex_joni> Bo^Dick: usually at 0
[13:11:45] <alex_joni> because that's the address where it jumps to at reset
[13:12:01] <alex_joni> Bo^Dick: unless you have a bootloader already programmed in it
[13:15:14] <jepler> or unless you are programming a bootloader...
[13:16:11] <Bo^Dick> i know the reset vector is location at adress 0x0000
[13:16:57] <Bo^Dick> 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
[13:19:27] <jepler> 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
[13:19:42] <jepler> when using avr-gcc this all happened behind my back, it placed the first code or data at the right address
[13:20:17] <Bo^Dick> some programs tend to look like this: .org 0x0000 rjump RESET; RESET: inc r17; ldi r18,0x14; ...
[13:20:52] <jepler> do you mean that RESET: directly follows the instruction at 0?
[13:21:07] <Bo^Dick> that was what i was thinking about
[13:21:18] <alex_joni> it usually has another .org
[13:21:37] <jepler> 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
[13:22:00] <jepler> 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)
[13:23:51] <Stumpy> Stumpy is now known as dastumster
[14:46:53] <NickServ> This nickname is owned by someone else
[14:46:53] <NickServ> If this is your nickname, type /msg NickServ IDENTIFY <password>
[15:44:43] <Lerneaen_Hydra> 'lo
[15:47:19] <alpha-lappy> anyone using nvidia beta drivers?
[15:47:31] <cradek> I used them briefly but they crashed
[15:54:58] <SWPadnos> I use the released nvidia drivers
[15:55:28] <cradek> me too, but nvidia-installer --update gave me a beta last time
[15:55:29] <SWPadnos> not that that's helpful ;)
[15:55:36] <SWPadnos> interesting
[15:55:48] <cradek> then X crashed a lot
[15:56:09] <SWPadnos> I'll probably be putting my two computers back together this week/weekend, so I may be able to do some testing then
[15:56:19] <SWPadnos> both nvidia
[15:56:25] <cradek> sorry
[15:56:33] <SWPadnos> heh
[15:56:56] <SWPadnos> I snagged a Quadro FX3500 for $430 (and just missed a second one at $375-ish)
[15:57:06] <SWPadnos> those were $1200 3 months ago
[15:57:18] <cradek> (II) Module glx: vendor="NVIDIA Corporation"
[15:57:19] <cradek> compiled for 4.0.2, module version = 1.0.8762
[15:57:25] <cradek> this one is stable
[15:58:29] <SWPadnos> so - I finally deduced that I had two problems with my big machine
[15:58:50] <SWPadnos> 1) my firewire card is weird, and causes the system to not boot with most power supplies
[15:59:10] <SWPadnos> 2) the PC Power & Cooling silencer series is incompatible with the rev3 SuperMicro H8DCE
[15:59:24] <cradek> yuck
[15:59:30] <SWPadnos> all other power supplies seem to work though (including PCP&C turbocool series)
[15:59:53] <SWPadnos> but the only supply that can get the machine to boot with my firewire card is the one cfrom SuperMicro
[16:00:00] <SWPadnos> interesting, no?
[16:00:26] <cradek> maybe it has a curse
[16:00:34] <SWPadnos> luckily I had access to 5 power supplies, another firewire card, and several motherboards for this testing
[16:00:38] <SWPadnos> maybe
[16:01:14] <SWPadnos> 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"
[16:01:23] <SWPadnos> if only I had seen that first ;)
[16:03:12] <cradek> jepler was looking at reviews on that site yesterday, they're very funny
[16:03:21] <cradek> seems there's often not a lot of useful information in there
[16:03:52] <cradek> Cons: THIS ONE SUCKS YOU NEED A CACLE SATA EVEN AFTER LOOKING FOR IT FOR 2 DAYS IT DID NOT WORK THIS SUCKS
[16:03:56] <SWPadnos> heh
[16:09:09] <Lerneaen_Hydra> 'lo
[16:09:18] <Lerneaen_Hydra> oops
[16:10:37] <Lerneaen_Hydra> wth is a cacle?
[16:10:41] <Lerneaen_Hydra> sata cable?
[16:10:53] <cradek> yes that's my guess too
[16:12:37] <Lerneaen_Hydra> reminds me of this bash quote a bit
http://www.bash.org/?5300
[16:14:17] <cradek> crap now I have to click "random" a hundred times
[16:14:42] <Lerneaen_Hydra> :D
[16:16:35] <cradek> haha
http://www.bash.org/?9335
[16:18:32] <Lerneaen_Hydra> haha
[16:20:21] <Lerneaen_Hydra> http://www.bash.org/?699415
[16:20:59] <cradek> hmm
[16:21:15] <cradek> I had forgotten about that already
[16:21:43] <Lerneaen_Hydra> i wonder what really happened with that...
[16:22:22] <cradek> hard to say