Welcome! Log In Create A New Profile

Advanced

patch for Jeff's u-boot on Pogoplug V1 (wallwart-ish)

Posted by davygravy 
patch for Jeff's u-boot on Pogoplug V1 (wallwart-ish)
February 22, 2012 05:19PM
I'm looking for the patch for Jeff's u-boot on Pogoplug V1 (wallwart-ish). {not looking for CloudEngine's original uboot source... no... for the patch that he used to build the replacement uboot for the Pogoplug V1 units.}

Jeff has the patches readily available for pinkpogo (v2), dockstar, and goflexnet... but I can't find the patch for the original pogoplug v1 (wallwart-ish) unit. http://jeff.doozan.com/debian/uboot/build_uboot.htm has links to the patches for the three units mentioned above, and to the general patch... but nothing for the pogov1...

I've scanned his uboot-install-mtd0.sh script , and have made educated guesses as to what the URL (an unlisted,unadvertised one) might be, but haven't gotten lucky.

Ideas anyone?

(can it be that he just used the sheevaplug config...?) [no, that wouldn't work... already found an acct of someone who tried that... wouldn't boot correctly due to incorrect RAM specs, it seems]
===========================================

Last login: Thu Feb 23 01:51:45 2012 from 192.168.11.149
root@debian:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-41) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Tue Jan 17 05:11:52 UTC 2012
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate FreeAgent DockStar   <<<<<<<<<<<<<<<<<<<<<+++++++++++++++++=========!!!!!!
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c03d50c4, node_mem_map c043f000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 121016KB available (3516K code, 583K data, 124K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

... and NAND shows up ...

[   22.380319] NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)

From the CE stock u-boot:
-bash-3.2# dmesg | grep NAND
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
0x00000200-0x00000233 : "NAND 16MiB 1,8V 8-bit"
mtd: partition "NAND 16MiB 1,8V 8-bit" doesn't start on an erase block boundary -- force read-only
-bash-3.2# dmesg | grep Memory
Memory policy: ECC disabled, Data cache writeback
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 125824KB available (3584K code, 252K data, 120K init)

=====================================================



Edited 4 time(s). Last edit at 02/22/2012 08:35PM by davygravy.
Re: patch for Jeff's u-boot on Pogoplug V1 (wallwart-ish)
February 22, 2012 09:11PM
The dockstar and the pogo v1 share the same uboot binary, even though it's downloaded as uboot.mtd0.dockstar.jeff-2010-10-23.kwb or uboot.mtd0.pogov1.jeff-2010-10-23.kwb in the install script. The MD5 is the same for both files.
Re: patch for Jeff's u-boot on Pogoplug V1 (wallwart-ish)
February 22, 2012 10:29PM
Kk, thanks Jeff.

=====================================================
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: