public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Snider, Marc" <Marc.Snider@icn.siemens.com>
To: "'Gary Thomas'" <gary@mlbassoc.com>
Cc: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Redboot image load via PCI bus?
Date: Thu, 06 Nov 2003 17:33:00 -0000	[thread overview]
Message-ID: <DC26B4448BEC824C8C4E58845FF9F04CD6A385@Email2.west.icn.siemens.com> (raw)

My thought was to provide the standard I/O device driver routines (open,
close, read...) on top of the PCI accesses and thus shield the higher layer
loader code.  I'd make it look like the image data was coming from somewhere
else like the flash.  It looks like do_load doesn't care where the image
data comes from as long as the native format (in my case likely SREC) is
maintained...

Yes, the host does have access to the memory on the target system, but it
would be preferable to pull the data from the host as opposed to pushing it
from there to the target...

Marc


-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Thursday, November 06, 2003 11:46 AM
To: Snider, Marc
Cc: 'ecos-discuss@sources.redhat.com'
Subject: Re: [ECOS] Redboot image load via PCI bus?


On Thu, 2003-11-06 at 09:45, Snider, Marc wrote:
> Is there a canned method implemented somewhere for loading an image via
the
> PCI bus (from another host), as opposed to using the network or loading
from
> flash?   I'd like to load an image from a control host across the PCI bus
> and then burn it to flash...   I'm assuming that if there isn't then I'll
> need to modify the do_load command and provide a set of I/O routines that
> map PCI accesses into standard I/O convention...
> 
> I'm on a PowerPC440 platform, if the platform matters.

What method would you use to access the image via the PCI?
Can your host access the memory on the board?

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-11-06 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 17:33 Snider, Marc [this message]
2003-11-06 17:41 ` Gary Thomas
  -- strict thread matches above, loose matches on Subject: below --
2003-11-06 18:10 Snider, Marc
2003-11-06 18:13 ` Gary Thomas
2003-11-06 16:41 Snider, Marc
2003-11-06 16:45 ` Gary Thomas

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=DC26B4448BEC824C8C4E58845FF9F04CD6A385@Email2.west.icn.siemens.com \
    --to=marc.snider@icn.siemens.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).