**** BEGIN LOGGING AT Wed Mar 02 23:59:56 2005 Mar 03 02:26:21 seems that the PL2303 driver in 2.6.9 doesn't work with the ATEN cable that i bought Mar 03 02:27:04 PL-2303 ttyUSB0: pl2303_open - failed submitting interrupt urb, error -28 Mar 03 02:27:04 PL-2303 ttyUSB0: PL-2303 converter now disconnected from ttyUSB0 Mar 03 02:27:21 http://www.fedoraforum.org/forum/archive/index.php/t-25219.html Mar 03 02:27:43 http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/0143.html Mar 03 02:27:59 http://www.ussg.iu.edu/hypermail/linux/kernel/0409.1/1014.html Mar 03 02:28:10 hmm Mar 03 02:28:22 looks like a common problem Mar 03 02:28:26 Suppose you could backport pl2303 from 2.6.newer.... Mar 03 02:29:03 one of those messages indicates it could be an ehci problem ... Mar 03 02:29:38 which wouldnt suprise me all that much. Mar 03 02:29:51 what I've been reading is ehci in 2.6.9 is kinda busted. Mar 03 04:12:46 ok, that's enough success for tonight - I don't want to jinx it. Mar 03 04:13:21 (after three nights of failures, AccessSlug now has mgetty runnning and recognising and initialising a modem) Mar 03 04:13:23 night all Mar 03 16:37:46 dyoung ping Mar 03 16:41:14 dyoung: mt-daapd has been pushed to the feed Mar 03 17:58:22 http://groups.yahoo.com/group/nslu2-linux/message/4757 Mar 03 18:07:28 <[g2]> dyoung-web, thx Mar 03 18:07:44 <[g2]> rwhitby-away, Mar 03 18:07:46 <[g2]> # USB Host Controller Drivers Mar 03 18:07:46 <[g2]> # Mar 03 18:07:46 <[g2]> CONFIG_USB_EHCI_HCD=y Mar 03 18:07:46 <[g2]> # CONFIG_USB_EHCI_SPLIT_ISO is not set Mar 03 18:07:46 <[g2]> # CONFIG_USB_EHCI_ROOT_HUB_TT is not set Mar 03 18:08:00 <[g2]> Do you need the Root_hub stuff ? Mar 03 18:33:14 I think you p;robably do. Mar 03 18:33:25 If you look at old boot messages it makes reference to roothub Mar 03 18:47:23 does /proc tell you anyting good? Mar 03 18:53:47 * [g2] checking /proc Mar 03 18:54:20 <[g2]> I was thinking that was rwhitby's hub issue Mar 03 18:55:01 <[g2]> the last kernel changes I made were including the usb_FTDI_SIO _VISO _IPAQ and _PL2303 Mar 03 18:55:03 <[g2]> modules Mar 03 18:56:27 <[g2]> Heh... This is something in /proc/cpuinfo that needs changing Mar 03 18:56:36 <[g2]> Hardware : Linksys NSLU2 Mar 03 18:56:40 is there going to be a separte openslug howto bit in the wiki? Mar 03 18:57:22 <[g2]> sure there's the TurnUp procedure now and ByronT was working on enhancing that Mar 03 18:57:50 I need to write HowTo/PivotYourRootToARaidWithOpenSlug or something like it Mar 03 18:58:16 <[g2]> I won't get in your way Mar 03 18:58:27 <[g2]> I think we need to clean up a couple issues first Mar 03 18:58:30 Well, what I'm asking is where does it belong. Mar 03 18:58:34 <[g2]> like ehci and the date :) Mar 03 18:58:59 The date will be fixed today. Mar 03 18:59:07 <[g2]> The HowTo that are OpenSlug specific are supposed to be under OpenSlug Mar 03 18:59:23 <[g2]> Just like the one's specific to Unslung are supposed to be under there Mar 03 18:59:51 So what belongs in the global howto then? Mar 03 19:02:29 <[g2]> things that are global to both, like spindown for maxtor external drive Mar 03 19:02:41 <[g2]> works the same setup on Unslung or OpenSlug Mar 03 19:04:14 okay Mar 03 19:04:20 it needs restructuring then. Mar 03 19:04:41 so does my howto belong on the main openslug page? or do we make a howto as a subpage of that page first? Mar 03 19:05:12 <[g2]> I think we can have a HowTo right off the main OpenSlug page Mar 03 19:19:33 what file am I supposed to edit to trigger ipkg-ing of modules? Mar 03 19:21:06 <[g2]> kernel modules ? Mar 03 19:21:14 <[g2]> or packages Mar 03 19:22:17 kernel modules Mar 03 19:22:25 like how pl2303 gets into a ipk for instance Mar 03 19:22:41 <[g2]> that's in the openslug.conf Mar 03 19:23:31 <[g2]> to be included in the rootfs Mar 03 19:23:32 didnt work for me. Mar 03 19:23:41 I dont want it in the rootfs. Mar 03 19:24:02 sorry that came out wrong. Mar 03 19:24:02 <[g2]> is it already packaged ? Mar 03 19:24:24 * [g2] hugs dyoung-web Mar 03 19:24:26 I want the modules in the rootfs, but it never gets into a ipkg. Mar 03 19:24:39 so when it tries to install it, it grumbles that it cant find it. Mar 03 19:25:05 <[g2]> right you didn't add it to extra depends in openslug.conf Mar 03 19:25:30 Just did. Mar 03 19:25:31 <[g2]> and if you did, you didn't clean the kernel Mar 03 19:25:39 did that too Mar 03 19:25:57 <[g2]> then they get added Mar 03 19:26:00 and in fact it never ends up in tmp/work/openslug-kernel-2.6.9/install Mar 03 19:26:12 <[g2]> which kernel is it building ? Mar 03 19:26:52 <[g2]> Packaged contents of kernel into /home/tom/dev/openslug/build/tmp/deploy/ipk/kernel_2.6.11-r0_nslu2.ipk Mar 03 19:26:52 <[g2]> Packaged contents of kernel-dev into /home/tom/dev/openslug/build/tmp/deploy/ipk/kernel-dev_2.6.11-r0_nslu2.ipk Mar 03 19:26:52 <[g2]> Packaged contents of kernel-module-jbd into /home/tom/dev/openslug/build/tmp/deploy/ipk/kernel-module-jbd_2.6.11-r0_nslu2.ipk Mar 03 19:26:53 <[g2]> Packaged contents of kernel-module-nfs into /home/tom/dev/openslug/build/tmp/deploy/ipk/kernel-module-nfs_2.6.11-r0_nslu2.ipk Mar 03 19:26:56 <[g2]> Packaged cont Mar 03 19:26:58 <[g2]> .... Mar 03 19:30:36 I;'m trying to make a 2.6.9. Mar 03 19:30:57 I get all of those messages except for the one I just added. heh. Mar 03 19:31:02 must not be licking it right. Mar 03 19:34:21 <[g2]> dyoung-web, Ok got the echi-hcd fix for 2.6.11 Mar 03 19:35:14 dyoung: any modules in the kernel defconfig get automatically built and packaged when the kernel is built. Mar 03 19:35:49 <[g2]> but not necessarily installed on the rootfs Mar 03 19:36:02 <[g2]> rwhitby-web, I've just fixed the ehci-hcd issue Mar 03 19:36:18 <[g2]> I'll be pushing in a few minutes after a sync Mar 03 19:39:04 right - dyoung you can get any modules from the default defconfig from the feed Mar 03 19:40:54 [g2]: PREFERRED_VERSION is now in openslug.conf Mar 03 19:41:14 I also moved some stuff from openslug.conf to openslug-image (the stuff which is not optional for the image) Mar 03 19:41:28 <[g2]> rwhitby-web, You didn't like dyoungs post ? Mar 03 19:41:53 it seemed like we were adding stuff to OPENSLUG_EXTRA_* which should have been going into openslug-image.bb Mar 03 19:41:55 which post? Mar 03 19:42:53 I put 2.6.9 in openslug.conf, and it can be overriden in local.conf as per dyoung's post Mar 03 19:43:10 <[g2]> ok Mar 03 19:43:12 <[g2]> great Mar 03 19:43:38 <[g2]> so I just add a PREFERRED_VERSION_openslug-kernel = "2.6.11" to my local.conf Mar 03 19:44:53 the question is: It seems that the 2.6.11 is (on the face of it, with limited testing time and breadth) up to the level of 2.6.9 - so do we switch before the beta (and delay the beta until the 20 have switched), or do we release the beta on 2.6.9, but then not be in a position to reproduce problems cause we've all moved to 2.6.11 .... Mar 03 19:44:58 yeah, that should do it Mar 03 19:49:39 <[g2]> Ok the world makes sense again Mar 03 19:50:02 [g2]: have you been bk send'ing your changesets to nslu-changesets@lists.sf.net - I haven't seen any come through .... Mar 03 19:52:21 <[g2]> rwhitby-web, I setup ssmtp as a /usr/bin/mail, It forwards mail to me but the bk sends seem to not make it Mar 03 19:53:51 <[g2]> rwhitby-web, the override doesn't appear to be working Mar 03 19:54:21 <[g2]> ... NOTE: package openslug-kernel-2.6.9-r9: task do_compile: started Mar 03 19:56:55 Hmm - maybe try a ?= in openslug.conf ... can you try that? Mar 03 19:57:10 I never know what order those things are read in anymore .... Mar 03 19:59:31 <[g2]> ?= I think that's assign it if it is not empty Mar 03 19:59:44 <[g2]> which basically means default if empty Mar 03 19:59:59 <[g2]> = assignemnt Mar 03 20:00:49 what was the ehci issue? Mar 03 20:01:00 right, I mean change the = in openslug.conf into an ?=, so that your = in local.conf (which must be getting read first for some reason) can override it. Mar 03 20:01:20 why would local.conf be getting read before openslug.conf though .... ??? Mar 03 20:02:01 <[g2]> becase it's first in the BBPATH Mar 03 20:02:20 <[g2]> that's why all the stuff in conf overrides Mar 03 20:02:46 <[g2]> unless you change the default ordering ,but we all know OE is infinitely flexible :) Mar 03 20:03:00 <[g2]> I'm testing the ?= now Mar 03 20:04:22 Ok so just add my modules to openslug.conf then? Mar 03 20:04:53 which modules? Mar 03 20:05:19 if they are meant to go in the default image, and are not optional, then they go in openslug-image.bb Mar 03 20:05:34 if they are mean to go in the default image, but are optional, then they go in openslug.conf Mar 03 20:05:56 if they are not meant to go in the default image, then they go in your local.conf Mar 03 20:06:12 in all cases, they end up in the feed if they are in the official defconfigf Mar 03 20:06:14 MD modules. Optional. Mar 03 20:06:31 in default image or not? Mar 03 20:07:24 Either way. I figure most people wont need that, so I can ipkg install them myself later. But if theres demand, we cam put it in the image. My initial thought is not though. Mar 03 20:08:09 ok, so you add them to official defconfig (so they get built for everyone and end up in the feed), but put them in your local.conf Mar 03 20:10:12 as a EXTRA_RDEPENDS ? Mar 03 20:10:30 or as OPENSLUG_EXTRA_RDEPENDS ? Mar 03 20:11:10 yes - use = in your local.conf Mar 03 20:11:18 that's plus equals Mar 03 20:11:45 [g2]: so should we change BBPATH ? Mar 03 20:11:53 <[g2]> no Mar 03 20:12:04 <[g2]> the ?= fixes the issue Mar 03 20:12:15 ok, can you push that? Mar 03 20:12:45 <[g2]> I will in a minute or two, the units reflashing with the 11-r1 kernel Mar 03 20:12:59 you need to get your email fixed, so we don't surprise each other with changesets Mar 03 20:13:31 remember that the emails to nslu-changesets are meant to be the main way of keeping all the other nslu2-linux oe developers informed of changes to repo Mar 03 20:13:51 (more reliable than irc) Mar 03 20:14:13 <[g2]> well all the changes are at http://nslu2-linux.bkbits.net Mar 03 20:14:37 right, but email is the notification that something has happened. Mar 03 20:14:52 <[g2]> given that the bazillion pulls from oe-devel don't show up it's hardly a complete set Mar 03 20:14:59 [g2], so ultimately what was the problem with ehci not loading? The MACH vs ARCH thing? Mar 03 20:15:09 <[g2]> dyoung-web, EXACTLY Mar 03 20:15:13 [g2]: right, but most of those don't affect us directly Mar 03 20:15:28 [g2]: are you saying we shouldn't be doing the nslu-changesets mails? Mar 03 20:15:29 <[g2]> rwhitby-web, clearly they do effect us Mar 03 20:16:16 ok, we had previously all agreed to do the nslu-changeset emails. Is that no longer the agreement? Mar 03 20:16:47 (I don't care either way, I just need us to be on the same page so I know what I have to do to keep in sync with what others are doing) Mar 03 20:17:02 <[g2]> we had. I one point I had a full sendmail on my system. Mar 03 20:17:10 <[g2]> and things worked ok Mar 03 20:17:32 <[g2]> Then I tried adding ssmtp and things went downhill from there Mar 03 20:18:01 <[g2]> sendmail has been purged, ssmtp works but bk doesn't like it Mar 03 20:19:15 understood. what's the plan going forward ? Mar 03 20:20:30 (i.e. are you going to fix it, or do we need to change to a different notification system)? Mar 03 20:22:46 <[g2]> rwhitby-web, Today the question is what is the purpose of the notification system, does it allow dev to reproduce the repo offline or is it just nslu2 specfic changes Mar 03 20:23:17 <[g2]> I can send a simple e-mail to changests... patch 1.xxxxx Yada yada yada Mar 03 20:24:07 just nslu2 specific changes so the nslu2 devs know what each other is pushing. Mar 03 20:24:53 <[g2]> Well a simple e-mail with the change set number should work then correct ? Mar 03 20:25:02 <[g2]> and a little text about the change Mar 03 20:25:13 what about external changes? Mar 03 20:25:29 no-one external should be touching openslug stuff Mar 03 20:25:32 <[g2]> they currently are not getting sent Mar 03 20:25:37 and we can't control the non-openslug stuff Mar 03 20:25:41 like Joe Developer needs to modify something for his Killer App; and sends his changeset to the changeset. Mar 03 20:25:50 how about the changes to OE that affect OpenSlug? Mar 03 20:26:17 dyoung-web: right - we've previously used the address for external people to submit changesets too (which we can automatically apply) Mar 03 20:26:36 ka6sox-away: we have no way currently of getting emails about them Mar 03 20:26:36 <[g2]> ka6sox-away, exactly, we were held up a week ago by non-OpenSlug changes that were Beta Blockers Mar 03 20:27:15 so we have outside influences that we need to be aware of. Mar 03 20:27:16 yep, but we can't get oe devs to do what we want, whereas we can make agreements amongst ourselves to make our lives easier for the openslug-specific stuff Mar 03 20:28:05 <[g2]> rwhitby-web, I'm we are doing the outside pulls ourselves... Mar 03 20:28:12 90% of the #oe changes I don't care about. 0.1% of them kill us. what do you do? Mar 03 20:28:22 <[g2]> s/I'm/Ummmm Mar 03 20:28:38 I am pulling from OE into nslu Mar 03 20:28:41 [g2]: the outside pulls happen hourly automatically Mar 03 20:28:52 <[g2]> that's the point Mar 03 20:29:26 so how do we keep each other informed of the nslu2-specific changes that we are doing, without being overloaded by notifications of *all* #oe changes? Mar 03 20:29:33 <[g2]> we are automatically pulling... That's different from we can't get the OE devs to ..... Mar 03 20:30:26 even if we were manually pulling, the issue is still the same: "how do we keep each other informed of the nslu2-specific changes that we are doing, without being overloaded by notifications of *all* #oe changes?" Mar 03 20:30:58 no cia for BK? Mar 03 20:31:00 <[g2]> I got straight to th bk repo and look at the changes Mar 03 20:31:24 that's documentation of the changes, not notification Mar 03 20:31:33 you have to know that you have to go and look Mar 03 20:31:58 <[g2]> we are talking about push versus pull Mar 03 20:32:03 the nslu-changesets emails are both notification that something interesting has happened, and also contain the text of exactly what changed Mar 03 20:32:15 (with the emphasis on "interesting") Mar 03 20:32:59 <[g2]> I scan *all* the OE changes on the pull Mar 03 20:33:10 exactly, the nslu-changesets lists is a push mechanism for interesting nslu2-linux changes. Mar 03 20:33:18 <[g2]> and I browse all the changesets in our repo Mar 03 20:34:10 yep, that's a comprehensive pull strategy. but it's missing the notification that nslu-changesets currently gives us for nslu2-developer nslu2-specific changes Mar 03 20:34:16 <[g2]> Is nudi or the other machine setup to do bk sends ? Mar 03 20:34:35 yes, if you clone into your home dir Mar 03 20:34:52 (the official build area is set up as read-only clone intentionally) Mar 03 20:35:13 it is? Mar 03 20:35:20 When did that happen? Mar 03 20:35:34 (last time I checked, mail didnt work for me) Mar 03 20:35:40 oops...I might have busted it. Mar 03 20:35:41 oh, I'm making an assumption there. perhaps it isn't Mar 03 20:35:45 exim is running. Mar 03 20:35:49 but it should be Mar 03 20:35:55 and mail injection is working iirc Mar 03 20:35:58 let me check on that. Mar 03 20:36:08 probably not licking it right. Mar 03 20:36:17 I cant seem to lick anything right today. Mar 03 20:36:35 I'll know soon, cause I'm about to push something from there. Mar 03 20:36:39 <[g2]> well the point of cloning the repo to do a bk send isn't a good ieda Mar 03 20:36:44 exim is running. Mar 03 20:37:18 [g2]: agreed - the bk send has to be from where you are making the change Mar 03 20:37:47 if you push then you send a notification. Mar 03 20:37:53 ? Mar 03 20:38:08 [g2]: or have I misunderstood why you were asking whether nudi is set up to do bk sends? Mar 03 20:38:42 I wonder if we can get the thing which does the CIA notifications in #nslu2-linux to also send the email ... Mar 03 20:39:06 rwhitby: I'll ask scanline Mar 03 20:39:13 (with full text, cause "2 files in 2 dirs" is not detailed enough to replace the current bk send scheme that we have in place) Mar 03 20:39:29 I'm not sure that CIA ever sees the full patch Mar 03 20:41:22 anyway, I gotta run. until we can devise a scheme with the same features as the current "bk send to nslu-changesets" scheme (i.e. is a push scheme with full text of the patch and comments), then I would ask that all bk pushers continue to bk send for each push. Mar 03 20:41:42 [g2]: do you need any assistance in fixing your mail setup? Mar 03 20:44:10 back later Mar 03 20:45:09 cya! Mar 03 20:47:17 <[g2]> rwhitby-web, my mail setup works Mar 03 20:47:51 <[g2]> I'm not using sendmail, ssmtp doesn't seem compatible with bk send Mar 03 20:49:16 [g2]: let me rephrase then: "do you need any assistance in being able to bk send changesets to nslu-changesets@lists.sf.net from the machine where you are making the changes" ? Mar 03 20:50:34 <[g2]> rwhitby-web, I don't plan to re-install sendmail. We do need to figure what we are going to do Mar 03 20:51:28 agreed. do you agree we need the same level of push notification including full patch contents that we have now? Mar 03 20:51:40 [I really gotta go - will check logs later] Mar 03 20:52:25 * [g2] hugs rwhitby Mar 03 20:53:06 <[g2]> The trigger you guys have been talking about is a good idea Mar 03 20:53:49 <[g2]> The script that kergoth uses for the sends (an xml thingy) could probably be easily adapter to send to be navi and changesets Mar 03 20:54:12 <[g2]> a general purpose mechanism is probably an even better idea Mar 03 20:54:25 Agree Mar 03 20:54:35 * [g2] hugs dyoung-web Mar 03 20:54:48 <[g2]> dyoung-web, spill on the date thing Mar 03 20:55:22 the rtc code. Mar 03 20:55:47 I havnt identified the exact place, but there this whole thing about month being 0-11 vs 1-12 Mar 03 20:55:49 <[g2]> dyoung-web, AND do you have any understaning why the ARCH/MACH causes the issues it does cause I'm clueless on that one Mar 03 20:56:16 <[g2]> AHH... so it's a 0-relative 1-relative thing Mar 03 20:56:24 I figure if I look at the clock code for more than 2 minutes (time spent thismorning) it should become evident Mar 03 20:56:30 If ytoure looking for something to do, feel free. Mar 03 20:56:44 But send the changeset so I know you already did it. ;-) Mar 03 20:57:04 sorry, I couldnt resist that one. :-) Mar 03 20:57:07 <[g2]> I can send a note Mar 03 20:57:09 <[g2]> :) Mar 03 20:57:37 that 'll be fine., I dont want to fix it if its already fixed. Mar 03 20:57:47 <[g2]> nod. Mar 03 20:58:14 <[g2]> Ok so we've got the following: Mar 03 20:58:22 <[g2]> 1/ EHCI pain in the butt Mar 03 20:58:26 <[g2]> 2/ date Mar 03 20:58:28 The MACH/ARCH thing is spinny in the brain, but I would imagine a few other things would need to be changed too. So I'm thinking the PCI or IRQ stuff isnt getting initilaized because only a single change was made. Mar 03 20:58:35 <[g2]> 3/ The minor unmatched interrupts Mar 03 20:59:10 <[g2]> 4/ The MACH/ARCH thing Mar 03 20:59:50 <[g2]> AHHh.... usbnet is happy again Mar 03 21:02:51 <[g2]> 5/ minor update on the TurnUp procedures Mar 03 21:05:15 <[g2]> 6/ coldplug on usbnet Mar 03 21:05:22 ka6sox: bk send not working on nudi Mar 03 21:05:40 its not sendmail..its exim Mar 03 21:05:48 <[g2]> dyoung-web, did you check the kernel size Mar 03 21:05:54 no Mar 03 21:05:58 its modules. Mar 03 21:06:00 so it should take sendmail commands. Mar 03 21:06:56 1038836 Mar 3 18:53 zImage Mar 03 21:10:58 ka6sox, its not setup right. "Mailing to remote domains not supported" Mar 03 21:11:08 dyoung-web, I see that. Mar 03 21:11:14 getting the docs now. Mar 03 21:16:25 <[g2]> 7/ root hub issue Mar 03 21:16:38 <[g2]> 8/ Interrupt driven ixp driver Mar 03 21:16:56 I think its the one on line 313.... Mar 03 21:17:52 <[g2]> tv.tv_sec = mktime(tm.tm_year+epoch, tm.tm_mon+1, tm.tm_mday, tm.tm_hour, Mar 03 21:19:24 but again, I want to sit down with it comfortably.. Mar 03 21:21:34 <[g2]> 9/ Get a proper device id for the x1205 Mar 03 21:23:16 <[g2]> 10/ swap setup Mar 03 21:25:05 <[g2]> 11/ GPIO for power-of Mar 03 21:25:08 <[g2]> 11/ GPIO for power-off Mar 03 21:28:34 [g2] which machine id are we using? the one for IXDP425 or NSLU2? Mar 03 21:29:14 remember redboot ... Mar 03 21:29:35 not passed. Mar 03 21:30:14 thats why we're pasing it 597 in the setup. Mar 03 21:31:37 <[g2]> I think beewoolie looked at it and it's hard-coded in the kernel Mar 03 21:31:59 Well, its hard coded because we're hard coding it. Mar 03 21:32:26 <[g2]> and it's hard-coded in the Linksys Mar 03 21:32:34 in head-xscale.S Mar 03 21:32:38 Right. Mar 03 21:33:57 <[g2]> THIS IS COOL, even if it isn't true http://www.linuxdevices.com/news/NS8705350561.html Mar 03 21:34:27 urban legend. Mar 03 21:37:24 Heck why not? Mar 03 21:38:01 <[g2]> And this is a cool device http://www.linuxdevices.com/news/NS7634317885.html Mar 03 21:38:17 summary for single window treo users? Mar 03 21:38:35 <[g2]> first, second or both Mar 03 21:39:13 <[g2]> first says some dude hacked the ipod bootloader code by playing it out as audio, then reconstructing the code Mar 03 21:39:52 <[g2]> The CSB637 is the newest small SBC from Cogent. It measures 1.75 x 2.5 (63.5 x 44.5mm), and is based on an Atmel AT91RM9200, a low-power SoC (system-on-chip) with an ARM920T core that Atmel says delivers 200 MIPS (millions of instructions per second) performance. Mar 03 21:40:24 Didnt y'all have the C=64 earlier? WIth the crappy ass tape deck interface? Mar 03 21:40:25 <[g2]> It's got USB2.0 (dunno high-speed or not), ETH, SPI, 64MB Mar 03 21:40:50 <[g2]> The Cogent board supplements the Atmel microcontroller?s functionality, according to Direct Insight, offering interfaces that include 10/100 Ethernet MAC and PHY, USB, Dual SDIO, 4 UARTs, SSI, SPI, and CompactFlash Interfaces, an onboard LCD/CRT Controller. Also included are 64MB SDRAM and 8MB flash memory and an "efficient" 3.3V Regulator. Mar 03 21:41:03 <[g2]> you can get 16MB flash too Mar 03 21:41:47 <[g2]> and JTAG :) Mar 03 21:42:06 how much? Mar 03 21:42:21 <[g2]> 12/ Find out real core speed Mar 03 21:42:44 <[g2]> rwhitby-treo1, dev kit is 1700 euros I think, dunno on the part Mar 03 21:43:20 ow. Mar 03 21:44:20 <[g2]> looks like the board is only 110 Mar 03 21:44:29 lets buy some. Mar 03 21:44:32 <[g2]> http://shop.directinsight.co.uk/catalog/product_info.php?products_id=510 Mar 03 21:44:41 <[g2]> I think that's euros Mar 03 21:44:52 <[g2]> or is it # Mar 03 21:45:34 # Mar 03 21:46:06 <[g2]> Ok 110 Pounds Mar 03 21:46:25 ~ $200. Mar 03 21:46:44 <[g2]> Hmmm Mar 03 21:46:57 <[g2]> I wonder what 1K pricing is Mar 03 21:47:25 $50 Mar 03 21:47:28 ;-) Mar 03 21:47:36 <[g2]> 50# Mar 03 21:47:49 yeah, thats what I meant. Mar 03 21:47:59 maybe less. Mar 03 21:48:39 the PDF Schematics are $550. Mar 03 21:48:42 dammit Mar 03 21:48:44 #550 Mar 03 21:48:58 breakout box is #345. Mar 03 21:50:40 <[g2]> $149 US at 1K Mar 03 21:50:49 <[g2]> http://www.cogcomp.com/ Mar 03 21:54:21 probably dont need the full devkit. Mar 03 21:54:32 it looks like nothing closed source. Mar 03 21:55:58 back later. Food. Mar 03 21:56:44 <[g2]> nite all Mar 03 21:56:48 nie Mar 03 21:56:50 nite Mar 03 21:56:56 <[g2]> sweet dreams Mar 03 21:57:01 you too! Mar 03 21:57:07 <[g2]> will do **** ENDING LOGGING AT Thu Mar 03 23:59:56 2005