| 00:34.24 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 00:35.00 | beewoolie-afk | peep |
| 00:37.10 | key2 | ? |
| 00:47.12 | *** join/#openjtag JoeLlama (i=snork@01-188.015.popsite.net) |
| 00:59.41 | [g2] | hey beewoolie-afk ! |
| 01:11.01 | beewoolie-afk | [g2]: Hey man |
| 01:11.10 | beewoolie-afk | I was just talking to ka6sox |
| 01:11.15 | [g2] | beewoolie-afk Hey dude |
| 01:11.16 | [g2] | cool |
| 01:11.17 | beewoolie-afk | .er.chatting |
| 01:11.22 | [g2] | sure |
| 01:11.29 | beewoolie-afk | I have a Q. |
| 01:11.34 | [g2] | I'm all ears |
| 01:11.36 | beewoolie-afk | My slug is crashing with a kernel panic. |
| 01:11.42 | beewoolie-afk | Have you ever see that? |
| 01:11.59 | beewoolie-afk | I know, no details, it's just that it was working fine until I started to add some new software. |
| 01:12.05 | [g2] | I've seen a couple in the last 1.5 years |
| 01:12.07 | beewoolie-afk | Now, it won't even do what it used to do. |
| 01:12.24 | beewoolie-afk | I get a panic within a few minutes of starting an NFS transfer. |
| 01:12.40 | [g2] | what happens if you revert ? |
| 01:12.42 | beewoolie-afk | I was getting all crazy with the slug. I installed apache2, php, and mysql. |
| 01:12.56 | ka6sox-office | nfs2 or nfs3? |
| 01:13.01 | beewoolie-afk | I'm moving my wiki to MediaWiki. Very nice stuff. |
| 01:13.09 | beewoolie-afk | ka6sox-office: Oh. I think it's nfs3. |
| 01:13.13 | [g2] | I've heard that with lots of stuff you run out of memory |
| 01:13.14 | beewoolie-afk | Not sure, tho. |
| 01:13.20 | ka6sox-office | beewoolie-afk, I"m moving to wikimedia too. |
| 01:13.26 | [g2] | mysql takes 50-80% of Mem by default |
| 01:13.37 | beewoolie-afk | I supposed, but I shut it all down and I still get the crash. |
| 01:13.39 | ka6sox-office | going home...bbl. |
| 01:13.45 | beewoolie-afk | ka6sox-office: ttfn |
| 01:13.49 | ka6sox-office | ttfn |
| 01:14.06 | beewoolie-afk | I know it's kinda sily, but I was just hacking around. |
| 01:14.17 | beewoolie-afk | It worked way better than I thought it would. |
| 01:14.20 | beewoolie-afk | Slow, but stable. |
| 01:14.23 | beewoolie-afk | Until today. |
| 01:14.48 | beewoolie-afk | Also, I've noticed that there is a lot of clock slew on the slug. |
| 01:15.13 | beewoolie-afk | I haven't gotten a real measurement, but it looks like it loses seconds a day. |
| 01:15.14 | [g2] | are you running NTP ? |
| 01:15.21 | beewoolie-afk | I just started to. |
| 01:15.35 | [g2] | I was accurate to lik 8-11 ppm |
| 01:15.45 | beewoolie-afk | Without NTP? |
| 01:15.52 | [g2] | no with NTP silly :) |
| 01:15.58 | [g2] | that was the drift |
| 01:16.04 | beewoolie-afk | Oh. With NTP it should all be good. |
| 01:16.09 | [g2] | nod |
| 01:16.33 | [g2] | I think there was some stuff about 33.000 versus 33.333 or 66.666 |
| 01:17.01 | beewoolie-afk | Hmm.. |
| 01:28.29 | beewoolie-afk | [g2]: I'm gonna let it cool down and see if that makes a difference. |
| 01:29.14 | [g2] | these boxes run pretty nicely |
| 01:29.23 | [g2] | the Loft are much faster though |
| 01:45.59 | *** join/#openjtag ByronT (n=byron-po@nslu2-linux/ByronT) |
| 01:54.36 | beewoolie-afk | [g2]: What version of the kernel are you running/ |
| 01:55.16 | [g2] | 2.6.13.4 |
| 01:55.46 | [g2] | but I'll probably be moving to 2.6.14 soon |
| 01:56.05 | [g2] | I picked up some ipw2200 MiniPCI cards |
| 01:56.14 | [g2] | and there's native support in 2.6.14+ |
| 02:09.31 | beewoolie-afk | [g2]: I saw that. Kinda cool that the OpenSource thing is starting to work on the hardware vendors. |
| 02:11.20 | [g2] | beewoolie-afk well I wouldn't say that |
| 02:11.50 | [g2] | I'd say Intel's wireless play flopped and they open source some stuff |
| 02:12.07 | [g2] | I _do_ like the click-through license MUCH better though |
| 02:15.16 | [g2] | nite all |
| 05:46.38 | *** join/#openjtag bullet (n=bullet@136.216.203.62.cust.bluewin.ch) |
| 09:42.33 | *** join/#openjtag ep1220 (n=NN@gate.epatec.at) |
| 12:34.12 | *** join/#openjtag DaKa (n=david@193.13.58.211) |
| 12:39.12 | *** join/#openjtag DaKa (n=david@193.13.58.211) |
| 13:24.31 | *** join/#openjtag key2 (n=key2@gob75-2-81-56-64-17.fbx.proxad.net) |
| 15:13.51 | *** part/#openjtag dwery-zzzz (n=dwery@nslu2-linux/dwery) |
| 15:15.07 | *** join/#openjtag vmaster_ (i=vmaster@p549B430C.dip.t-dialin.net) |
| 15:56.52 | *** part/#openjtag ep1220 (n=NN@gate.epatec.at) |
| 15:57.05 | *** join/#openjtag ep1220 (n=NN@gate.epatec.at) |
| 15:58.50 | *** join/#openjtag JoeLlama (i=snork@02-182.015.popsite.net) |
| 16:40.13 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 18:02.44 | prpplague | [g2]: i sure have hell of a time getting with beewoolie |
| 18:02.53 | prpplague | [g2]: seems like we are off by 12 hours |
| 18:08.56 | vmaster | hehehe |
| 18:10.12 | prpplague | vmaster: trying to get some patches added for apex |
| 18:10.40 | prpplague | vmaster: beewoolie is driving me nuts with short responses via email |
| 18:11.37 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 18:12.02 | prpplague | HA |
| 18:12.11 | prpplague | speak of the devils minions |
| 18:12.16 | prpplague | beewoolie-afk: ho ho ho |
| 18:12.25 | beewoolie-afk | prpplague: Hey man |
| 18:12.36 | prpplague | beewoolie-afk: whats the latest? |
| 18:12.49 | beewoolie-afk | I've got a sick slug. It's more green than usual. |
| 18:13.00 | prpplague | hehe |
| 18:13.06 | beewoolie-afk | Do you have a copy of the latest openslug firmware binary you can share? |
| 18:13.12 | [g2] | prpplague beewoolie-afk is right here :) |
| 18:13.19 | prpplague | beewoolie-afk: you get my last email with the question about the sdram boot stuff? |
| 18:13.22 | beewoolie-afk | The link online was broken last night. |
| 18:13.29 | beewoolie-afk | Let me check.... |
| 18:14.35 | beewoolie-afk | prpplague: I don't see it. I'm checking the spam folder. |
| 18:14.59 | beewoolie-afk | Not there either. |
| 18:15.02 | prpplague | odd |
| 18:16.18 | prpplague | beewoolie-afk: otw |
| 18:16.27 | [g2] | beewoolie-afk is there a kenel debug flag to be verbose about what's happening at calling init ? |
| 18:16.35 | [g2] | right after mounting the rootfs |
| 18:16.45 | beewoolie-afk | I've been clearing out space so that I can run the monotone VCS and build openslug. |
| 18:17.07 | prpplague | [g2]: only by enabling kernel debugging and adding a printascii to the printk function |
| 18:17.13 | beewoolie-afk | [g2]: I don't know what you mean. Calling init is just a matter ofstarting a program. |
| 18:17.28 | beewoolie-afk | [g2]: What are you trying to do? |
| 18:17.30 | [g2] | beewoolie-afk I know but it's failing on my uClibc rootfs |
| 18:17.35 | [g2] | init=/bin/sh |
| 18:17.41 | prpplague | [g2]: or atleast thats the only way i know of |
| 18:17.42 | [g2] | doesn't put me in the shell |
| 18:17.50 | beewoolie-afk | Usually, it's a library problem. Did you check ldd? |
| 18:18.19 | beewoolie-afk | If it doesn't work, sometimes I insert a printk (no DEBUG_LL needed) to tell me what programs it is starting. |
| 18:18.37 | beewoolie-afk | Generally, it's just that the executable cannot be started due to a missing link library. |
| 18:18.48 | [g2] | no I didn't check ldd but I think it's a library problem too |
| 18:18.58 | beewoolie-afk | [g2]: BTW, what happenedto the openslug binary download? |
| 18:19.08 | [g2] | dunno. |
| 18:19.24 | [g2] | I've kinda been out of the openslug loop |
| 18:19.30 | beewoolie-afk | Oh. It came back. |
| 18:20.01 | beewoolie-afk | [g2]: How are you bootstrapping? |
| 18:20.39 | [g2] | bootstrapping the Loft ? |
| 18:21.10 | [g2] | I'm in Nirvana with the Loft |
| 18:21.12 | beewoolie-afk | Well, we have been using a flash filesystem as a recovery tool and bootstrap into a full install. loft or slug. |
| 18:21.48 | [g2] | with the Loft I stick a CF in and go load -r -v -b 0x1600000 -m disk hda1:/boot/zImage |
| 18:22.09 | [g2] | and that loads the kernel from the ext2/3 CF |
| 18:22.15 | beewoolie-afk | Oh. You've got an extra input method. Still, don't you put something in flash for recovery? |
| 18:22.41 | [g2] | well besides 16MB of strataflash, I've got JTAG |
| 18:22.51 | [g2] | and serial |
| 18:22.56 | beewoolie-afk | True. Do you use flash? |
| 18:23.00 | [g2] | 2 serial ports actually |
| 18:23.06 | [g2] | sometimes |
| 18:23.10 | [g2] | fis load zimage |
| 18:23.12 | beewoolie-afk | Ok OK. So you're phat. |
| 18:23.16 | [g2] | fis load zimage26 |
| 18:23.31 | [g2] | It's almost like GRUB |
| 18:23.47 | [g2] | I've got fconfig too for scripting |
| 18:24.17 | beewoolie-afk | In other words, you don't use openslug at all anymore?? |
| 18:24.36 | [g2] | not for a couple months |
| 18:24.47 | [g2] | I've got BE sarge running |
| 18:24.53 | beewoolie-afk | Hmm. The binary I downloaded appears to be broken. |
| 18:25.07 | beewoolie-afk | right. But I still need something to get sarge booted. |
| 18:25.29 | [g2] | just a kernel for me |
| 18:25.43 | [g2] | when running sarge it's often |
| 18:25.50 | [g2] | fis load kernel |
| 18:25.51 | beewoolie-afk | Yeah. It's easier and safer without the slug's limits. |
| 18:26.09 | [g2] | exec -c ".... root=/dev/sda1 rootdelay=12 .... |
| 18:26.31 | beewoolie-afk | I noticed that someonee took my work on the intel access library and has produced a kernel patch for LE support. |
| 18:26.34 | [g2] | My web site is running and old Debian Slug |
| 18:26.48 | [g2] | yeah guys are running LE |
| 18:26.52 | beewoolie-afk | That's what I'm trying to do, but the slug has gone south. |
| 18:27.09 | beewoolie-afk | I think that the OS is corrupted. |
| 18:27.28 | [g2] | do you have serial ? |
| 18:27.38 | beewoolie-afk | Yeah. |
| 18:27.41 | beewoolie-afk | I'm not lost. |
| 18:27.49 | [g2] | then just reload a kernel |
| 18:27.53 | beewoolie-afk | I just want to do another setup to see if a different slug has the same problems. |
| 18:28.03 | beewoolie-afk | That would also load a new kernel. |
| 18:28.16 | [g2] | reflash is your friend |
| 18:28.22 | beewoolie-afk | Oh, I know. |
| 18:28.33 | beewoolie-afk | The thing is, it's a little tough to get the pieces to flash. |
| 18:28.47 | beewoolie-afk | Besides, I doubt that the kernel in flash is wrong. |
| 18:28.55 | beewoolie-afk | I suspect that something on the HD changed. |
| 18:29.04 | [g2] | then just unplug |
| 18:29.26 | [g2] | don't mind me I'm just typing too fast :) |
| 18:29.47 | [g2] | it does fall back to the jffs2 partition though |
| 18:29.58 | beewoolie-afk | unplug? Oh. That works fine. The troble is that I don't know why the debian system crashes. |
| 18:30.26 | [g2] | set -x in it linuxrc |
| 18:30.35 | [g2] | s/it// |
| 18:30.49 | beewoolie-afk | Let me be moreclear. The system boots and I can get a login. |
| 18:31.10 | beewoolie-afk | I can even mount it via NFS. But when I start using it, the system crashes. |
| 18:31.26 | [g2] | Ok so NFS has issues |
| 18:31.37 | [g2] | if you don't mount NFS then it's stable ? |
| 18:32.09 | beewoolie-afk | Don't know. |
| 18:32.24 | beewoolie-afk | I've been using NFS for more than a month without incident. |
| 18:33.28 | [g2] | does debian have an install log ? |
| 18:33.40 | [g2] | like gentoo's emerge.log |
| 18:34.01 | beewoolie-afk | I think there is a way to see what's been installed. I've never looked. What are you thinking? |
| 18:35.05 | [g2] | I'm wondering if you can just see what you installed in the last 24/48 hours |
| 18:35.33 | [g2] | I've been playing around with SD |
| 18:35.38 | beewoolie-afk | Hmm. |
| 18:36.01 | [g2] | there's a physical Lock mechanism on most |
| 18:36.14 | [g2] | a hw RO system |
| 18:37.25 | [g2] | it would be nice to play with unionfs |
| 18:37.36 | [g2] | then allow changes to be saved each day |
| 18:37.58 | beewoolie-afk | Sounds reasonable. |
| 18:38.23 | [g2] | then you could "rollback" |
| 18:38.43 | [g2] | that'd be a good name for the disto |
| 18:38.49 | [g2] | Rollback linux |
| 18:38.53 | beewoolie-afk | Well, I shutdown all of the new services. |
| 18:39.30 | [g2] | right but obviously something else is effected |
| 18:39.45 | beewoolie-afk | But this is a kernel panic. |
| 18:39.57 | beewoolie-afk | That isn't a user-space kind of problem. |
| 18:40.32 | [g2] | so it's a panic not a silent crash ? |
| 18:43.14 | prpplague | beewoolie-afk: basically i was just curious about whether you though i really needed to init the rs-232 interface even during a sdram boot |
| 18:43.17 | beewoolie-afk | I see a kernel panic message. |
| 18:44.13 | lennert | where is it panicking? |
| 18:46.19 | beewoolie-afk | lennert: it ishard to say. I'm still getting the spurrious irq messages. |
| 18:46.26 | beewoolie-afk | It happens right after one. |
| 18:46.44 | lennert | spurious irqs on ixp4xx is hard if not impossible to solve |
| 18:48.28 | beewoolie-afk | I thought that the solution was to ignore them. |
| 18:48.54 | lennert | well, yeah, the warning needs to be silenced because there is no good solution |
| 18:49.32 | beewoolie-afk | Right. I just mean that I'm running a kernel that doesn't suppress them. |
| 18:50.19 | beewoolie-afk | I could get an ooops report and see where there crash is happening. |
| 18:50.38 | lennert | Yeah. My 'spurious irqs on ixp4xx is hard if not impossible to solve' was a random thought in context. |
| 18:50.46 | lennert | that would help |
| 18:50.58 | beewoolie-afk | Let me boot it up. |
| 18:58.17 | beewoolie-afk | Hmm. Not crashing now. I think that part of the problem was that I had some hanging NFS sessions. |
| 18:58.49 | lennert | okay |
| 18:58.54 | lennert | if you see it again, do let me know |
| 18:59.44 | beewoolie-afk | k. |
| 19:02.31 | beewoolie-afk | lennert: I was running a wiki on this little box, so I'll try it again. |
| 19:02.39 | prpplague | beewoolie-afk: do you want me to resubmit the patch with the rs-232 init code prior to the sdramboot section? |
| 19:04.20 | beewoolie-afk | prpplague: yeah. The idea is that APEX should work completely if it is run from SDRAM. Init of the uart and other devices should be correct. You may not know the state of the system. |
| 19:04.32 | beewoolie-afk | prpplague: Moreover, the uart init ought to be in the driver and not in the init- code. |
| 19:04.51 | prpplague | beewoolie-afk: hmm |
| 19:05.30 | prpplague | beewoolie-afk: just out of curiosity how would you be running apex directly from sdram without already having the rs-232 init'd ? |
| 19:05.33 | beewoolie-afk | prpplague: the uart init in the startup routine is there for debug only. |
| 19:05.42 | beewoolie-afk | JTAG. |
| 19:06.16 | beewoolie-afk | You also don't know what performed the init. It may not be compliant with what the system needs. |
| 19:06.22 | prpplague | beewoolie-afk: ahh, thats something i don't normally do, i always get flash working first |
| 19:06.42 | beewoolie-afk | The idea is that we want to guarantee, to the best of our ability, that the system is in the state that we need. |
| 19:07.05 | beewoolie-afk | prpplague: That's you, but there is no guarantee that others will do the same. |
| 19:07.41 | prpplague | beewoolie-afk: i meant only that i didn't think of it due to the fact that we don't dev in that way, not that its not a feasible item |
| 19:08.17 | beewoolie-afk | The contract is this: after APEX starts, the system is in a known state for the OS. |
| 19:08.42 | beewoolie-afk | Anything that we don't do could mean that the system won't run. |
| 19:09.41 | beewoolie-afk | UART init belongs in the driver. |
| 19:11.24 | *** join/#openjtag JoeLlama (i=snork@01-124.015.popsite.net) |
| 19:12.05 | prpplague | beewoolie-afk: ok |
| 19:17.42 | prpplague | beewoolie-afk: btw, another "feature" i'm working on is adding a micro load option, which builds just enough of apex to init an interface like the sd/mmc and copy the bootloader, kernel, and rootfs to flash |
| 19:18.07 | prpplague | beewoolie-afk: is that something you want submitted? or should i not bother? |
| 19:22.57 | prpplague | beewoolie-afk: updated patch otw |
| 19:31.55 | prpplague | beewoolie-afk: still there d00d? |
| 19:38.16 | beewoolie-afk | yeah. |
| 19:38.41 | beewoolie-afk | How small is micro? |
| 19:38.47 | prpplague | 1-2k |
| 19:38.56 | prpplague | 3max |
| 19:39.01 | beewoolie-afk | I'm not sure how that's apex at all. |
| 19:39.21 | prpplague | beewoolie-afk: its not really, just helps to have it all in one place |
| 19:39.28 | beewoolie-afk | Is this for keeping a NAND flash image small? |
| 19:39.44 | prpplague | beewoolie-afk: keeping the initial load via jtag small |
| 19:40.02 | prpplague | beewoolie-afk: when you are building 5000 units, jtagin takes time |
| 19:40.05 | beewoolie-afk | For faster manufacturing? |
| 19:40.11 | prpplague | yea |
| 19:40.22 | beewoolie-afk | How long does 16K take to download? |
| 19:40.37 | prpplague | 3 minutes |
| 19:40.47 | beewoolie-afk | Ouch. That's slow jtag. |
| 19:40.56 | beewoolie-afk | Why so slow? |
| 19:41.15 | prpplague | several reasons |
| 19:41.36 | prpplague | parallel port, 16 bit flash |
| 19:42.13 | beewoolie-afk | If you are manufacturing, don't you think it makes sense to use a faster JTAG interface? |
| 19:42.26 | beewoolie-afk | This isn't to say that it is a bad idea to write a boot-strap. |
| 19:42.39 | beewoolie-afk | I just wonder how it makes sense to put this in apex. |
| 19:42.48 | beewoolie-afk | It sounds like a targeted application. |
| 19:43.00 | prpplague | one sec phone |
| 19:43.04 | beewoolie-afk | k. |
| 19:44.03 | prpplague | beewoolie-afk: yea we have discussed designing a faster jtag, but we have lots of legacy devices and we already have the jtag dongles built |
| 19:44.14 | beewoolie-afk | right. |
| 19:44.25 | beewoolie-afk | Classic legacy problem. |
| 19:44.39 | prpplague | beewoolie-afk: my main thought in doing it with apex is that i will have about 5-6 different processors that will eventually be supported in apex |
| 19:44.52 | prpplague | beewoolie-afk: i would like to use the same microloader design for all of them |
| 19:45.00 | beewoolie-afk | How is the user going to select the right startup? |
| 19:45.09 | prpplague | beewoolie-afk: hence trying to standardize the process so i do have to keep writing it from scratch |
| 19:45.30 | beewoolie-afk | Ok. what in APEX is valuable for this project? |
| 19:45.38 | *** join/#openjtag Tiersten (i=tman@nslu2-linux/Tiersten) |
| 19:45.58 | beewoolie-afk | The biggest components are the FS drivers and the mechanisms used to load services and drivers. |
| 19:46.05 | prpplague | beewoolie-afk: severalt things, first, the support for the different file systems, second, the support for the automated copies |
| 19:46.08 | beewoolie-afk | printf is really big. |
| 19:46.20 | beewoolie-afk | You aren't going to get an FS driver in 3K. |
| 19:46.37 | prpplague | hmm |
| 19:46.45 | beewoolie-afk | Look at the object files. |
| 19:46.54 | prpplague | one sec conference call just started |
| 19:46.58 | beewoolie-afk | The only thing I've been trying to do is get thumb instructions. |
| 19:46.59 | beewoolie-afk | k. |
| 19:48.14 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 19:48.41 | prpplague | beewoolie-afk: ok done, sorry, short call |
| 19:49.15 | prpplague | beewoolie-afk: well i could get by with something small_er like 8-10k |
| 19:49.33 | vmaster | prpplague: what are those 5-6 different processors? variants of arm? or different architectures? |
| 19:49.43 | prpplague | all arm |
| 19:50.12 | vmaster | and currently you flash them using jtag-tools? |
| 19:50.13 | prpplague | however there was talk of doing a mips board |
| 19:50.33 | prpplague | vmaster: no i usually write a small app to do the job |
| 19:51.25 | prpplague | vmaster: although i usually get jtag-tools working with the boards |
| 19:51.25 | vmaster | ok, but using the boundary-scan approach? 3 minutes for 16k sounds like it |
| 19:51.25 | prpplague | vmaster: i usually optomized the flash routines |
| 19:51.28 | beewoolie-afk | prpplague: This is with single-byte programing, too. Right? |
| 19:51.52 | prpplague | basically just bitbanging the flash interface |
| 19:52.08 | vmaster | beewoolie-afk: it's not so much single-byte vs. block, but about using boundary-scan vs. processor logic |
| 19:52.19 | prpplague | vmaster: yea no processor logic |
| 19:53.01 | beewoolie-afk | vmaster: I think they also cannot write blocks |
| 19:53.31 | prpplague | i suspose if i make an extra small version of apex that would probably be enough |
| 19:53.54 | beewoolie-afk | prpplague: IMHO, this deserves more attention. |
| 19:54.07 | beewoolie-afk | prpplague: Perhaps you'd be better off writing something that could activate a serial transfer. |
| 19:54.15 | beewoolie-afk | That could be really small. |
| 19:54.33 | vmaster | even my "naive" flashing achieves 500-1000 bytes / sec using a wiggler |
| 19:54.44 | prpplague | beewoolie-afk: yea, i already have an app that is just 2k that inits the sd/mmc interface and copies the other items from there, but no fs support |
| 19:55.20 | prpplague | i was considering adding some very small fat16 code that i have |
| 19:55.33 | beewoolie-afk | You could init SDRAM and the serial interface, add xmodem and be able to download the loader over the wire. |
| 19:56.21 | prpplague | beewoolie-afk: yea |
| 19:56.28 | beewoolie-afk | that would be only 3K. |
| 19:56.34 | beewoolie-afk | xmodem is kinda big, too. |
| 19:56.45 | vmaster | how much is the whole download? |
| 19:57.03 | beewoolie-afk | As I wrote, I'd really like to get thumb working to reduce the code size. |
| 19:57.07 | prpplague | beewoolie-afk: roughly 1.5mb with bootloader, kernel, and rootfs |
| 19:57.12 | prpplague | beewoolie-afk: yea |
| 19:57.13 | beewoolie-afk | vmaster: the whole loader could be 30K. |
| 19:57.39 | vmaster | beewoolie-afk: i was refereing to what prpplague has to download (1.5mb) |
| 19:57.45 | beewoolie-afk | ah, |
| 19:58.21 | prpplague | vmaster: the initial load of the device is a diagnostic kernel and ramdisk that we will use to do a burning |
| 19:58.24 | prpplague | burnin |
| 19:58.57 | prpplague | vmaster: prior to shipment a util in the ramdisk will fetch a new kernel and ramdisk via a wireless interface |
| 19:59.01 | beewoolie-afk | prpplague: I'd be inclined to do a setup that gives you network access so that the whole process could be automated. |
| 19:59.31 | vmaster | hmm, ok - i wanted to see if doing the whole download through jtag would save you a lot, but with >1mb you'd need more than parport, no matter if you use processor logic and ram buffers or not |
| 19:59.36 | prpplague | beewoolie-afk: yea we are considering that as well |
| 19:59.48 | prpplague | vmaster: yea |
| 20:00.32 | prpplague | beewoolie-afk: problem we have is not all of our devices have the same net interface and some don't even have net |
| 20:00.40 | prpplague | beewoolie-afk: but they all have sd/mmc |
| 20:01.39 | beewoolie-afk | prpplague: From my perspective, the big win is in automation. You could reduce some of the steps, but the more you can do in batch and without intervention, the faster you can do a large batch. |
| 20:01.45 | beewoolie-afk | Henry Ford did it first. |
| 20:05.12 | vmaster | prpplague: are they all arm7/arm9? or xscale, too? |
| 20:05.43 | prpplague | beewoolie-afk: yea the main boards are plugged into a test bed that already has the sd card in them |
| 20:06.09 | prpplague | vmaster: arm7 and arm9 right now, with arm11 in the future |
| 20:06.43 | prpplague | vmaster: no xscale |
| 20:07.06 | prpplague | vmaster: intel is a beoych to work with for companies our size |
| 20:07.45 | vmaster | mhh, with a ft2232c i can write to target ram at 25kb/s - with the overhead for transfering the flash code and the actual flash write, you could probably flash at >20kb/s |
| 20:08.29 | vmaster | < 90s until all of the 1.5mb are inside your flash, with no human interaction |
| 20:08.33 | prpplague | vmaster: yea i actually have a ez-usb based device that i get great performance with, but we have a legacy issue |
| 20:08.44 | prpplague | vmaster: management doesn't want to change the jtag interface |
| 20:08.49 | vmaster | hehehe, ok |
| 20:09.10 | vmaster | didn't get what "legacy" meant 30min ago |
| 20:09.14 | prpplague | ahh |
| 20:09.42 | prpplague | vmaster: we already have all the parallel port dongles and test beds made |
| 20:09.45 | beewoolie-afk | prpplague: Do you have to use the legacy device for the test-bed? |
| 20:09.51 | beewoolie-afk | Oh. |
| 20:10.11 | vmaster | ok, gotta go - cya |
| 20:10.19 | prpplague | beewoolie-afk: they represent a pretty big investment |
| 20:11.34 | prpplague | beewoolie-afk: i'll probably present 3 options to they, custom micro loader, micro version of apex, and just an extra small version of apex |
| 20:11.56 | prpplague | beewoolie-afk: after discussing with you guys i suspect that just the extra small apex will be acceptable |
| 20:13.03 | prpplague | beewoolie-afk: btw, does the ";" function work now? |
| 20:13.37 | beewoolie-afk | prpplague: For your constraints, I'd recommend a second build target. |
| 20:13.49 | beewoolie-afk | You can use the code in apex to link in the drivers you need. |
| 20:14.13 | beewoolie-afk | Really, there is no need to link in all of the UI. |
| 20:14.19 | prpplague | beewoolie-afk: agreed |
| 20:14.47 | beewoolie-afk | It's an interesting problem. |
| 20:14.57 | beewoolie-afk | What might work is a script that performs the loads you need. |
| 20:15.21 | beewoolie-afk | Might be straightforward. |
| 20:16.18 | prpplague | yea |
| 20:16.24 | [g2] | lennert you saw the post from the Atheros guy on l-a-k about the "nobody cared" problem right ? |
| 20:16.57 | prpplague | beewoolie-afk: a stripped down build of apex with just the options i need is 16k |
| 20:18.36 | beewoolie-afk | prpplague: I've spent a lot of time getting it small. |
| 20:18.46 | beewoolie-afk | Part of the problem is that there are limits on what I can remove. |
| 20:18.48 | prpplague | beewoolie-afk: yea i know |
| 20:18.59 | beewoolie-afk | One of the big pieces is the printf/sprintf code. |
| 20:19.06 | [g2] | bbl |
| 20:19.16 | beewoolie-afk | If we remove the UI, that stuff can go. |
| 20:19.17 | beewoolie-afk | [g2]: later |
| 20:19.29 | prpplague | [g2]: later |
| 20:19.48 | beewoolie-afk | with thumb, it drops about 2K right now, but it doesn't run anymore. |
| 20:20.03 | beewoolie-afk | And that is with only a small portion of the code in thumb. |
| 20:20.53 | beewoolie-afk | There are a couple of things to chase on the thumb path: the call-by-r3 library function is missing; the code doesn't even run now. |
| 20:21.40 | prpplague | beewoolie-afk: i plan on tinkering this weekend, so i'll let you know |
| 20:21.52 | prpplague | beewoolie-afk: you got the latest s3c2410 patch correct? |
| 20:24.50 | beewoolie-afk | I don't think so. Let me check the receipt log. |
| 20:25.24 | beewoolie-afk | It hasn't even been received. |
| 20:25.26 | prpplague | hehe you already have my address set to send to the trash bin |
| 20:25.47 | beewoolie-afk | Tee hee. No. I have a log that show everything received. |
| 20:25.56 | beewoolie-afk | Even before the auto-trashing procmail gets it. |
| 20:29.03 | prpplague | beewoolie-afk: the latest one has the serial changes you suggested and doesn't include the meminfo removed |
| 20:33.12 | beewoolie-afk | OK. Still waiting. |
| 20:34.24 | prpplague | hmm |
| 20:34.58 | prpplague | beewoolie-afk: otw |
| 20:35.08 | prpplague | yahoo delivery schedule sucks |
| 20:35.47 | prpplague | beewoolie-afk: i've been wondering why it takes so long for you to respond, hehe, must be crappy yahoo mail |
| 20:36.14 | beewoolie-afk | I'd be lying if that was the only reason. Sometimes, I get the mail and it takes a couple of days before I can review it. |
| 20:36.33 | prpplague | hehe |
| 20:37.18 | prpplague | beewoolie-afk: my boss is considering no longer submitting patches, since we've had horrible responses in the last 2 months |
| 20:39.07 | beewoolie-afk | Then your boss is naive. |
| 20:39.27 | beewoolie-afk | Open source doesn't run on corporate schedules, but it does deliver results. |
| 20:39.28 | prpplague | beewoolie-afk: why is that? |
| 20:39.43 | beewoolie-afk | Open source is about relationships. |
| 20:39.51 | beewoolie-afk | Relationships take time. |
| 20:40.14 | beewoolie-afk | prpplague: There may be something wrong with my email. i'm not getting anything. |
| 20:40.38 | prpplague | beewoolie-afk: yea well, they have never submitted patches before untill i started there |
| 20:41.26 | beewoolie-afk | Look at reiser. that guy is *nuts* about getting his code in the kernel, but his behaviour has shown that he's untrustworthy |
| 20:42.01 | beewoolie-afk | The kernel folks are cautious, with good reason. |
| 20:46.04 | prpplague | beewoolie-afk: well, most of the time adding our stuff to the main trees |
| 20:48.27 | beewoolie-afk | I'm still not getting email, so I suspect something has gone awry. |
| 20:49.40 | prpplague | bummer, |
| 20:49.50 | prpplague | beewoolie-afk: well, most of the time adding our stuff to the main trees isn't very beneficial to us |
| 20:50.06 | beewoolie-afk | It's been running for, gosh, years without trouble. |
| 20:50.07 | prpplague | beewoolie-afk: i'm mainly doing it to add back to community |
| 20:50.18 | beewoolie-afk | It can be tricky. |
| 20:50.56 | beewoolie-afk | If it's specific to your hardware, and you don't care about updating your patches as the kernel progresses forward, then there is no reason to worry. |
| 20:51.17 | beewoolie-afk | However, you get somebenefit from putting your code into the tree as code improvements are, kinda, free. |
| 20:57.59 | prpplague | beewoolie-afk: yea normally our builds are very static |
| 21:08.07 | beewoolie-afk | prpplague: bbs, I'm going to reset this machine. |
| 21:08.22 | prpplague | beewoolie-afk: ok |
| 21:13.56 | *** join/#openjtag beewoolie-afk (n=beewooli@206.124.142.26) |
| 21:14.34 | beewoolie-afk | prpplague: Still no mail from you. I'm getting other email. |
| 21:15.23 | prpplague | resending |
| 21:31.44 | beewoolie-afk | prpplague: I found the problem... |
| 21:49.39 | prpplague | beewoolie-afk: hehe and? |
| 21:53.30 | prpplague | beewoolie-afk: gotta run, let me know about the patch |
| 22:33.08 | *** join/#openjtag ByronT (n=byron-po@nslu2-linux/ByronT) |
| 22:34.40 | *** join/#openjtag odoc (i=odoc@is.borntobooze.de) |
| 23:51.05 | *** part/#openjtag odoc (i=odoc@is.borntobooze.de) |