From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott McNutt <smcnutt@psyent.com>
Date: Tue, 20 Apr 2010 17:37:08 -0400
Subject: [U-Boot] Is there a better way?
In-Reply-To: <20100420195955.GJ7651@ovro.caltech.edu>
References: <k2m7753e5291004201201u401d9a82xa172216f44d6312b@mail.gmail.com>
	<20100420195955.GJ7651@ovro.caltech.edu>
Message-ID: <4BCE1E84.7000007@psyent.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Chris,

Ira W. Snyder wrote:
>> My problem:
>> If I have an in-memory filesystem on my board (the ramdisk), and I have the
>> entire 256MB of memory accessible to the host over the PCI bus, you'd think
>> I could write a tool (or find a tool) that I could point at a block of
>> physical memory and have it recognize it as an ext2 filesystem and read it
>> as such. Unfortunately, there doesn't appear to be a precedent for doing
>> this. Is there a better way to accomplish my goal of getting my logs off the
>> ramdisk on the board from the host?
>>
> 
> I've solved a relatively similar problem here. I have a
> mpc8349emds-based board that is a PCI target. I've written a couple of
> smallish drivers for U-Boot and Linux that make the board seem like an
> ethernet interface.

Ditto. Ira's suggestion is a very elegant and useful technique ... and
has been used successfully for many applications.

> We tftp our kernel and boot our board over NFS using the "ethernet"
> interface.

As Ira suggests, once your target appears as an addressable host, the
sky's the limit. You can telnet/ssh into your target, run tftpd,
run a web server for configuration/status, etc. Cool stuff!

Regards,
--Scott