From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] arm ports update
Date: Thu, 13 May 2010 12:56:02 -0700 [thread overview]
Message-ID: <AANLkTilMVy_IYQZMDXxVaSqUS0ONI5VzZn8_LXHEKrzv@mail.gmail.com> (raw)
In-Reply-To: <55A04A20-1074-42EA-9432-B364ABA6574F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
Awesome! Looks like the big one can do 2x GigE and some home automation
stuff. Sounds like good fun for Plan 9.
On Thu, May 13, 2010 at 12:30 PM, Gorka Guardiola <paurea@gmail.com> wrote:
> In the sheeva you can access the Jtag through the usb port...
>
> -
> Curiosity sKilled the cat
>
> G.
>
>
> On May 13, 2010, at 6:48 PM, Skip Tavakkolian <9nut@9netics.com> wrote:
>
> 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.
>>>
>>
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2457 bytes --]
next prev parent reply other threads:[~2010-05-13 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 3:42 geoff
2010-05-13 4:24 ` Jacob Todd
2010-05-13 10:41 ` Charles Forsyth
2010-05-13 16:06 ` Boo
2010-05-13 16:48 ` Skip Tavakkolian
2010-05-13 16:58 ` David Leimbach
2010-05-13 19:30 ` Gorka Guardiola
2010-05-13 19:56 ` David Leimbach [this message]
2010-05-13 20:56 ` Skip Tavakkolian
2010-05-13 21:05 ` David Leimbach
2010-05-13 22:29 ` Skip Tavakkolian
2010-05-14 3:29 ` David Leimbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilMVy_IYQZMDXxVaSqUS0ONI5VzZn8_LXHEKrzv@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).