From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0c1bc96da7b1bfe53510959b69e8b07b@9netics.com>
To: geoff@plan9.bell-labs.com, 9fans@9fans.net
Date: Thu, 13 May 2010 09:48:21 -0700
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <67b4fb8b76d32f954fd53fd84d757a66@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] arm ports update
Topicbox-Message-UUID: 20a3d3de-ead6-11e9-9d60-3106f5b1d025

thank you!

the two guruplugs i had ordered arrived today.  i was disappoint to
find that i'll need to order the JTAG board before i can do anything.
i didn't see this requirement when i ordered them over a month ago.
did anyone else miss this?

> The kw port now supports the Guruplug Server Plus, including both
> Ethernet interfaces, and probably the other Guruplugs.  booting(8) now
> has the necessary instructions to get started.  They are more diverse
> than one might like because every version of u-boot we get for a new
> board seems to have had the dhcp, bootp and tftp commands tinkered
> with to behave slightly differently.  We have two Guruplugs and one
> has been stable but the other is prone to random resets (and runs much
> warmer than the Sheevaplugs).  I'd be interested in hearing from
> anyone else who sees random resets.
>
> I've imported the flash memory support from native Inferno, other than
> the flash translation layer, which was developed for nor flash and is
> suspect with nand flash.  flash(3) describes the interface.  It seems
> to work on the Kirkwood boards, but I haven't exercised it
> extensively.  It does implement software ECC.  /dev/flash looks like
> it always returns zero bytes on the igepv2 board, but lack of
> documentation makes it a little hard to tell what to expect.