00:37:07 | sammy | morning all... |
00:37:17 | prpplague | morning |
00:37:22 | prpplague | morning/night |
02:05:48 | sammy | Russ : ? |
02:06:03 | Russ | yes? |
02:07:01 | sammy | is that ramdisk need to match with the kernel version ? |
02:08:36 | sammy | or only upper then just can run ? |
02:09:49 | sammy | you know what I am saying , if don't forgive my poor english .. |
02:10:31 | Russ | if there are modules in the ramdisk, the modules need to have the same version as the kernel to work |
02:11:55 | sammy | what kind of modules ? |
02:15:51 | sammy | I am just download the ramdisk with jffs2 by erikm an try to make a ramdisk with jffs2 on LART ... |
02:16:01 | Russ | kernel modules |
02:18:57 | sammy | Amm...about this ? /lib/moduleskmod: failed to exec /sbin/modprobe -s -k char-major-4, errno = 2 |
02:19:14 | sammy | is that a problem with make kernel ? |
02:19:34 | sammy | or just the problem with the kmod ? |
02:21:27 | Russ | do the modules match the kernel? |
02:24:44 | sammy | I don't know , I use the ramdisk with |
02:24:45 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:24:48 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:24:51 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:24:55 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:01 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:07 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:13 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:19 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:25 | sammy | ramdisk-lart-minimal-new-tty.gz |
02:25:27 | sammy | I don't know , I use the kernel-2.4.9-ac10-rmk3 and with the ramdisk with ramdisk-lart-minimal-new-tty.gz ... |
02:27:19 | sammy | but , I don't know about the module very much ... and the LART at this place still can work |
02:27:59 | sammy | is that the problem so ? |
08:01:20 | seletz | hi! |
09:19:02 | sammy | is home now... |
13:14:36 | erikm | hi |
13:14:46 | erikm | hmm, I expected seletz to be here |
16:40:39 | Russ | hmmm....command history support wouldn't be very usefull unless it remembered things between boots |
16:41:58 | prpplague | Russ: something specific you refering to? |
16:42:28 | Russ | cvs commits |
16:42:35 | prpplague | ahh |
16:43:30 | prpplague | someone adding command history to blob? i'd agree with you on the usefullness |
18:10:36 | erikm | hi Russ |
18:13:13 | Russ|werk | hey erikm |
18:13:25 | Russ|werk | "<Russ> hmmm....command history support wouldn't be very usefull unless it remembered things between boots" |
18:13:30 | Russ|werk | "<prpplague> someone adding command history to blob? i'd agree with you on the usefullness" |
18:14:17 | erikm | what about my last proposal? (making a separate diagnostics tool) |
18:14:49 | Russ|werk | I don't know what you'd put in there |
18:15:23 | erikm | things like the memory tester etc. |
18:15:33 | Russ|werk | btw, resistor value for led = (vpp - forward voltage of led)/forward current of led |
18:15:36 | Russ|werk | right? |
18:15:44 | Russ|werk | erikm: just add them as extra commands |
18:15:59 | erikm | resistor value is OK |
18:16:22 | Russ|werk | it'd be easy enough to make a simple term program specifially for blob diag |
18:16:44 | erikm | like expect, you mean |
18:16:50 | Russ|werk | 52 ohms just seems a bit small |
18:18:01 | erikm | 470 ohm is usually enough for 10mA LED current and 0.7V forward voltage over LED |
18:18:18 | erikm | and 5V Vpp |
18:18:24 | Russ|werk | this led says 25mA @ 2V |
18:18:39 | Russ|werk | and its 3.3Vpp |
18:19:13 | erikm | hmm 52 ohm is correct in that case |
18:19:29 | Russ|werk | do I even need one? |
18:19:35 | erikm | you'd better |
18:20:29 | Russ|werk | now I just need to find the closest manufactured value |
18:20:47 | erikm | 47 ohm, or what's the next in the E12 range? 68 ohm, I think |
18:22:12 | Russ|werk | is there anything replacing tantalums? |
18:22:26 | Russ|werk | 68 and 47 sound right |
18:22:30 | Russ|werk | probably go with 68 |
18:23:45 | erikm | afaik there isn't anything replacing tantalums. jdb might know, but he's currently to a conference in zurich |
18:27:05 | erikm | anyway, about the command line history |
18:27:59 | erikm | I'm going to remove it, and I'll extend the command line parser so it recognises abbreviations |
18:28:22 | erikm | things like "do blob" |
18:28:25 | erikm | for "download blob" |
18:29:47 | erikm | I'll also restructure the code so seletz can put his diagnostics stuff in a separate package that you can download and start as if it is a linux kernel |
18:31:12 | erikm | because blob and "diag" share quite some code, I'll make a lib directory to put in the serial code, LED code, etc. blob and diag will link against this library |
18:31:54 | erikm | blob will be small and simple (like the goal was from the start), and diag can be more full featured |
18:32:44 | Russ|werk | hey WeirdArms |
18:32:49 | WeirdArms | hey |
18:33:32 | erikm | WeirdArms: eh, what time is it at your place? |
18:34:43 | WeirdArms | 5:30 am |
18:35:29 | WeirdArms | late or early |
18:35:35 | WeirdArms | whichever way you want to look at it |
18:35:45 | erikm | WeirdArms: woke up early, or not yet to bed? |
18:35:50 | WeirdArms | not yet bed |
18:35:55 | WeirdArms | Working on FASS |
18:36:06 | WeirdArms | trying to work out how to debug it |
18:36:55 | WeirdArms | and why Russel does some of the things he does |
18:37:03 | WeirdArms | ;) |
18:37:07 | WeirdArms | I sent him a patch |
18:37:21 | WeirdArms | he probably won't have time to look at it though |
18:38:20 | WeirdArms | you know it's fun when you disable the domain which tags the exception vector table |
18:38:22 | erikm | he's currently at Alan and Telsa |
18:38:28 | WeirdArms | infinite exception loop |
18:38:30 | WeirdArms | Wee! |
18:38:34 | WeirdArms | Yeah he said |
18:40:12 | erikm | he hoped for good weather, but yesterday evening they had already two "mild showers" as Telsa called it |
18:41:14 | erikm | mind you: he had to close the window or otherwise his bed would become soaking wet :) |
18:42:36 | WeirdArms | What's he doing there |
18:42:54 | WeirdArms | He said "I'm working from home at Alan's house, if that makes sense" |
18:43:03 | erikm | just visiting afaik. and some walking, if weather permits |
18:43:22 | WeirdArms | I want to know whats wrong |
18:43:29 | WeirdArms | I get a looping page fault |
18:43:40 | WeirdArms | I thought if a page fault fails you get a segfault |
18:44:00 | erikm | that's what I would think |
18:44:01 | WeirdArms | erikm: what you up to? |
18:44:12 | WeirdArms | I'll check if it is a bad fault |
18:45:25 | erikm | blob hacking. playing with the assabet. turns out the second assabet I got from Intel has a faulty jtag cable |
18:45:50 | WeirdArms | bummer |
18:45:57 | WeirdArms | but the other cable works? |
18:46:00 | erikm | yes |
18:46:08 | WeirdArms | Do you think you would be able to look at the PLEB flash stuff? |
18:46:10 | erikm | takes some time before you find out |
18:46:38 | erikm | I'm not sure. I'm currently completely restructuring the directory layout |
18:46:39 | WeirdArms | If you interested I can send you a patch for the FASS stuff too ;) |
18:46:43 | WeirdArms | ok |
18:47:21 | WeirdArms | trying to get it done for a mid nov paper deadline |
18:47:27 | erikm | seletz submitted command line history to CVS. jdb and I completely disagree with that, so I'll remove it |
18:47:31 | WeirdArms | Don't know how likely that is but damn I'm going to try |
18:47:44 | WeirdArms | yeah fix delete first :) |
18:47:55 | erikm | fix delete? what's wrong with delete? |
18:47:57 | WeirdArms | backspace doesn't work for me |
18:48:01 | erikm | huh? |
18:48:09 | WeirdArms | hmm |
18:48:14 | erikm | never had any problems with that |
18:48:15 | WeirdArms | might be my term |
18:48:36 | WeirdArms | hmm |
18:48:38 | WeirdArms | it works |
18:48:39 | WeirdArms | .... |
18:48:49 | erikm | you reparied the LART? |
18:48:55 | WeirdArms | no |
18:48:59 | WeirdArms | using pleb |
18:49:02 | erikm | ah |
18:49:13 | WeirdArms | with your life saving small ramdisk |
18:49:26 | erikm | hehe |
18:49:42 | WeirdArms | you can probably imagine how much that helps when I can't flash stuff |
18:49:54 | erikm | yeah, a *lot* smaller |
18:50:22 | WeirdArms | I probably could work it out, we have an old kernel patched to enable the flash but it would take me a day to track it down off someone and move it to the current kernel |
18:53:49 | WeirdArms | hmm |
18:53:56 | WeirdArms | I think the only time you get a repeated fault |
18:54:02 | WeirdArms | is when the page has been mapped in ok |
18:54:12 | WeirdArms | could be a caching issue |
18:54:30 | WeirdArms | do you know how to turn the cache off in linux erik? |
18:55:06 | erikm | yeah, play with the MMU |
18:55:28 | Russ|werk | what flash do you have? |
18:58:11 | erikm | WeirdArms: cache disable code is in arch/arm/boot/compressed/head-sa1100.S |
18:58:37 | WeirdArms | Intels 3v advanced+ boot block flash |
18:58:54 | WeirdArms | 2 * 2MB chips 32bit wide |
19:04:51 | Russ|werk | and blob isn't flashing it? |
19:05:44 | WeirdArms | I haven't written the flash code for it |
19:05:51 | WeirdArms | I tried the tuxscreen code |
19:05:54 | WeirdArms | that didn't work |
19:05:59 | Russ|werk | yah... |
19:06:05 | Russ|werk | use the lart code, but without the plaiting |
19:06:07 | WeirdArms | I thought the flash chips would be sufficiently similar |
19:06:14 | WeirdArms | same chips? |
19:06:22 | Russ|werk | the lart code is for intel flash, the tuxscreen code is for amd |
19:06:27 | WeirdArms | hmm |
19:06:32 | WeirdArms | yeah maybe I shoudl |
19:07:04 | erikm | Russ|werk: did I already explain you my plans to rewrite the flash code? |
19:07:45 | prpplague | howdy all |
19:07:48 | erikm | hi prpplague |
19:07:49 | Russ|werk | different files for differetn flash? |
19:07:59 | erikm | no, not necessary |
19:08:28 | erikm | suppose we want to write an image to the flash, we first start reading the flash |
19:09:03 | erikm | if we don't find 0xffffffff, we issue an erase command for that address which will erase the complete block |
19:09:23 | Russ|werk | hmm.... |
19:09:37 | Russ|werk | I would say just erase, I wouldn't trust 0xffffffff |
19:10:16 | erikm | keep on scanning and erasing until we have enough room for the image |
19:10:28 | erikm | oh, but it works |
19:10:47 | Russ|werk | what if it was a power loss during an erase |
19:10:59 | WeirdArms | hehehe |
19:11:02 | Russ|werk | or the first part of whatever it is, happens to be 0xffffffff |
19:11:12 | erikm | the code that copied blob from the LART external flash to the internal flash used this trick |
19:11:18 | WeirdArms | thats what I was wondering |
19:11:20 | erikm | we scan the whole block |
19:11:40 | Russ|werk | I've watched some mtd discussions on this sort of thing |
19:11:46 | erikm | the flash writer wouldn't even have an idea what a block is |
19:11:48 | Russ|werk | and it doesn't seem to be worth it |
19:11:51 | WeirdArms | using the LART flash code does the same as the TuxScreen one did |
19:11:56 | WeirdArms | it crashes blob |
19:12:02 | Russ|werk | WeirdArms: turn off the plaiting |
19:12:08 | WeirdArms | it is off |
19:12:28 | Russ|werk | suppose its time to pull out the data sheet and schematics tehn |
19:12:48 | WeirdArms | hehehe |
19:12:49 | prpplague | erikm: i looked back on the conversation about command line history, i like the final decision |
19:13:04 | WeirdArms | I just don't feel like working out the flash |
19:13:04 | erikm | prpplague: the separate diagnostics tool? |
19:14:28 | erikm | Russ|werk: so what could go wrong if we use my plan? |
19:14:49 | erikm | Russ|werk: especially if I CRC32 or md5sum the contents of the flash |
19:15:03 | Russ|werk | if you lose power during an erase |
19:15:15 | erikm | Russ|werk: ok, one block toast |
19:15:18 | Russ|werk | then read the area, and notice its all 0xffffffff |
19:15:23 | WeirdArms | you have a partial erase and you are not sure of the bundary |
19:15:35 | Russ|werk | when you go abck and read it again, it may not still be 0xffffffff |
19:15:41 | Russ|werk | the bits wobble around |
19:15:54 | erikm | Russ|werk: ok, something went wrong. so we program the flash |
19:16:09 | Russ|werk | how do you know something went wrong, you read all 0xffffffff |
19:16:21 | erikm | Russ|werk: after programming we md5sum the contents of the flash and detect something went wrong |
19:16:34 | Russ|werk | ? |
19:16:46 | Russ|werk | how do you md5sum an erased blockZ |
19:16:48 | Russ|werk | er, ? |
19:16:48 | erikm | user gets error "flash failed" |
19:17:10 | erikm | let me start from begin: |
19:17:12 | Russ|werk | I'm confused |
19:17:18 | erikm | 1. erase block |
19:17:27 | erikm | 2. power fails, block is half erased |
19:17:32 | erikm | 3. power on again |
19:17:40 | erikm | 4. download image |
19:17:47 | erikm | 5. flash image |
19:18:01 | erikm | 6. half erased block is detected as clean, so not erased again |
19:18:06 | erikm | 7. write image |
19:18:19 | erikm | 8. re-read image from flash and md5sum |
19:18:33 | erikm | 9. compare md5sum with md5sum from the image in memory |
19:18:37 | Russ|werk | just seems simpler to erase than to do all this checking and re-erasing reflashing |
19:18:59 | WeirdArms | :) |
19:19:21 | erikm | Russ|werk: no, the advantage of this approach is that the flash code doesn't have to have an idea about block boundaries |
19:19:35 | WeirdArms | is it such a big deal for it to know though? |
19:19:51 | Russ|werk | I see what you are trying to do there |
19:20:02 | Russ|werk | and it might be helpfull for the user to know that something didn't f lash right |
19:20:13 | erikm | Russ|werk: flashing blob >1k on LART already fails |
19:20:18 | erikm | 16k I mean |
19:20:18 | Russ|werk | skipping erases ends up being a side effect |
19:20:33 | prpplague | erikm: ya the seperate diagnostics and the shorten keyword recognition ie "do blob" |
19:20:56 | erikm | Russ|werk: *nod* |
19:21:10 | erikm | it's a side effect, but it makes the flash code blocksize agnostic |
19:21:23 | erikm | so it will work without any modifcation on all platforms |
19:21:35 | erikm | except the difference for commands, of course |
19:22:28 | prpplague | erikm: i've not finished my patch yet, this week has been crazy |
19:22:45 | erikm | prpplague: hehe, over here as well :) |
19:23:53 | erikm | prpplague: I've been giving courses in fundamental filter theory, fundamental sampling theory, and fundamental maths to coworkers :) |
19:25:36 | prpplague | erikm: fundametal filter theory? audio filtering or data filtering? |
19:26:18 | erikm | prpplague: things like: aliasing has to be dealt with immediately, you can't first put your data through an integrator and try to remove the aliasing effect afterwards |
19:26:41 | erikm | prpplague: there is no difference in audio filtering and data filtering for me |
19:28:14 | prpplague | erikm: true, the description just kinda points you in the intended application area |
19:28:48 | erikm | prpplague: but in this case it was about filtering data from accelerometers and gyroscopes |
19:29:18 | prpplague | erikm: lol, ok,ok |
19:29:43 | erikm | prpplague: sampled at 2000Hz, filtered and decimated to 100Hz (otherwise userland keep up with the speed) |
19:30:41 | WeirdArms | erikm: How's the trimedia chip thingy project going? Have they got anywhere? Has JDB got his crazy dual powerPC board done yet to outdo it? |
19:31:28 | erikm | WeirdArms: Sony UK made a quad trimedia board, don't know about the current status of the dual PPC board |
19:32:04 | erikm | WeirdArms: unfortunately sony wouldn't listen to our advice and put the cheapest PCI bridge on the board they could find |
19:32:54 | erikm | WeirdArms: a bloody transparent bridge, which will severely limit you in the amount of memory you can put in your host, especially if you want to put three our four quad trimedia boards in your host |
19:36:29 | WeirdArms | any guesses of the different between pte and ppte? |
19:37:02 | erikm | page table entry and pointer to page table entry? |
19:37:05 | WeirdArms | nope |
19:37:19 | WeirdArms | looks like hardware page table entry and linux page table entry |
19:37:47 | WeirdArms | printk(", *pte = %08lx", pte_val(*pte)); |
19:37:55 | WeirdArms | printk(", *ppte = %08lx", pte_val(pte[-PTRS_PER_PTE])); |
19:38:31 | WeirdArms | that looks like an offset the size of the leaf page entry away |
19:39:53 | WeirdArms | hmm |
19:39:59 | WeirdArms | the entry seems set to reserved |
19:40:03 | WeirdArms | which isn't good |
19:41:28 | erikm | WeirdArms: sorry, I don't know |
19:45:59 | erikm | decides between wisky and cognac |
19:46:06 | WeirdArms | cognac |
19:46:12 | prpplague | cognac |
19:47:23 | erikm | nope, wisky |
19:47:34 | WeirdArms | hehehe |
19:49:59 | erikm | life is good: bach's brandenburger concertos on the stereo, glass of single malt whisky within reach, and a new chair :) |
19:52:15 | erikm | I bought the chair by accident: I was at Ikea for a new lamp, tried the chair, and fell in love with it |
19:56:35 | WeirdArms | hmm |
19:56:39 | WeirdArms | this doesn't make sense |
19:56:48 | WeirdArms | it shouldn't be faulting |
19:57:39 | prpplague | lol |
20:02:48 | erikm | problems with the 'net, Russ|werk? |
20:05:29 | Russ|werk | xchat is acting "funny" |
20:08:00 | WeirdArms | argh! |
20:08:11 | WeirdArms | I found the bug but I'm too tired to focus |
20:08:28 | erikm | WeirdArms: write it down, go to bed |
20:08:36 | erikm | WeirdArms: and fix it tomorrow |
20:08:45 | WeirdArms | it is tommorow |
20:08:50 | WeirdArms | No i must fix it now |
20:57:39 | erikm | WeirdArms: bug already fixed? |
21:26:16 | prpplague | erikm: i think he's fallen asleep at the keyboard.... |
21:27:51 | erikm | prpplague: I think so, yes |
21:29:33 | prpplague | hmm paycheck time... |
21:51:37 | prpplague | erikm: howdy, i figured you were headed for some zzzz's |
21:51:52 | erikm | no, ISDN bailed out |
21:51:52 | WeirdArms | erikm: i hven't fixed the bug but I know exactly whats wrong and how to fix it ;) |
21:59:16 | erikm | goes zzz |
21:59:36 | prpplague | later |
21:59:44 | erikm | later |
22:45:44 | BZFlag | consider yourself LARTed needs to be "blob's your uncle" ;-) |
22:47:40 | Russ|werk | BZFlag: did you get a chance to test the bootp stuff in 0.9.6 yet? |