| 00:44.47 | [g2] | beewoolie-away, hey! ping |
| 01:04.42 | beewoolie-away | [g2]: hi |
| 01:22.22 | beewoolie-away | [g2]: fyi. I implemented the kernel configuration for APEX. It makes configuration *way* easier. |
| 04:59.04 | *** join/#openjtag Tiersten (tman@Tiersten.nslu2-linux) |
| 09:17.13 | *** join/#openjtag ka6sox-zzzz (~tking@ka6sox.nslu2-linux) [NETSPLIT VICTIM] |
| 09:17.14 | *** join/#openjtag dyoung (~dyoung@dyoung.nslu2-linux) [NETSPLIT VICTIM] |
| 09:17.14 | *** join/#openjtag VoodooZ_log (~VoodooZ@CPE00c0f021712c-CM014110003785.cpe.net.cable.rogers.com) [NETSPLIT VICTIM] |
| 09:17.53 | *** join/#openjtag Tiersten (tman@Tiersten.nslu2-linux) [NETSPLIT VICTIM] |
| 09:17.53 | *** join/#openjtag [g2] (~g2@g2.nslu2-linux) [NETSPLIT VICTIM] |
| 09:20.59 | *** join/#openjtag dyoung-logger (~dyoung-lo@cpe-70-93-27-157.hawaii.res.rr.com) |
| 09:22.43 | *** join/#openjtag nslu2-log (dyoung@netblock-66-159-209-60.dslextreme.com) [NETSPLIT VICTIM] |
| 12:54.42 | *** join/#openjtag Tiersten_ (tman@Tiersten.nslu2-linux) |
| 13:15.23 | *** join/#openjtag ka6sox-zzzz (~tking@adsl-66-159-198-116.dslextreme.com) [NETSPLIT VICTIM] |
| 13:15.54 | *** join/#openjtag dyoung-zzzz (~dyoung@dyoung.nslu2-linux) |
| 13:24.47 | *** join/#openjtag VoodooZ_log (~VoodooZ@CPE00c0f021712c-CM014110003785.cpe.net.cable.rogers.com) [NETSPLIT VICTIM] |
| 14:41.15 | *** join/#openjtag prpplague (~dave@mailhost2.amltd.com) |
| 16:07.18 | *** join/#openjtag [g2] (~g2@rdu57-8-035.nc.rr.com) |
| 19:33.59 | *** join/#openjtag beewoolie-away (~beewoolie@florence.buici.com) |
| 19:35.06 | VoodooZ_work | hey |
| 19:36.42 | beewoolie | ih |
| 19:36.50 | beewoolie | 8-p |
| 19:41.59 | *** join/#openjtag prpplague^2 (~dave@mailhost.amltd.com) |
| 20:10.39 | VoodooZ_work | beewoolie: How's APEX doing? |
| 20:11.12 | beewoolie | Pretty good as far as I can tell. |
| 20:11.19 | beewoolie | I got two users on new platforms. |
| 20:11.30 | beewoolie | They've vetted the ports I did. |
| 20:11.40 | beewoolie | ...kinda blind if the truth be told. |
| 20:11.46 | VoodooZ_work | good to hear. |
| 20:11.57 | VoodooZ_work | I'm looking forward to trying it on the slug. |
| 20:11.59 | beewoolie | I've got one more key feature to add before I call it stable. |
| 20:12.14 | beewoolie | Yeah, me too. The problem is that I don't have working jtag on that platform. |
| 20:12.18 | VoodooZ_work | good. |
| 20:12.21 | beewoolie | I've got some tests to run to determine the problem. |
| 20:12.30 | VoodooZ_work | Because without JTAG I can't really risk it before then. |
| 20:12.33 | beewoolie | I have a cable, but it isn't reliable. |
| 20:12.40 | beewoolie | You know it. |
| 20:12.40 | VoodooZ_work | ouch |
| 20:12.55 | beewoolie | I don't know if it's the cable or my soldering job on the slug. |
| 20:13.04 | VoodooZ_work | hehehehe |
| 20:13.06 | beewoolie | I worked better on a previous slug. |
| 20:13.15 | beewoolie | But I salted that one good. |
| 20:13.44 | VoodooZ_work | How much time approx. would I shave off on bootup going from redboot to apex would you say? |
| 20:13.45 | beewoolie | Also, we don't really know why APEX isn't booting the kernel. |
| 20:13.58 | beewoolie | Have you tried openslug? |
| 20:14.12 | beewoolie | Someone made some improvements there. It boots pretty fast. |
| 20:14.37 | VoodooZ_work | yeah, but redboot takes a good chunk I was told |
| 20:14.42 | beewoolie | There are about 15 seconds of pauses in the boot process. Moreover, the decompression phase is slowr than it needs to be. |
| 20:14.46 | VoodooZ_work | And booting directly would be niuce. |
| 20:14.52 | VoodooZ_work | yeah. |
| 20:14.54 | beewoolie | When I tried openslug is was really speedy. |
| 20:15.04 | VoodooZ_work | right now It's like 50+ with bluetooth. |
| 20:15.23 | VoodooZ_work | that was probably before they added the CSR stuff though. |
| 20:15.31 | beewoolie | the real benefit of APEX will come through better flash management. |
| 20:15.41 | beewoolie | CSR? what stuff was done? |
| 20:15.44 | VoodooZ_work | yeah. I heard it's pretty small too. |
| 20:16.07 | VoodooZ_work | oh, I meant made the ethernet drivers load by default. |
| 20:16.29 | beewoolie | APEX should fit in a single block. The problem is that we think or wonder or fear (take you pick) that the Intel access library is necessary to initialize the NPEs. |
| 20:16.30 | VoodooZ_work | stock i think it's like 41 seconds. |
| 20:16.42 | VoodooZ_work | i see. |
| 20:17.01 | VoodooZ_work | Thankfully I don't use them for my robot so.. |
| 20:17.29 | beewoolie | I think the gating factor is me having a working JTAG emulator. |
| 20:17.57 | beewoolie | I've got a milestone in progress that, once done, means I can spend some quality time with the skug. |
| 20:17.58 | VoodooZ_work | yeah. that's pretty much a requirement. |
| 20:18.06 | VoodooZ_work | nice |
| 20:20.17 | [g2] | beewoolie how's APEX going ? |
| 20:20.30 | beewoolie | [g2]: we were just talking about that. |
| 20:20.35 | [g2] | I got GigE running on the avila board |
| 20:21.06 | [g2] | so the PCI is working OK to start with :) |
| 20:21.14 | beewoolie | I saw some of that. what got the driver to link? |
| 20:21.35 | [g2] | Oh, I just purge those calls |
| 20:21.38 | [g2] | purged |
| 20:21.54 | prpplague | beewoolie: hmm, you haven't got the one we sent? |
| 20:21.55 | [g2] | I've got a patch that's #ifdef FIXME |
| 20:22.04 | prpplague | beewoolie: jtag dongle that is? |
| 20:22.18 | [g2] | it's only two calls in e1000_ethtool.c |
| 20:22.27 | [g2] | and they're actually for loopback setup |
| 20:22.35 | beewoolie | g |
| 20:22.43 | beewoolie | prpplague: Nothing yet. |
| 20:22.48 | beewoolie | prpplague: when did you send it? |
| 20:23.04 | prpplague | beewoolie: doh, i turned it over to shipping like 2 weeks ago |
| 20:23.09 | prpplague | beewoolie: i'll check on it |
| 20:23.47 | [g2] | so about APEX, I'd like to start using the JTAG header I've got on the device for APEX |
| 20:23.55 | beewoolie | [g2]: you've got some cohones, hombre. |
| 20:24.07 | beewoolie | [g2]: OK. |
| 20:24.18 | [g2] | what commenting out the call ? |
| 20:24.38 | beewoolie | [g2]: uh huh. |
| 20:25.15 | [g2] | I was going to stub the routine and put an oops in but it was simpler to just try it |
| 20:25.27 | [g2] | it's not like it was in the main init routine or anything |
| 20:25.56 | [g2] | but it shows that nobody's insmoded the thing with the later kernels |
| 20:26.30 | [g2] | The device was responding to 6-8K pings a second |
| 20:27.05 | [g2] | it didn't measure the link rate, but there were more than 1M packets in no time and 2+GB of rx/tx data |
| 20:27.24 | beewoolie | That would be what we call fast, I think. |
| 20:27.44 | [g2] | dunno how fast exactly |
| 20:28.32 | [g2] | the GigE card on the P4 does nearly 600Mbs TCP xfer as measure by ttcp on a 700MB file |
| 20:28.45 | [g2] | that's plenty fast for me at $29 buck for the card |
| 20:29.39 | [g2] | I'm looking for another adapter for the disk side |
| 20:29.47 | [g2] | the 3 choices are |
| 20:29.54 | [g2] | Same NEC chip |
| 20:29.58 | [g2] | as in the slug |
| 20:30.09 | [g2] | Firewire 400 and possibly 800 |
| 20:30.33 | [g2] | There's an Adaptec SCSI module that's got RAID support |
| 20:30.36 | beewoolie | Seems like most of the HDs are both USB2 and firewire. |
| 20:30.42 | beewoolie | which raid? |
| 20:31.04 | [g2] | I think just 0 1 |
| 20:31.16 | [g2] | I'm not excited about SCSI |
| 20:31.17 | beewoolie | Keep in mind that most of those raid devices aren't really raid devices. |
| 20:31.39 | beewoolie | At least that's true on the IDE world. |
| 20:32.02 | [g2] | well there's a bunch of stuff to check out. |
| 20:32.21 | [g2] | I'm really kinda curious why the PCI bug doesn't seem to show up with the GigE card |
| 20:33.01 | [g2] | not that I've stressed it super hard |
| 20:35.29 | beewoolie | [g2]: good question. |
| 20:38.20 | [g2] | so back to APEX, I can make a connector, but I may just get an adaptor from the vendor |
| 20:38.54 | beewoolie | Don't they use the standard ARM pinout/ |
| 20:39.01 | [g2] | probably |
| 20:39.20 | [g2] | it's a 14 pin connector 2x7 |
| 20:40.45 | beewoolie | yeah. |
| 20:41.07 | [g2] | the pinout is documented |
| 20:41.18 | [g2] | does someone make a cheap cable ? |
| 20:41.30 | beewoolie | What is on the other end of the cable? |
| 20:42.04 | [g2] | well they sell a wiggler like device for $99 that plugs into the PC and they've got sw |
| 20:42.13 | [g2] | that runs on the windows platform |
| 20:42.57 | [g2] | I could rig up some wire and use my own cable from digilent |
| 20:43.28 | [g2] | but I'd rather spend my time on APEX |
| 20:43.37 | [g2] | and other things |
| 20:45.49 | [g2] | maybe I'll play with it tonight, but anyway what's the state of APEX ? |
| 20:46.24 | beewoolie | there hasn't been much change on the nslu2 front. I've done a lot to make it build better. |
| 20:46.43 | beewoolie | The new config stuff is really great. I can say that because I didn't write it. |
| 20:47.27 | [g2] | where's ext2 at ? |
| 20:47.38 | prpplague | beewoolie: hehe |
| 20:48.24 | beewoolie | [g2]: ext2 is in good shape. It supports symlinks, directories, and partitions. |
| 20:48.43 | beewoolie | there isn't a directory list function, yet. That's part of the feature set I need to implement. |
| 20:48.43 | [g2] | cool |
| 20:48.55 | prpplague | beewoolie: i've been testing the sd/mmc code, but i'm not satisfied with the way it is now |
| 20:49.38 | [g2] | beewoolie, so on a ext2 partition it could load the kernel from /boot/zImage ? |
| 20:50.23 | beewoolie | Yep. Even if it has symlinks in the path. |
| 20:50.36 | [g2] | awesome |
| 20:50.36 | beewoolie | prpplague: What's wrong with your MMC code? |
| 20:51.12 | prpplague | beewoolie: not as clean as it should be |
| 20:51.31 | [g2] | beewoolie, there a way to specify the kernel to APEX ? |
| 20:51.35 | [g2] | is there |
| 20:51.39 | beewoolie | Of course. |
| 20:51.45 | [g2] | from the cmdline |
| 20:51.54 | [g2] | or config |
| 20:51.57 | beewoolie | What are you wondering? yeah. You can do it there, but that doesn't make sense. |
| 20:52.14 | beewoolie | Specifying the kernel is really about copying it to SDRAM. |
| 20:52.31 | [g2] | nod. |
| 20:52.32 | beewoolie | There is a config option to set the source region for the kernel. |
| 20:52.51 | beewoolie | ...and to copy it on startup. |
| 20:52.59 | [g2] | I talking grub like pick a kernel from the cmdline |
| 20:53.08 | [g2] | during testing or recovery |
| 20:53.14 | beewoolie | I'm going to add aliases that will make that sort of thing easier. |
| 20:53.31 | beewoolie | You can always copy the kernel by hand or set the startup command in the environment. |
| 20:54.01 | beewoolie | If you want a menu select, it'll have to be an extension. APEX doesn't expect there to be a user at the console. |
| 20:54.27 | [g2] | we'll need to change that at least for development :) |
| 20:55.15 | beewoolie | What do you want to see? |
| 20:55.16 | beewoolie | More importantly, what do you want to see that APEX doesn't do? |
| 20:55.35 | [g2] | I'll have to review the commands and run the latest from RAM |
| 20:55.51 | [g2] | it's probably all there |
| 20:56.20 | beewoolie | since you can set the kernel region in the environment, I'm inclined to leave it as is. |
| 20:56.30 | beewoolie | but I'm open to suggestions. |
| 20:56.58 | [g2] | right now you expect the kernel to be in its own partition correct ? |
| 20:57.07 | beewoolie | No. |
| 20:57.25 | beewoolie | What do you mean? |
| 20:57.30 | [g2] | ok the Kernel region is the memory area the kernel gets copied to |
| 20:57.39 | [g2] | in mem |
| 20:57.51 | beewoolie | No. The kernel LMA is the address where the kernel is copied. |
| 20:57.58 | beewoolie | The region is the source for the copy. |
| 20:58.18 | beewoolie | Technically, the LMA is also a region, but that's a sneaky side-effect of the way that APEX works. |
| 20:59.42 | [g2] | Ok from my memory there was nor:... and mem: |
| 21:00.19 | [g2] | actually, I can just check the code |
| 21:01.20 | beewoolie | The default driver is the mem driver. So, 0x00008000 is really the same as mem:0x8000 |
| 21:03.56 | [g2] | the code I've got is old 1.1.1 |
| 21:04.31 | [g2] | I'l pull the latest, but in that code CONFIG_KERNEL_LMA=0x00008000 defines the LMA |
| 21:04.34 | beewoolie | I'm working on a 1.2.5. There's an error in the config handling. |
| 21:04.46 | beewoolie | That's the memory address. tight. |
| 21:04.52 | beewoolie | s/tight/right/ |
| 21:05.16 | [g2] | CONFIG_ENV_REGION_KERNEL=nor:0x60010+0xffff0 |
| 21:05.37 | [g2] | defines the kernel source |
| 21:05.48 | beewoolie | That's the one to change. |
| 21:06.27 | [g2] | and how would one specify /boot/bzImage in the middle of a compressed ext2 partition ? |
| 21:06.47 | [g2] | or non-compressed for that matter ? |
| 21:06.52 | beewoolie | We don't yet have compressed ext2 partitions, yet. |
| 21:06.57 | beewoolie | Oh. |
| 21:07.14 | beewoolie | We don't yet support ext2 in flash. That's the other thing I need to do. |
| 21:07.23 | beewoolie | It will look something like this: |
| 21:07.58 | beewoolie | nor:2m+6m|ext2:/boot/zImage |
| 21:08.14 | beewoolie | I'm going to add two features. |
| 21:08.19 | [g2] | that looks cool |
| 21:08.27 | beewoolie | There will be the | pipe for cascading drivers. |
| 21:08.39 | beewoolie | Then, I'm going to add aliases so that it is easier to specify these. |
| 21:08.44 | beewoolie | Thus, we can say |
| 21:08.53 | beewoolie | alias part2 nor:2m+6m |
| 21:09.10 | beewoolie | alias root part2|ext2 |
| 21:09.13 | beewoolie | then |
| 21:09.22 | beewoolie | the kernel will be root:/boot/zImage |
| 21:10.15 | [g2] | or alias root nor:2m+6m|ext2 |
| 21:10.21 | beewoolie | right. |
| 21:10.27 | beewoolie | depends on your needs. |
| 21:10.48 | beewoolie | It'll be a simple text substitution, so it can be used for commands, too. |
| 21:11.08 | beewoolie | alias erase_flash nor:128k |
| 21:11.22 | beewoolie | ...er... alias erase_flash erase nor:128k |
| 21:11.45 | beewoolie | I also want to add confirmation to the erase command. |
| 21:11.52 | [g2] | so basically alias name .... |
| 21:12.04 | [g2] | confirmation is important |
| 21:12.06 | beewoolie | Just as people have come to expect. |
| 21:13.29 | [g2] | ok so pipe is the key missing feature for that support |
| 21:13.39 | beewoolie | ...and an option to override the confirmation: erase -f ... |
| 21:13.43 | beewoolie | Right. |
| 21:13.55 | beewoolie | Pipe is the crucial feature. Aliases make it nice. |
| 21:14.35 | beewoolie | I just came up with the syntax a day or so ago. I've been having a hard time forming the feature so that it is clear, alias-able, and sufficient. |
| 21:14.42 | beewoolie | I think that the pipe works well. |
| 21:15.27 | [g2] | can the pipe handle something like |
| 21:16.02 | [g2] | nor:2m+6m|ext2,ext2.gz,jffs2:/boot/bzImage ? |
| 21:16.24 | [g2] | similar to rootfstype |
| 21:16.24 | beewoolie | What are you trying to say? |
| 21:16.43 | beewoolie | You want a wildcard? |
| 21:16.47 | dyoung-zzzz | ssh dyoung; init 6 |
| 21:16.57 | beewoolie | :-p |
| 21:17.06 | [g2] | I asking whether you need to know aproari |
| 21:17.16 | [g2] | I asking whether you need to know apriori |
| 21:17.41 | [g2] | hey dyoung-zzzz |
| 21:19.06 | beewoolie | That's an interesting question. Presently, yes. I'll have to think about that. It requires selecting the driver at runtime. The way I've been looking at it, there would be no way...let me think about it. There may be something that does work. |
| 21:19.24 | beewoolie | I'm thinking that it would be like this: |
| 21:19.25 | [g2] | Ok. You do great work |
| 21:19.32 | dyoung-zzzz | [g2] Axoimtek. |
| 21:19.36 | dyoung-zzzz | http://www.axiomtek.com.tw/product_detail.php?model_num=AX8931A&majorcat=Industrial+PCs&subcat=Rackmount+Peripherals+%26+Accessories |
| 21:19.50 | dyoung-zzzz | Theres a US Importer in Texas IIRC. |
| 21:20.03 | [g2] | I've got a tw importer already :) |
| 21:20.08 | beewoolie | flashpart|(ext2,fat,ext2gz,jffs2):/boot/zImage |
| 21:20.31 | [g2] | dyoung-zzzz, I could live with IDE for a start |
| 21:20.45 | [g2] | I'd prefer SATA, but IDE's ok |
| 21:21.10 | beewoolie | [g2]: I posted 1.2.5 to fix a problem with the config strings. |
| 21:21.14 | [g2] | that runs linux right |
| 21:21.24 | [g2] | beewoolie, thx. I'll pull that tonight and build it |
| 21:21.32 | dyoung-zzzz | I found a bunch of MiniPCI stuff by accident a few years abck when I was looking for CPCI (compact PCI) stuff; but all my links are... lost in a huge bitbucket |
| 21:22.16 | beewoolie | dyoung-zzzz: What's the white header for? |
| 21:22.57 | dyoung-zzzz | Aux Power i would guess. |
| 21:26.38 | dyoung-zzzz | Or, maybe a LED. Yeah, iuts probably for a LED. |
| 21:44.51 | beewoolie | dyoung-zzzz: that makes sense to me. |
| 21:56.57 | [g2] | dyoung-zzzz, THX for the axiomtek link btw |
| 22:07.43 | dyoung-zzzz | That wasnt the one i was thinking of last night though; that one is still spinning around in my brain. Somewhere. |
| 22:37.37 | *** join/#openjtag nslu2-log_ (dyoung@netblock-66-159-209-60.dslextreme.com) |