**** BEGIN LOGGING AT Thu May 21 02:59:57 2009
May 21 07:03:16 <digger3> okay, that took some time... I cannot use ubifs with my sd-card...
May 21 07:03:42 <digger3> what's the 2nd best choice for an sd-card? (I'm planning to run debian from it)
May 21 07:52:41 <rabeeh> digger3: ubifs is intended for the internal flash of the plug. with SD card (the same as USB stick) all the wear leveling and bad block managament is don't on the card itself
May 21 07:53:08 <rabeeh> digger3: for SD card I recommend EXT2 or any other filesystem that doesn't have journalling
May 21 07:53:15 <rabeeh> (minimizes writes to the SD card)
May 21 07:53:23 <digger3> rabeeh: I'm curious: why not yaffs2?
May 21 07:54:20 <rabeeh> digger3: same reasons. jffs2/ubifs/yaffs2 are all intended to be run on the hos Linux when there is a bare NAND flash connected to it. So all wear leveling is done on host Linux
May 21 07:55:11 <digger3> rabeeh: ah, okay, thanks
May 21 08:27:05 <Md> ubifs is just better :-)
May 21 09:41:00 <digger3> hi, I'm getting loads of: http://pastebin.com/m3339eb9 errors when booting debian from the sd-card, any advice on what could be the problem?
May 21 09:44:39 <digger3> ah, now the complete filesystem is trashed.. fascinating
May 21 09:46:56 <rabeeh> digger3: which kernel are you using?
May 21 09:47:52 <digger3> I copied all the files with the stock 2.6.22 kernel which came pre-installed -> no worries, I installed debian with the usual instructions (kernel version 2.6.29) and end up with a corrupt fs
May 21 09:48:28 <rabeeh> which usual instructions?
May 21 09:48:37 <digger3> I'm planning to try and reboot into the NAND flash, unzip debian on the sd-card again, and replace the 2.6.29 kernel with the 2.6.30-rc6 one, does this make sense?
May 21 09:48:38 <rabeeh> are you applying the mvsdio patch?
May 21 09:48:46 <digger3> rabeeh: http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html
May 21 09:49:40 <digger3> rabeeh: nope, it's my first day trying this plug
May 21 09:53:00 <digger3> rabeeh: are there precompiled kernels that will allow me to quickly test this 'mvsdio' patch or do I need to compile it?
May 21 09:53:29 <rabeeh> digger3: http://plugcomputer.org/plugforum/index.php?topic=298.0
May 21 10:25:55 <digger3> rabeeh: okay, I'll try that as soon as I get it to boot from the NAND-flash again
May 21 10:26:00 <digger3> rabeeh: thanks
May 21 10:26:22 <rabeeh> digger3: i'll be posting a new recovery tool on the forums (today)
May 21 10:26:53 <rabeeh> the new recovery tool will install the plug with kernel 2.6.30-rc6, uboot with SD card support (patch from the forums) and ubuntu 9.04 the release version
May 21 10:30:21 <digger3> rabeeh: sounds good
May 21 10:30:54 <digger3> rabeeh: will it allow me to install ubuntu to the SD, or to the NAND?
May 21 10:31:05 <rabeeh> NAND
May 21 10:31:17 <rabeeh> can be easily modded to install on SD
May 21 10:31:37 <digger3> that's true, I like the fact that I have a recovery system installed, comes in handy now...
May 21 14:24:59 <rabeeh> http://plugcomputer.org/plugforum/index.php?topic=323.0
May 21 14:53:14 <Md> rabeeh: I suppose that this kernel too lacks crypto acceleration, doesn't it?
May 21 14:54:18 <rabeeh> Md: crypto driver is supported on the 2.6.22.18 kernel only. Lately crypto driver was posted for Orion support; but I don't know what is their status.
May 21 14:56:20 <Md> do you have a URL?
May 21 14:56:32 <Md> a friend of mine is interested in porting it to mainline
May 21 14:57:52 <rabeeh> http://marc.info/?l=linux-arm-kernel&m=124173065908928&w=2
May 21 14:58:03 <rabeeh> Sebastian?
May 21 14:58:13 <rabeeh> the same guy?
May 21 14:58:27 <Md> no
May 21 14:58:53 <rabeeh> does he have orion or a plug?
May 21 15:06:20 <zumbi> why don't you use OCF layer?
May 21 15:06:46 <rabeeh> zumbi: that's what kernel 2.6.22.18 use
May 21 15:09:55 <zumbi> rabeeh: ok - we had been using OCF with an AES hardware crypto engine on the 2.6.28
May 21 15:10:47 <zumbi> also with openssl support
May 21 15:49:55 <Md> I do not like much the idea of using OCF, because this means that there are about zero changes for the driver to be merged in mainline...
May 21 15:49:59 <Md> rabeeh: a plug
May 21 15:51:15 <lennert> there's no mainline crypto framework that is usable from userspace, is there?
May 21 15:51:37 <lennert> on x86 it's all just instructions built into the cpu itself
May 21 15:52:07 <Md> s/changes/chances/
May 21 15:52:25 <zumbi> lennert: no mainline, but out-of-tree, http://ocf-linux.sourceforge.net/
May 21 15:52:48 <Md> zumbi: this is what the existing driver is using
May 21 15:54:04 <zumbi> Md: yes, that is what rabeeh said above
May 21 15:54:46 <mjl-> i'm reading the FS on sdio.  page 260 mentions the sdio registers at being at offset 0x80000, while the register descriptions at page 714 at 0x90000.
May 21 15:55:03 <mjl-> describe them at*
May 21 15:55:11 <mjl-> rabeeh: are new versions of the FS being made?
May 21 15:56:05 <lennert> zumbi: i'm not talking about OCF
May 21 15:56:35 <zumbi> lennert: then i misunderstood, sorry
May 21 20:11:51 <timtimred> ping lennert....
May 21 20:39:00 <timtimred> lennert remember the n1200 (the one with the 10/100 marvell switch chip)
May 21 20:39:28 <timtimred> we still have the issue where we need to plug in one of the switch ports and it has to be up for the other ones to work
May 21 20:39:51 <timtimred> if we can get you one at some point wanna fix that? :)
May 21 20:40:11 <timtimred> bbradley is going to get other bits mainline soon
May 21 20:40:28 <timtimred> (woo i get my name in the kernel somewhere then finally...)
May 21 20:41:21 <timtimred> if we get you one its obviously for keepsies. thats if marvell wont spank you for owning a mpc based ppc device :D
May 21 20:41:56 <timtimred> back in a bit...
May 21 20:46:30 <digger3> I installed the 2.6.30-rc6 kernel, and tried to boot from the sd card, but all I'm getting is: http://pastebin.com/m758013fe  and it then just hangs, any tips?
May 21 21:07:10 <lennert> timtimred: that's the phy issue
May 21 21:07:21 <lennert> timtimred: you should be able to say in the dts that giantfart needs to use a 'fixed' phy
May 21 21:07:33 <lennert> timtimred: ask afleming how to do that if you can't figure it out
May 21 21:07:40 <lennert> timtimred: should be straightforward i guess
May 21 21:07:51 <lennert> timtimred: i think i have enough devices :)
May 21 21:12:52 <timtimred> afleming noted ta
May 21 21:13:01 <timtimred> hmm, i think i know ho to do that already.
May 21 21:13:36 <lennert> okay :)
May 21 21:13:47 <timtimred> um, maybe.
May 21 21:13:47 <lennert> i fixed a bug in gianfar the other day... afleming owes me :)
May 21 21:13:48 <timtimred> :)
May 21 21:13:51 <lennert> so feel free to bother him ;)
May 21 21:14:00 <timtimred> cool will do :)
May 21 21:15:10 <timtimred> will try it out this weekend
May 21 21:15:26 <timtimred> ping bbradley_ your changes in our git repo? :)
May 21 21:15:48 <bbradley_> not yet, just sorting out a defconfig and splitting my changes into two patches
May 21 21:16:18 <timtimred> okies. i think OE pulls that repos head so lets put it in a branch to test?
May 21 21:16:35 <timtimred> (maybe im wrong there)
May 21 21:17:03 <bbradley_> yeah, I'll put it on a for-mainline branch or something
May 21 21:17:23 <timtimred> sweet
May 21 21:57:59 <timtimred> lennert did you find out more about that device
May 21 21:58:43 <lennert> timtimred: which?
May 21 22:00:02 <timtimred> 440
May 21 22:00:04 <timtimred> based
May 21 22:00:17 <lennert> sorry?
May 21 22:00:24 <timtimred> some powerpc thing
May 21 22:00:30 <lennert> what is this in?
May 21 22:01:16 <timtimred> you said someone might have a device for a mainline port
May 21 22:01:26 <timtimred> i dont know what it is :)
May 21 22:01:54 <timtimred> and were going to get more info :)
May 21 22:02:14 <lennert> ah!
May 21 22:02:20 <lennert> yea, that was from TS
May 21 22:02:27 <lennert> i should follow up with the guy actually, haven't done yet
May 21 22:02:28 <lennert> sorry
May 21 22:02:40 <timtimred> heh np...
May 21 22:04:31 <timtimred> i can see a couple of other devices in 2.6.23 have fixed phy thing happening
May 21 22:04:35 <timtimred> using vitesse
May 21 22:06:00 <timtimred> as specified in some dts
May 21 22:58:29 <timtimred> night all :)
May 22 00:38:49 <pauldy> can someone clarify 0x400000@0x100000(uImage) is > 2MB is it not?
May 22 00:42:07 <pauldy> is it size@base or end@base
May 22 00:42:46 <cbxbiker61> size@base
**** ENDING LOGGING AT Fri May 22 02:59:57 2009