• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 ... 3 4 [5]
Author Topic: 3.9.0+ Device-tree kernels  (Read 22523 times)
Acid_Jack
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #60 on: October 09, 2013, 11:04:48 PM »


I don't have a lot of time to look at this at the moment, but there is a "fresh" 3.2.51 kernel with that module.

thx, i'll check it
Logged

Acid_Jack
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #61 on: October 10, 2013, 12:09:46 AM »

guruplug freezes after message "Uncompressing Linux... done, booting the kernel."

i use these variables:
arcNumber 2659
mainlineLinux yes
Logged

apemberton
Newbie
*

Karma: 1
Posts: 31


View Profile
« Reply #62 on: October 10, 2013, 03:31:51 AM »

Although the console 'freezes' with Device Tree kernels earlier than 3.11.2 for Guruplug (I am running this on my Guruplugs) it is possible that you may get access using SSH after a period for the kernel to boot fully.

Another possibility is do you have a line 'machid=a63' in your u-boot environment? (Replaces arcNumber.)
Logged

Tony Pemberton

Acid_Jack
Newbie
*

Karma: 0
Posts: 16


View Profile
« Reply #63 on: October 10, 2013, 03:36:50 AM »

it is very risky
i want to see all console output
so i better stay with previous kernel
kirkwood-* kernels boots without such problem (but lacks uap module)

i don't use 'machid'
Logged

marcus11
Newbie
*

Karma: 0
Posts: 8


View Profile
« Reply #64 on: October 19, 2013, 04:23:14 PM »

Updated u-boot 2013.10 final attached, flash like so:
copy to fat16 usb stick
in existing console:
usb start
fatload usb 0 0x800000 u-boot.kwb
nand erase 0x0 0x80000
nand write 0x0800000 0x0 0x80000

Build instructions and patches for the built binary from https://doukki.net/doku.php?id=wiki:tutoriels:uboot.howto
Code:
Marvell>> version

U-Boot 2013.10 (Oct 20 2013 - 09:13:23)
Marvell-Sheevaplug - eSATA - SD/MMC
arm-none-linux-gnueabi-gcc (GCC) 4.2.1
GNU ld (GNU Binutils) 2.18.50.20070820

Note you'll want to set the nand sizes differently to the default if you wish to access it via linux.  Here's my env that handles the debian stock and cbxbiker kernels without modification from SD:
Code:
baudrate=115200
bootargs=console=ttyS0,115200n8 earlyprintk mtdparts=orion_nand:512k(uboot),128k(uboot_env),11m@1m(kernel),-@12m(rootfs) root=/dev/mmcblk0p2 rootdelay=5
bootcmd=run x_bootcmd; run z_bootstrap; reset;
bootdelay=3
console=console=ttyS0,115200n8
ethact=egiga0
ethaddr=00:50:43:01:D0:7B
filesize=6da04
initrdaddr=0x01100000
initrdfile=/uInitrd
kerneladdr=0x00800000
kernelfile=/uImage
loadcmd=ext2load mmc 0:1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:512k(uboot),128k(uboot_env),11m@1m(kernel),-@12m(rootfs)
scriptaddr=0x00800000
scriptfile=/boot/boot.scr
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200n8 earlyprintk mtdparts=orion_nand:512k(uboot),128k(uboot_env),11m@1m(kernel),-@12m(rootfs)
x_bootargs_root=root=/dev/mmcblk0p2 rootdelay=5
x_bootcmd=${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; run z_bootinit;
x_bootcmd_kernel=echo ====== BootStrap start ======
x_bootcmd_mtd=nand read.e ${kerneladdr} kernel 0x00b00000;
x_bootstrap_cmd=for device in "mmc"; do for fs in "ext2"; do setenv loadcmd "${fs}load ${device} 0:1"; if ${loadcmd} ${kerneladdr} ${kernelfile}; then; if ${loadcmd} ${initrdaddr} ${initrdfile}; then; run z_bootcmd; fi; fi; done; done;
z_bootcmd=if imi ${kerneladdr}; then; bootm ${kerneladdr} ${initrdaddr}; else; echo --- next bootcmd device try ---; fi;
z_bootfail=echo ====== BootStrap end ======
z_bootinit=mmc rescan; usb reset; ide reset;
z_bootstrap=run z_bootinit; run x_bootstrap_scr; run x_bootstrap_cmd; run x_bootcmd_mtd; run z_bootfail;

Environment size: 1612/131068 bytes

I've also compiled netconsole in (untested).

Stuff added to include/configs/sheevaplug.h:
Code:
#define CONFIG_OF_LIBFDT
#define CONFIG_SYS_CONSOLE_IS_IN_ENV 1
#define CONFIG_CMD_NET
#define CONFIG_CMD_CONSOLE
#define CONFIG_CMD_DNS


* mvsdio-patch.diff (35.19 KB - downloaded 93 times.)
* u-boot.kwb (440.35 KB - downloaded 99 times.)
Logged

apemberton
Newbie
*

Karma: 1
Posts: 31


View Profile
« Reply #65 on: December 10, 2013, 05:25:11 AM »

I have updated my various boxes (3xeSata Sheevaplug, 3xGuruplug Server+,2xCubox,2xTonidoplug2,11xRPi) to kernel 3.12.3 and so far, all seems to be well! Well almost. It seems that this kernel has an interrupt problem on my Guruplugs and I show a dmesg from one of them. Also, one small point is there is a typo type error in the 'UPDATE-KERNEL.sh' script and the line
Code:
elif grep -qs 'GuruPlug' /proc/cpuinfo || grep -qs 'GuruPlug' /proc/device-tree/model; then
should be
Code:
elif grep -qs 'GuruPlug' /proc/cpuinfo || grep -qs 'Guruplug' /proc/device-tree/model; then

The 'dmesg' was taken after my plugs had been running for 48 hours though I do not know exactly when the errors occurred. It seems to be worse on a GP+ using SDHC rather than eSata.

Code:
root@NS2:/# dmesg
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.12.3 (kelly@bbb.internal) (gcc version 4.8.2 20131014 (prerelease) (Linaro GCC 4.8-2013.10) ) #2 Wed Dec 4 14:41:22 MST 2013
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell Kirkwood (Flattened Device Tree), model: Globalscale Technologies Guruplug Server Plus
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c07205bc, node_mem_map c0992000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 131072 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200n8 root=/dev/sda2 rw rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512012K/524288K available (5015K kernel code, 328K rwdata, 1676K rodata, 261K init, 385K bss, 12276K reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc0691124   (6693 kB)
      .init : 0xc0692000 - 0xc06d370c   ( 262 kB)
      .data : 0xc06d4000 - 0xc0726028   ( 329 kB)
       .bss : 0xc0726028 - 0xc0786740   ( 386 kB)
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:114
sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
Console: colour dummy device 80x30
Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc04c0a38 - 0xc04c0a90
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
Kirkwood: MV88F6281-A0, TCLK=0.
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource orion_clocksource
FS-Cache: Loaded
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
zbud: loaded
FS-Cache: Netfs 'nfs' registered for caching
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4000, nTxLock = 32000
msgmni has been set to 1000
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
kirkwood-pinctrl f1010000.pinctrl: registered pinctrl driver
mv_xor f1060800.xor: Marvell shared XOR driver
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell shared XOR driver
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
sata_mv f1080000.sata: version 1.28
sata_mv f1080000.sata: slots 32 ports 1
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 25
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit), 512MiB, page size: 2048, OOB size: 64
Scanning device for bad blocks
3 ofpart partitions found on MTD device orion_nand
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "data"
libphy: orion_mdio_bus: probed
mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 02:50:43:0c:95:90
mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 02:50:43:34:97:5e
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ehci-orion: EHCI orion driver
orion-ehci f1050000.ehci: EHCI Host Controller
orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
orion-ehci f1050000.ehci: irq 23, io mem 0xf1050000
orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
i2c /dev entries driver
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdio f1090000.mvsdio: no pins associated
mmc0: new high speed SDIO card at address 0001
mvsdio f1090000.mvsdio: lacking card detect (fall back to polling)
sdhci-pltfm: SDHCI platform and OF driver helper
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
zram: Created 1 device(s) ...
TCP: cubic registered
NET: Registered protocol family 10
NET: Registered protocol family 17
Key type dns_resolver registered
registered taskstats version 1
rtc-mv f1010300.rtc: setting system clock to 2013-12-09 18:27:23 UTC (1386613643)
usb 1-1: new high-speed USB device number 2 using orion-ehci
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
ata1.00: ATA-8: WDC WD2500BEVT-00A23T0, 01.01A01, max UDMA/133
ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD2500BEVT-0 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
usb 1-1.1: new high-speed USB device number 3 using orion-ehci
 sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 8:2.
usb-storage 1-1.1:1.0: USB Mass Storage device detected
scsi1 : usb-storage 1-1.1:1.0
devtmpfs: mounted
Freeing unused kernel memory: 260K (c0692000 - c06d3000)
scsi 1:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 1:0:0:1: Direct-Access     Generic  STORAGE DEVICE   9909 PQ: 0 ANSI: 0
sd 1:0:0:1: Attached scsi generic sg2 type 0
sd 1:0:0:0: [sdb] Attached SCSI removable disk
sd 1:0:0:1: [sdc] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
sd 1:0:0:1: [sdc] Write Protect is off
sd 1:0:0:1: [sdc] Mode Sense: 03 00 00 00
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
 sdc: sdc1 sdc2
sd 1:0:0:1: [sdc] No Caching mode page found
sd 1:0:0:1: [sdc] Assuming drive cache: write through
sd 1:0:0:1: [sdc] Attached SCSI removable disk
systemd-udevd[825]: starting version 204
orion_wdt: Initial timeout 21 sec
cfg80211: Calling CRDA to update world regulatory domain
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
libertas_sdio: failed to load firmware
Bluetooth: module_cfg_cmd(f1): timeout: 1
EXT4-fs (sda2): re-mounted. Opts: (null)
EXT4-fs (sda2): re-mounted. Opts: (null)
fuse init (API version 7.22)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
mv643xx_eth_port mv643xx_eth_port.1 eth1: link up, 1000 Mb/s, full duplex, flow control disabled
IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
mvsdio f1090000.mvsdio: unhandled interrupt status=0x0810 en=0x0100 pio=0
root@NS2:/# ls

This doesn't seem to be mission critical for me though.
Logged

Tony Pemberton

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #66 on: December 12, 2013, 11:08:06 PM »

apemberton, it's great that your testing on a wide variety of systems!

I fixed the typo in UPDATE-KERNEL.sh, it may be a while before it makes it's way to the main web servers due to caching.

As far as the mvsdio interrupt warning, I'm seeing that on my sheevaplug and it hasn't caused any problems for me.  I'm sure that in due time someone will figure out what changed in the interrupt handling code and fix it.
Logged

mgillespie
Full Member
***

Karma: 7
Posts: 239



View Profile
« Reply #67 on: February 18, 2014, 04:14:02 PM »

Anyone else having problems with http://www.xilka.com ?

Many links just redirect to www.appfail.com  Huh

Has this site been compromised?  Have the kernels it hosts been compromised too?  All rather unnerving....

I desperately need to downgrade from 3.13.2 due to ehci usb disconnect problems, but can't get an old kernel, not do I trust that site anymore even if I could...
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 440


View Profile WWW
« Reply #68 on: February 18, 2014, 07:43:31 PM »

Anyone else having problems with http://www.xilka.com ?
Not at the moment. I've just browsed down through the 3.13.3 kernel listing with no problem.
Quote from: see above
Many links just redirect to www.appfail.com  Huh
Odd place to go.  The xilka site isn't accessed over https.  Well, it can be, but the certificate is issued for "*.scaleengine.net", which is where xilka.com lives, but isn't of any use for it.
Seems odd to go to the expense of a valid wildcard certificate (from Comodo) when the subject name isn't actually going to be used.
Logged

mgillespie
Full Member
***

Karma: 7
Posts: 239



View Profile
« Reply #69 on: February 19, 2014, 01:07:31 AM »

Working OK again today. Grabbed the last 3.11 kernel and will stick with that seems more robust on my sheevaplug.
Logged

doragasu
Newbie
*

Karma: 0
Posts: 34


View Profile
« Reply #70 on: March 21, 2014, 11:32:30 AM »

I would like to update my GP+ kernel to the newest ones using the update script, but I don't know how to do it. Let me explain a bit more...

I'm running ArchLinux. Arch on GPs comes with a 3.1 kernel, but I am using 3.7.9 kernel downloaded from xilka. Until now I have been manually installing kernels from uboot via tftpboot/nand erase/nand write. So my GP+ reads the kernel from the NAND, and then the filesystem is mounted from the microSD card.

I was going to test manually updating to the latest 3.13 kernel, but now I see that not only the kernel image is needed, also the device tree must be flashed. And I don't know where do I need to flash it or how. So I think now it's time to do things the right way: updating the system using the update script instead of manually messing with uboot.

How can I do it? Do I need to format the internal flash in a special way and mount it? What boot command/params should I set it uboot? Is there a step by step tutorial anywhere?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #71 on: March 24, 2014, 11:27:54 PM »

I would like to update my GP+ kernel to the newest ones using the update script, but I don't know how to do it. Let me explain a bit more...

I'm running ArchLinux. Arch on GPs comes with a 3.1 kernel, but I am using 3.7.9 kernel downloaded from xilka. Until now I have been manually installing kernels from uboot via tftpboot/nand erase/nand write. So my GP+ reads the kernel from the NAND, and then the filesystem is mounted from the microSD card.

I was going to test manually updating to the latest 3.13 kernel, but now I see that not only the kernel image is needed, also the device tree must be flashed. And I don't know where do I need to flash it or how. So I think now it's time to do things the right way: updating the system using the update script instead of manually messing with uboot.

How can I do it? Do I need to format the internal flash in a special way and mount it? What boot command/params should I set it uboot? Is there a step by step tutorial anywhere?

Unfortunately I don't have a GP+ to test on, so here's how you probably want to proceed.

The kernel image is built with a device-tree backward compatibility mode,  If you look at the script you will see that it "merges" the zImage with the appropriate .dtb file.  When the zImage is loaded it looks for a .dtb that is appended to it's tail.  The .dtb describes the hardware and everything should work.

That merged zImage/.dtb can be in either system flash or on removable media (if your u-boot supports that).  If you look at the section that handles the original sheevaplug you should be able to duplicate that functionality for a GP+.

Please get back to me with patches if you decide to proceed with enhancing the UPDATE-KERNEL.sh script.

Logged

Pages: 1 ... 3 4 [5]
Print
Jump to: