public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: John Dallaway <jld@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: New CPM/DPRAM allocator
Date: Wed, 19 Mar 2003 13:02:00 -0000	[thread overview]
Message-ID: <m3znnrk420.fsf@miso.calivar.com> (raw)
In-Reply-To: <200303191019.45969.jld@ecoscentric.com>

John Dallaway <jld@ecoscentric.com> writes:

> A few of questions:
> 
> 1) Does this incompatibilty affect _all_ targets which run both RedBoot and 
> eCos?

Just PowerPC QUICC targets, like the MBX, Adder or Viper, for example.

> 2) Could the new allocator implementation be modified in any way to preserve 
> compatibility?

Possibly. But I'll defer to Gary on this one.

> 3) To what extent might the new allocator perturb eCos functionality other 
> than by a stepwise "it will work or it will be completely broken".

It shouldn't affect anything else. Failure modes are hard to specify
since they depend on the contents of what is currently an
uninitialized location in RAM. Different instances of RedBoot might
have different values there.

We might even be able to add a test to the DPRAM code to detect an old
RedBoot and generate an error message before proceeding.

> 4) Is a further break in compatibility possible as potential issues with the 
> new allocator are ironed out?

Unlikely. The code is only a handful of lines. 

> 
> We need to determine how to manage the switch over to the new CPM/DPRAM 
> allocator smoothly for everyone. From my perspective, it is certainly 
> unfortunate that this innovation has arrived between 2.0 beta and 2.0 
> final. Were it not for the break in compatibility, I would vote against 
> incorporating this change for 2.0 final since the change will (to a certain 
> extent) invalidate beta testing by the net community. However, it would 
> also be undesirable for 2.0 final RedBoot to be incompatible with anonCVS 
> eCos from day 1. Users are likely to want to stick with a release version 
> of the firmware while experimenting with eCos from anonCVS.
> 

It only affects a handful of boards: MBX, VIPER, ADDER, TS1000. QUICC2
targets like the tS6 and VADS are not affected, and non-QUICC MPC8xx
targets like the CMA28x and FADS boards are not affected.

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

  reply	other threads:[~2003-03-19 13:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  8:47 Patches for the eCos 2.0 branch John Dallaway
2003-03-18 13:48 ` Gary Thomas
2003-03-18 16:04   ` Proposal for processing patches " John Dallaway
2003-03-18 17:25     ` Jonathan Larmour
2003-03-18 18:21       ` Nick Garnett
2003-03-18 18:56     ` Andrew Lunn
2003-04-12  5:00       ` Jonathan Larmour
2003-04-14  7:28         ` Andrew Lunn
2003-03-18 19:01     ` Andrew Lunn
2003-03-18 22:58       ` Jonathan Larmour
2003-03-18 19:16     ` SNMP for FreeBSD Andrew Lunn
2003-03-19 13:22       ` Jonathan Larmour
2003-03-19 14:23         ` Gary Thomas
2003-03-19 18:07         ` Nick Garnett
2003-03-25 17:01       ` Andrew Lunn
2003-03-19 14:22     ` 2.0 branch: mn10300 debug info patch Bart Veer
2003-03-19 14:40       ` John Dallaway
2003-03-19 18:07       ` Nick Garnett
2003-03-18 18:09   ` Patches for the eCos 2.0 branch Nick Garnett
2003-03-18 18:25     ` Gary Thomas
2003-03-18 19:05       ` Nick Garnett
2003-03-18 19:13         ` Gary Thomas
2003-03-19 10:18           ` New CPM/DPRAM allocator John Dallaway
2003-03-19 13:02             ` Nick Garnett [this message]
2003-03-19 14:38               ` Gary Thomas
2003-03-19 15:44               ` John Dallaway
2003-03-19 17:06                 ` Gary Thomas
2003-03-19 18:22                   ` Nick Garnett
2003-03-19 18:26                     ` Gary Thomas
2003-03-19 18:52                       ` Nick Garnett
     [not found]                         ` <1048100525.7462.5617.camel@hermes.chez-thomas.org>
2003-03-19 19:21                           ` Nick Garnett
2003-03-20 13:02                           ` Nick Garnett
2003-03-20 13:14                             ` Gary Thomas
2003-03-20 18:11                               ` Nick Garnett

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=m3znnrk420.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jld@ecoscentric.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).