This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Redboot image load via PCI bus?
- From: Gary Thomas <gary at mlbassoc dot com>
- To: "Snider, Marc" <Marc dot Snider at icn dot siemens dot com>
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: 06 Nov 2003 11:13:14 -0700
- Subject: RE: [ECOS] Redboot image load via PCI bus?
- Organization: MLB Associates
- References: <DC26B4448BEC824C8C4E58845FF9F04CD6A387@Email2.west.icn.siemens.com>
On Thu, 2003-11-06 at 11:13, Snider, Marc wrote:
> Makes sense, Gary. Thanks for the pointers... Assuming I'm otherwise
> entirely comfortable with what version 1.3.1 provides, will I need to go to
> (do you advise) version 2.0 before making these mods or is 1.3.1 adequate?
>
1.3.1 is too out of date - don't even think about it.
Use the latest from CVS - that's the best approach.
>
> Thanks again,
> Marc
>
>
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Sent: Thursday, November 06, 2003 12:42 PM
> To: Snider, Marc
> Cc: 'ecos-discuss@sources.redhat.com'
> Subject: RE: [ECOS] Redboot image load via PCI bus?
>
>
> On Thu, 2003-11-06 at 10:37, Snider, Marc wrote:
> > 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...
> >
>
> Understood. If you look carefully at how the "load" command works,
> you won't need to make *any* changes directly to it, but just add a
> new I/O method. Also, I'd suggest that you put your new PCI method
> in your platform HAL - there is no need to mess about with the core
> of RedBoot.
>
> note: a lot of care has been taken (by me) to allow such extensions
> without any [direct] changes to the RedBoot tree.
>
> ... Ah, the joy of tables.
>
> > 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
--
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