linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: "Mark S. Mathews" <mark@absoval.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: rpx_cfg() copy to NVRAM?
Date: Tue, 30 May 2000 12:22:07 -0400	[thread overview]
Message-ID: <3933EAAF.C6C5C2A0@embeddededge.com> (raw)
In-Reply-To: Pine.LNX.3.96.1000530110746.8009A-100000@tristar.cc.absoval.com


"Mark S. Mathews" wrote:

> It appears to be copying the eeprom data to NVRAM.  Is anyone using this?

No, get rid of it.  It is some forgotten debug code from long ago.
I'll remove it from all of the sources I can find.

Sorry about that.  Thanks for pointing it out.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-05-30 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-30 15:11 rpx_cfg() copy to NVRAM? Mark S. Mathews
2000-05-30 16:03 ` Matthew Locke
2000-05-30 16:23   ` Dan Malek
2000-05-30 16:34     ` Mark S. Mathews
2000-05-30 16:30   ` Mark S. Mathews
2000-05-30 16:22 ` Dan Malek [this message]

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=3933EAAF.C6C5C2A0@embeddededge.com \
    --to=dan@netx4.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mark@absoval.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 NNTP newsgroup(s).