From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18101 invoked by alias); 6 Nov 2003 18:10:23 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 18088 invoked from network); 6 Nov 2003 18:10:22 -0000 Received: from unknown (HELO mail.siemenscom.com) (12.146.131.10) by sources.redhat.com with SMTP; 6 Nov 2003 18:10:22 -0000 Received: from imail1.icn.siemens.com (mail-stc.siemenscom.com [165.218.65.50]) by mail.siemenscom.com (8.9.3p092403/8.9.3) with ESMTP id KAA00008; Thu, 6 Nov 2003 10:07:19 -0800 (PST) Received: from boca210a.boca.ssc.siemens.com (boca210a.boca.ssc.siemens.com [165.218.12.110]) by imail1.icn.siemens.com (8.12.10/8.12.10) with ESMTP id hA6I4RM6024814; Thu, 6 Nov 2003 10:04:28 -0800 (PST) Received: by boca210a.boca.ssc.siemens.com with Internet Mail Service (5.5.2657.72) id ; Thu, 6 Nov 2003 13:10:19 -0500 Message-ID: From: "Snider, Marc" To: "'Gary Thomas'" Cc: "'ecos-discuss@sources.redhat.com'" Date: Thu, 06 Nov 2003 18:10:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [ECOS] Redboot image load via PCI bus? X-SW-Source: 2003-11/txt/msg00077.txt.bz2 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? 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 > MLB Associates -- Gary Thomas 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