06:20:25 | Sammy | BZflag: I just got my Tux tool .... |
06:20:36 | Sammy | it's really cool .... |
06:22:08 | Sammy | BZFlag: some of my friend feel that's really cool , so he want me to sale one for him now... |
06:24:00 | Sammy | haha, so how's Tux left now ? |
06:26:23 | Sammy | some of them that already have one , said wants another one .... |
06:28:10 | Sammy | I told them before , this will be worth to order more then two ,they are too conservative ... |
06:30:54 | Sammy | but now , they believe , so here have 3, and want 4 ... |
06:31:06 | Sammy | er wait |
06:32:55 | Sammy | anyway , maybe next month I'll order again , keep that for me :D |
06:33:56 | BZFlag | over 600 left. |
06:33:58 | Sammy | BZFlag: oh, soem curious question , is that tuxscreen have black color ? |
06:34:43 | Sammy | if so , next time , I want a black one :) hehe.... |
06:34:51 | BZFlag | there were some black and some clear prototypes, but I have never had any. |
06:36:45 | Sammy | ok , never mind ^_^ |
07:25:01 | | Russ was last seen on #tuxscreen 36 minutes and 24 seconds ago, saying: we can do a vmlinuz on jffs2 [Thu Dec 6 06:48:37 2001] |
07:25:01 | Sammy | ibot: seen Russ ? |
07:25:18 | Sammy | Russ : ? |
07:30:07 | Russ | ? |
07:36:54 | Sammy | Sorry ,need to harry you again ... |
07:37:29 | Sammy | yesterday , I change what the erikm say , but sound like no use ... |
07:38:10 | Sammy | now have this kind of massage a lot ... |
07:38:13 | Sammy | Write error in obliterating obsoleted node at 0x00380744: -30 |
07:38:16 | Sammy | Write error in obliterating obsoleted node at 0x00380000: -30 |
07:38:53 | Sammy | and after this , also this massage ... |
07:39:11 | Sammy | Freeing init memory: 60K |
07:39:11 | Sammy | Kernel panic: No init found. Try passing init= option to kernel. |
07:42:02 | Sammy | I got some problem to be clear by partition , if my flash is 32MB (28F128J3A) , am I right to define this partition ? |
07:42:10 | Sammy | here is the define ... |
07:43:26 | Sammy | static flash_descriptor_t assabet_flash_descriptors[] = |
07:43:27 | Sammy | { |
07:43:28 | Sammy | { |
07:43:29 | Sammy | size: 2 * 128 * 1024, |
07:43:30 | Sammy | num: 1, |
07:43:31 | Sammy | lockable: 1 |
07:43:32 | Sammy | }, |
07:43:33 | Sammy | { |
07:43:34 | Sammy | size: 2 * 128 * 1024, |
07:43:35 | Sammy | num: 63, |
07:43:37 | Sammy | }, |
07:43:39 | Sammy | { |
07:43:41 | Sammy | /* NULL block */ |
07:43:43 | Sammy | }, |
07:43:45 | Sammy | }; |
07:44:14 | Sammy | ? |
07:45:14 | Sammy | I feel sounds not right . because the flash map , show like this => |
07:45:16 | Sammy | 1x 0x00040000, lockable |
07:45:17 | Sammy | 64x 0x00040000, not lockable |
07:45:18 | Sammy | Flash map: |
07:45:19 | Sammy | 0x00040000 @ 0x00000000 (256 kB), lockable |
07:45:28 | Sammy | until |
07:45:37 | Sammy | 0x00040000 @ 0x01000000 (256 kB), not lockable |
07:46:15 | Sammy | here only have 16MB right ? |
07:52:03 | Russ | don't you mean "63x 0x00040000, not lockable"? |
07:52:18 | Russ | er |
07:53:24 | Russ | how is there flash *at* 0x1000000 if its 16M? |
07:53:40 | Russ | flash should stop at 0xFFFFFF |
07:55:45 | Sammy | but I have 32MB flash ram , so if I set like this , strill wrong right ? |
07:58:05 | Sammy | Can you give me a example , how to normally partition the 32MB flash RAM ? |
08:17:00 | Russ | so you have 128 erase sectors, correct? |
08:17:14 | Russ | does the data sheet say that? does it say which are locable? |
08:19:29 | Sammy | no , I just guess first one is lockable , I have try don't lock every block before, but the result all the same ... |
08:33:57 | Russ | look at the datasheet for your flash |
09:57:25 | Sammy | I can't get any ieda in it .. check for me , help me some ... |
09:57:39 | Sammy | http://211.75.21.252/28F128J3A.pdf |
10:26:24 | erikm | morning, * |
10:29:12 | Russ | morning erikm |
10:29:14 | Russ | small update to your kernel in CVS guide |
10:29:44 | erikm | Russ: what's wrong? |
10:29:50 | Russ | cvs update -j linus_2_4_7 -j my_2_4_7 |
10:29:54 | Russ | should be: |
10:30:01 | Russ | cvs update -j linus_2_4_7 -j my_2_4_7 -dP |
10:30:10 | erikm | *nod* |
10:30:22 | erikm | I have "update -dP" in my .cvsrc :) |
10:30:35 | Russ | noticed when I added drivers/video/backlight/ |
10:31:07 | Russ | any chance you want to put something up about keeping your tree in sync with more than one sync? |
10:31:53 | Russ | (ie, if I want to maintain a set of 2.4 tuxscreen patches and a set of 2.5 tuxscreen patches) |
10:33:29 | Russ | btw, if sammy comes back, his flash datasheet essential says: |
10:33:39 | erikm | you can create multiple sandboxes |
10:33:39 | Russ | there are 128 blocks, all of which are lockable |
10:33:46 | erikm | ok |
10:34:16 | erikm | I guess you're going to do a sleep(n*3600), where n >=6 or so |
10:34:20 | Russ | in x16 mode the erase size in 64kB, and since he has interleaved chips, his erase size is 128kB |
10:34:32 | Russ | no study(4*3600) |
10:34:50 | Russ | total flash size is 128kB*128 = 16M |
10:34:57 | erikm | like assabet |
10:35:15 | Russ | I thought assabet had a 256kB erase size |
10:35:22 | erikm | you're right :) |
10:35:33 | erikm | just commited the changes to the CVS howto |
10:35:45 | Russ | so how do I sync changes between my sandboxes? |
10:36:31 | erikm | I think you want changesets, but unfortunately cvs doesn't have such a thing |
10:36:43 | Russ | should I learn bitkeeper? |
10:37:00 | erikm | somebody pointed me to http://www.cobite.com/cvsps/ , which adds changesets to cvs |
10:37:13 | erikm | haven't looked at it yet, but it looks useful |
10:37:36 | Russ | ah, so I could break stuff out easier |
10:38:01 | Russ | everytime I do a new realese, I have to extract hunks manually atm |
10:38:15 | Russ | but this would just let me say "backlight", "dsp", etc? |
10:38:22 | erikm | I haven't tried bitkeeper yet. |
10:39:16 | Russ | I haven't heard very much about it, other than people being upset about licensing details |
10:39:44 | erikm | yeah, I don't really like the "logging to big brother" idea |
10:41:05 | erikm | gets coffee |
11:34:13 | seletz | hi |
12:39:02 | erikm | hello |
13:21:10 | seletz | back |
14:06:14 | Russ | couldn't be simpler |
14:06:30 | Russ | simply by not sleeping, I turned a 7:40AM early morning final |
14:06:38 | Russ | into a late evening final |
15:16:55 | prpplague | morning all |
15:16:59 | prpplague | everyone been larted this morning? |
15:17:27 | erikm | morning prpplague |
15:17:52 | erikm | prpplague: Russ might be autolarted by lack of sleep |
15:19:15 | prpplague | lol |
16:21:38 | Russ | I just larted my phy361 final |
16:22:10 | Russ | and now getting ready for an operating systems final in 3 hours |
16:23:44 | erikm | phy361 == physics? |
16:24:11 | erikm | doesn't know US course codes |
16:24:49 | prpplague | Russ: cool, good luck |
16:25:01 | prpplague | is headed for barbados to clean a raid mess |
16:28:28 | Russ | modern physics |
16:29:59 | erikm | Russ: modern as in quantum theory, general relativity, etc? |
16:30:11 | Russ | right |
18:25:13 | sammy_wms | ho ho ...it's really cool ... |
18:26:05 | sammy_wms | BZFlag: tuxscreen can be the plone use over here ... |
18:26:13 | erikm | over here as well. I guess it's about 3 or 4 celcius |
18:26:56 | sammy_wms | hello erikm |
18:28:25 | sammy_wms | but few more days later , it's will change the OS running linux ,haha... |
18:28:31 | sammy_wms | really cool ... |
18:29:05 | sammy_wms | BZFlag: next month , I'll order another 4 ... |
18:30:34 | sammy_wms | erikm: Ah, tell you one more things , about the jffs2 yesterday you told me , but still can't work . |
18:31:35 | sammy_wms | erikm: "kernel panic : no init found , try input some init= command line ..." some massage like that ... |
18:31:48 | erikm | sammy_wms: check /etc/ld.so.cache |
18:33:52 | sammy_wms | yeap , already check ...first , there is no such file in /etc/ dir and then after ldconfig , here comes the file .... |
18:33:58 | sammy_wms | right ? |
18:34:04 | erikm | that's right |
18:34:33 | sammy_wms | so at this step , I _really_ do so , but..... |
18:41:12 | sammy_wms | erikm: if my flash is 32MB , how do I normal setup the partition ? |
18:43:18 | erikm | depends on the flash block size |
18:44:13 | sammy_wms | if that is flash is 28F128J3A , is that use 0x40000 be the block size ? |
18:45:14 | erikm | sammy_wms: you have a 128K block size |
18:45:39 | erikm | sammy_wms: (that's what Russ told me) |
18:45:43 | Russ | sammy looks to me like your flash is 16M |
18:46:15 | Russ | your data sheet says that in x16 mode, your erase blocks are 64kB, and with them interleaved, that makes a 128kB erase size |
18:46:29 | Russ | and in your chip, there are 128 erase blocks, making: |
18:46:42 | | 16777216 |
18:46:42 | Russ | ibot: 2 * 64 * 1024 * 128 |
18:46:46 | Russ | 16M |
18:47:05 | Russ | also, all of your sectors are lockable |
18:47:17 | Russ | its all in the datasheet |
18:47:55 | sammy_wms | which part is saying the lock or unlock ? |
18:48:11 | Russ | its on the couple of pages |
18:48:32 | sammy_wms | maybe I must say , it's hard for me to read the hw , |
18:49:09 | Russ | look at page 13, the memory map |
18:49:26 | Russ | its pretty clear how much flash there is and what the erase size is |
18:49:37 | Russ | er, wait, maybe I'm confused... |
18:50:01 | Russ | arghhh...it was really late when I read it |
18:50:10 | Russ | 64k*word* blocks in x16 |
18:50:12 | erikm | sammy_wms: you're lucky. intel data sheets are quite readable. try ALI data sheets in which case it's a question of "ok, page 25 says pin 15 must be high, but page 43 says it should be low. what's it gonna be?" |
18:50:37 | Russ | erikm: a 0 ohm jumper in the design? |
18:51:03 | Russ | so it is 256k*byte* erase blocks |
18:51:18 | Russ | and there are 128 of them, making 32M |
18:51:18 | erikm | Russ: basically two: one to Vcc, and one to Gnd. burn the one you don't need |
18:51:29 | Russ | right |
18:52:35 | sammy_wms | amm...so the erase blocks is 0x40000 right ? |
18:52:42 | Russ | yes |
18:55:31 | sammy_wms | checking the page 13 |
18:55:44 | | 33554432 |
18:55:44 | Russ | ibot: ((64 * 1024 * 16) / 8) * 2 * 128 |
18:56:45 | Russ | 11:58:17 up 9 days, 27 min, 6 users, load average: 0.21, 0.27, 0.14 |
18:57:40 | erikm | 19:58:37 up 1 day, 10:08, 6 users, load average: 0.43, 0.42, 0.30 |
18:58:08 | erikm | had to shut down during flight back home. -ENOBATTERYPOWER :( |
18:58:39 | Russ | oops |
18:58:42 | Russ | didn't mean to do -o |
19:07:12 | sammy_wms | Russ: how to know which mode is that I use ? if I got a chip and have choose like this ? |
19:11:43 | sammy_wms | oh, assabet only have 16 MB flash ? |
19:11:58 | erikm | sammy_wms: yes |
19:17:52 | sammy_wms | so , my flash size is double then it , I must set the size : 2 * 128 * 1024 and num:128 lockable:1 |
19:19:54 | sammy_wms | erikm : but at this how much size should I give it to RAMDISK_FLASH_LEN ? |
19:20:24 | erikm | sammy_wms: anything shorter than 4MB |
19:21:01 | erikm | sammy_wms: (and yes, that's a known bug) |
19:22:12 | sammy_wms | erikm: so now this part of setting maybe right for the chips ? |
19:24:18 | erikm | the RAMDISK_FLASH_LEN has nothing to do with the flash layout |
19:24:29 | erikm | that is: not *yet( |
19:25:34 | sammy_wms | I am try find a way to let the kernel stop panic .... |
19:26:07 | sammy_wms | if my jffs2 image is bigget then 4MB , what's will happen ? |
19:26:33 | erikm | sammy_wms: no, if your *RAMDISK* image is larger than 4MB. |
19:29:10 | sammy_wms | erikm: ok , what's will happen ? |
19:30:06 | erikm | sammy_wms: see the "large ramdisk" link on http://www.arm.linux.org.uk/developer/ |
19:30:13 | erikm | sammy_wms: large ramdisks just don't make sense |
19:33:05 | sammy_wms | some of my friend tell me he want to put some QT library into ramdisk, and I think the library normally almost about 3MB, so after build , the ramdisk must be over then 4MB , and it's must be right ? |
19:34:11 | erikm | sammy_wms: I repeat: large ramdisks don't make sense. period. |
19:34:55 | sammy_wms | ~O~ |
19:42:36 | sammy_wms | raining all night ... made the air feel so cold .... |
19:42:43 | | rumour has it time is 19:42:43 2001 |
19:42:43 | sammy_wms | ibot : time ? |
19:44:04 | | sammy_wms: Try a 4-letter station code (see http://weather.noaa.gov/weather/curcond.html for locations and codes) |
19:44:04 | sammy_wms | ibot : weather ? |
19:44:47 | | ACTION drifts off to sleep. |
19:44:47 | sammy_wms | ibot : sleep |
19:45:59 | sammy_wms | I also need that too ...- . - |
19:46:11 | sammy_wms | nite ... |
19:46:38 | sammy_wms | z.Z.z....2 |
21:15:10 | BZFlag | hacks up a jtag cable. |
21:15:21 | BZFlag | anyone used jflash on sa1110? |
21:15:36 | BZFlag | Russ: does your mtd/jtag detect chips? |
21:25:35 | Russ | as in different flash chips? |
21:26:07 | BZFlag | yeah. I'm looking to hook up to a sa1110/sa1111 device. |
21:26:19 | BZFlag | not sure what the flash on board is. |
21:26:26 | Russ | it does, but it will need to be rewritten for sa1110 |
21:26:34 | Russ | and your jtag interface |
21:26:46 | Russ | I have a funky homebrew isa card |
21:27:13 | Russ | good bit faster than a parallel port |
21:30:08 | Russ | outb(TMS << 1 | TDO) |
21:30:20 | Russ | TDI = inb() & 1 |
21:30:21 | Russ | (etc) |
21:30:34 | Russ | TCLK happens automatically |
21:43:04 | BZFlag | I've got the lart jtag dongle. |
21:43:10 | BZFlag | has anyone used it with that? |
22:58:33 | BZFlag | Russ: hmmm.... will jflash or your mtd/jtag handle multiple devices on the jtag chain? |
22:58:46 | BZFlag | looks like I've got 3 different devices on this one. |
23:42:10 | Russ | no, rmk has code for that though |