**** BEGIN LOGGING AT Wed Jul 29 02:59:57 2009
Jul 29 03:33:38 <elfMobile> anybody cross compiling for the sheeva?
Jul 29 03:34:03 <tinker-f595> not at the moment.
Jul 29 03:34:46 <tinker-f595> thinking of just ding the compiling on the plug as I have it running off of a drive.  And before you ask why - cause I can ;)
Jul 29 03:36:07 <tinker-f595> elfMobile: have you got it booting off a hard drive?
Jul 29 03:47:19 <elfMobile> gave up
Jul 29 03:47:22 <elfMobile> i flashed my NAND
Jul 29 03:47:29 <elfMobile> didn't want to though...
Jul 29 03:48:21 <elfMobile> I am in my Gentoo environment rsyncing 300Gb of stuff from my old fileserver which I hope to retire
Jul 29 03:50:58 <tinker-f595> ah
Jul 29 03:51:16 <tinker-f595> gave up with which?
Jul 29 04:09:47 <elfMobile> gave up with booting off the hard drive
Jul 29 04:09:53 <elfMobile> or getting the uImage from tehre
Jul 29 04:15:13 * mwester wonders what's so difficult about it
Jul 29 04:16:23 <elfMobile> well.... the ext2load commands just load a file
Jul 29 04:16:48 <elfMobile> the commands on the gentoo page had it loading uImage from an offset and only a particular ammount of bytes
Jul 29 04:16:56 <elfMobile> I couldn't find a way to get ext2load to handle that
Jul 29 04:20:58 <elfMobile> mwester, http://plugcomputer.org/plugforum/index.php?topic=532.0
Jul 29 04:24:16 <mwester> elfMobile,  the nand read command does not read from a filesystem; it reads _directly_ from the NAND flash memory.  The numbers you are providing to the nand read command tell it where in the flash memory to read how many bytes into what location in ram.
Jul 29 04:25:01 <mwester> elfMobile,  you don't need that with ext2load because ext2load reads from a filesystem -- the filesystem tells the bootloader where on the sd device the requested file starts, and how large it is -- you don't have have to tell it that.
Jul 29 04:25:21 <mwester> The only thing you need with ext2load is to tell it the starting address in RAM to load the named file into.
Jul 29 04:25:41 <mwester> very simple; I think you are looking for more complexity than necessary!
Jul 29 04:26:14 <elfMobile> mwester, so why is there any offset used when I flashed mtdblock1 with my uImage?
Jul 29 04:26:36 <mwester> Because it needs to know where in the flash to put the bits.
Jul 29 04:27:06 <elfMobile> no... I'm talking about getting the bits
Jul 29 04:27:08 <elfMobile> nand read 0x01000000 0x00100000 0x00400000
Jul 29 04:27:16 <mwester> I told you above.
Jul 29 04:27:45 <elfMobile> if I flashed my uImage using cat uImage > /dev/mtdblock1   then why doesn't the uImage start at 0x0000000 of mtdblock1?
Jul 29 04:27:49 <mwester> nand read needs to know a) where in the very large flash memory to start reading, b) how many bytes to read, and c) where in the RAM to place the data it reads from falsh.
Jul 29 04:28:02 <mwester> mtdblock1 is not a concept known to uboot.
Jul 29 04:28:25 <elfMobile> what is the significance of 0x00100000
Jul 29 04:29:39 <mwester> when someone partitioned the flash space, they somewhat arbitrarily selected that spot as a good place for the kernel.  on other systems with much less flash, you may find less "round" numbers selected, in order to avoid wasted "holes' in the flash.
Jul 29 04:30:27 <mwester> You could put the kernel anywhere you wanted in flash, as long as you don't overwrite u-boot itself (and as long as you pass the new partitioning you have created in to the kernel when you boot it, so it also knows about the flash arrangement).
Jul 29 04:31:20 <elfMobile> arg!
Jul 29 04:31:45 <elfMobile> 0x00100000 was the offset in NAND to start reading
Jul 29 04:31:50 <elfMobile> correct?
Jul 29 04:34:18 <elfMobile> Are you saying that 0x00100000 maps to /dev/mtdblock1 ?
Jul 29 04:38:46 <mwester> I don't know what the partitioning on your device looks like, but probably.
Jul 29 04:40:27 <mwester> In any case, the correct way to boot from a file on the USB device has nothing to do with the nand read command, so there's no need to worry about those numbers.
Jul 29 04:40:40 <mwester> Just do:
Jul 29 04:40:41 <mwester> usb start
Jul 29 04:41:08 <mwester> ext2load usb 0:1 0x8000000 /boot/uImage
Jul 29 04:41:25 <mwester> bootm 0x8000000
Jul 29 04:42:08 <mwester> The 0x8000000 is the address in RAM into which you loaded the kernel with the ext2load command... you could put it in any other reasonable location, but no need to change what the plug wiki suggests.
Jul 29 04:42:35 <mwester> No other numbers from the nand read are needed; they do not apply to the usb and the filesystem.
Jul 29 04:43:32 <mwester> (that's how I boot my ARM Fedora plug)
Jul 29 05:17:56 <tinker-f595> see http://plugcomputer.org/plugwiki/index.php/U-Boot_Quick_Reference
Jul 29 05:19:19 <tinker-f595> mwester:  your explanation is the clearest one I have seen.  Most descriptions seem to totally obfuscate what is occurring during boot etc
Jul 29 19:08:54 <_dieter_> rabeeh: ping
Jul 29 19:09:52 <_dieter_> rabeeh: I noticed that there is a new project open-rd.org :)
Jul 29 19:10:30 <_dieter_> rabeeh: is this also initiated from marvell or from a third party?
Jul 29 19:21:55 <_dieter_> Does anybody know something about open-rd.org?
Jul 29 19:22:26 <_dieter_> I wonder why there is a different forum because the board isn't much different IMHO?
Jul 29 20:25:56 * timtimred wiggles
Jul 30 02:10:05 <tinker-f595> dieter_: Domain ID:D156140305-LROR
Jul 30 02:10:05 <tinker-f595> Domain Name:OPEN-RD.ORG
Jul 30 02:10:05 <tinker-f595> Created On:15-May-2009 22:58:55 UTC
Jul 30 02:10:06 <tinker-f595> Last Updated On:15-Jul-2009 03:53:09 UTC
Jul 30 02:10:06 <tinker-f595> Expiration Date:15-May-2010 22:58:55 UTC
Jul 30 02:10:06 <tinker-f595> Sponsoring Registrar:CSC Corporate Domains, Inc. (R24-LROR)
Jul 30 02:10:08 <tinker-f595> Status:CLIENT TRANSFER PROHIBITED
Jul 30 02:10:10 <tinker-f595> Registrant ID:89840107fdbf2481
Jul 30 02:10:12 <tinker-f595> Registrant Name:Jeff Lagman
Jul 30 02:10:14 <tinker-f595> Registrant Organization:Marvell International Limited
Jul 30 02:10:16 <tinker-f595> Registrant Street1:5488 Marvell Lane
Jul 30 02:10:18 <tinker-f595> Registrant Street2:
Jul 30 02:10:20 <tinker-f595> Registrant Street3:
Jul 30 02:10:22 <tinker-f595> Registrant City:Santa Clara
Jul 30 02:10:24 <tinker-f595> Registrant State/Province:CA
Jul 30 02:10:26 <tinker-f595> Registrant Postal Code:95054
Jul 30 02:10:28 <tinker-f595> Registrant Country:US
Jul 30 02:10:30 <tinker-f595> Registrant Phone:+1.4082222500
Jul 30 02:10:32 <tinker-f595> Registrant Phone Ext.:
Jul 30 02:10:34 <tinker-f595> Registrant FAX:+1.4082222500
Jul 30 02:10:56 <tinker-f595> whoops forgot to reformat it
Jul 30 02:14:17 <mwester> ~pastebin
Jul 30 02:14:26 <mwester> No bot?
Jul 30 02:15:15 <mwester> Anyway,  use a pastebin service for large blocks of text.  Not only does it preserve formatting, and make cut and paste more useful for the intended recipient(s), it's considered polite to the rest of the channel.  (Although it's not like there's a lot of activity here!)
Jul 30 02:15:40 <mwester> What's that domain record all about, anyway?
Jul 30 02:17:56 <ShadowJK> as a reply to the question about whether open-rd.org is "initiated from marvell or from a third party?", I imagine
Jul 30 02:20:40 <mwester> Ah.  I missed that.  :)  Looks like marvell, I guess.  I'd have thought the similarities to the plug would have led to a single site, but I guess marvell's marketing folks felt differently.
Jul 30 02:38:32 <tinker-f595> I just finished looking at the license
Jul 30 02:38:38 <tinker-f595> for the site...
Jul 30 02:39:05 <tinker-f595> mwester: sorry about mis-formatting that
Jul 30 02:39:31 <tinker-f595> would off only been a could of lines but paste error
Jul 30 02:39:50 <tinker-f595> tired from a long day staring at bits
Jul 30 02:40:21 <tinker-f595> http://open-rd.org/index.php/faq/terms-of-use
Jul 30 02:44:52 <tinker-f595> hmmm and they use google for the openrd forum...
Jul 30 02:47:39 <mwester> bloody lawyers.
**** ENDING LOGGING AT Thu Jul 30 02:59:57 2009