public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: John Dallaway <jld@ecoscentric.com>,
	eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: New CPM/DPRAM allocator
Date: Wed, 19 Mar 2003 18:52:00 -0000	[thread overview]
Message-ID: <m3znnri3z1.fsf@miso.calivar.com> (raw)
In-Reply-To: <1048098401.9579.5496.camel@hermes.chez-thomas.org>

Gary Thomas <gary@mlbassoc.com> writes:

> 
> Only that the old code didn't use 0x2000 for it's buffers, but
> 0x2800 (for the serial ports).  The only driver that this should
> affect would be the serial driver in the installed RedBoot.  If
> the new allocator is using a different "base", then there should
> be no conflict.

OK. I hadn't realized that. Have you moved QUICC_BD_BASE before?
Could the original Adder RedBoot have been using 0x2000 too?

> 
> Do you recall what configurations/templates/etc you were using?

Nothing special. The standard net template with some config to give
the ethernet device a static IP address, and turn assertions
on. Nothing that would affect things at this level.

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

  reply	other threads:[~2003-03-19 18:52 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
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 [this message]
     [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=m3znnri3z1.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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).