RE: [ECOS] ROMRAM stand-alone application

RE: [ECOS] ROMRAM stand-alone application

[Alan Bowman]

> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: 08 April 2004 09:53
> To: Gary Thomas
> Cc: Andrew Lunn; Alan Bowman; ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] ROMRAM stand-alone application
> 
> 
> > Also make sure that this change doesn't break the exiting 
> ROMRAM RedBoot
> > on the board :-)
> 
> Does the ROMRAM redboot actually work? To me it looks like it would
> not.
> 
>         Andrew
> 
> 

I don't think it's ever worked for me (before the changes that I'm hopefully about to post).  I'm trying to access the CVS server, and I can't seem to get a response.  Is it working at the moment?

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

RE: [ECOS] ROMRAM stand-alone application

[Gary Thomas]

Alan Bowman said:
>
>
>> -----Original Message-----
>> From: Andrew Lunn [mailto:andrew@lunn.ch]
>> Sent: 08 April 2004 09:53
>> To: Gary Thomas
>> Cc: Andrew Lunn; Alan Bowman; ecos-discuss@sources.redhat.com
>> Subject: Re: [ECOS] ROMRAM stand-alone application
>>
>>
>> > Also make sure that this change doesn't break the exiting
>> ROMRAM RedBoot
>> > on the board :-)
>>
>> Does the ROMRAM redboot actually work? To me it looks like it would
>> not.
>>
>>         Andrew
>>
>>
>
> I don't think it's ever worked for me (before the changes that I'm hopefully about to post).  I'm
> trying to access the CVS server, and I can't seem to get a response.  Is it working at the moment?

It may not be - there were reports of hardware problems on that machine
earlier today and at the moment it may be offline.



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

Re: [ECOS] ROMRAM stand-alone application

[Nick Garnett]

Andrew Lunn <andrew@lunn.ch> writes:

> > > I don't think it's ever worked for me (before the changes that I'm
> > > hopefully about to post).  I'm trying to access the CVS server, and
> > > I can't seem to get a response.  Is it working at the moment?
> > 
> > The ROMRAM RedBoot fell by the wayside. With so little RAM available
> > on these boards it was felt that it was a waste of resource. Hence the
> > ROMRAM .ldi files have suffered a little bitrot.
> 
> We have two options. Fix the bitrot so that ROMRAM RedBoot works
> again, or change the ROMRAM so that it works for standalone
> applications.
> 
> Nick says that ROMRAM redboot makes little sense, so i would suggest
> the second option. Is everybody happy with that?

I would vote for making it work for standalone apps only. To make
ROMRAM Redboot work would mean moving the load point for RAM apps up
in memory for both RAM and ROMRAM RedBoots. This would waste RAM in
the ROM RedBoot case, and would give RAM apps less room in both cases.

Of course if we were clever, we could put in some CDL to make it
impossible to configure ROMRAM RedBoots.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


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

Re: [ECOS] ROMRAM stand-alone application

[Nick Garnett]

Alan Bowman <ABowman@synaptics-uk.com> writes:

> > -----Original Message-----
> > From: Andrew Lunn [mailto:andrew@lunn.ch]
> > Sent: 08 April 2004 09:53
> > To: Gary Thomas
> > Cc: Andrew Lunn; Alan Bowman; ecos-discuss@sources.redhat.com
> > Subject: Re: [ECOS] ROMRAM stand-alone application
> > 
> > 
> > > Also make sure that this change doesn't break the exiting 
> > ROMRAM RedBoot
> > > on the board :-)
> > 
> > Does the ROMRAM redboot actually work? To me it looks like it would
> > not.
> > 
> >         Andrew
> > 
> > 
> 
> I don't think it's ever worked for me (before the changes that I'm
> hopefully about to post).  I'm trying to access the CVS server, and
> I can't seem to get a response.  Is it working at the moment?

The ROMRAM RedBoot fell by the wayside. With so little RAM available
on these boards it was felt that it was a waste of resource. Hence the
ROMRAM .ldi files have suffered a little bitrot.

The sources.redhat.com server is currently experiencing some disk
problems and CVS access has been turned off. We will probably have to
wait until a RedHat person can take a look at it in the morning, US
time.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


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

Re: [ECOS] ROMRAM stand-alone application

[Andrew Lunn]

> > I don't think it's ever worked for me (before the changes that I'm
> > hopefully about to post).  I'm trying to access the CVS server, and
> > I can't seem to get a response.  Is it working at the moment?
> 
> The ROMRAM RedBoot fell by the wayside. With so little RAM available
> on these boards it was felt that it was a waste of resource. Hence the
> ROMRAM .ldi files have suffered a little bitrot.

We have two options. Fix the bitrot so that ROMRAM RedBoot works
again, or change the ROMRAM so that it works for standalone
applications.

Nick says that ROMRAM redboot makes little sense, so i would suggest
the second option. Is everybody happy with that?

    Andrew

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

Re: [ECOS] ROMRAM stand-alone application

[Gary Thomas]

Andrew Lunn said:
>> > I don't think it's ever worked for me (before the changes that I'm
>> > hopefully about to post).  I'm trying to access the CVS server, and
>> > I can't seem to get a response.  Is it working at the moment?
>>
>> The ROMRAM RedBoot fell by the wayside. With so little RAM available
>> on these boards it was felt that it was a waste of resource. Hence the
>> ROMRAM .ldi files have suffered a little bitrot.
>
> We have two options. Fix the bitrot so that ROMRAM RedBoot works
> again, or change the ROMRAM so that it works for standalone
> applications.
>
> Nick says that ROMRAM redboot makes little sense, so i would suggest
> the second option. Is everybody happy with that?

Sure - it at least sounds like it's not a step backwards.

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

[ECOS] Re: ROMRAM stand-alone application

[John Dallaway]

Nick Garnett wrote:

> I would vote for making it work for standalone apps only. To make
> ROMRAM Redboot work would mean moving the load point for RAM apps up
> in memory for both RAM and ROMRAM RedBoots. This would waste RAM in
> the ROM RedBoot case, and would give RAM apps less room in both cases.

That seems sensible.

> Of course if we were clever, we could put in some CDL to make it
> impossible to configure ROMRAM RedBoots.

Simply removing the redboot_ROMRAM.ecm files in each of the AT91EBxx 
platform HALs should clarify this.

John Dallaway
eCosCentric Limited

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