linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Kumar Gala <kumar.gala@motorola.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [RFC] "indirect" DCR access (40x, BookE)
Date: Fri, 12 Mar 2004 08:20:23 -0800	[thread overview]
Message-ID: <20040312162023.GA24851@gate.ebshome.net> (raw)
In-Reply-To: <1921A482-7431-11D8-AFB6-000393DBC2E8@motorola.com>


On Fri, Mar 12, 2004 at 08:25:23AM -0600, Kumar Gala wrote:
>
> Look in u-boot.  They have some user commands that allow
> reading/writing dcr's.  These commands are written with self modifying
> code, I would recommend that we reuse that.
>

I would not.

Kumar, I'm aware of code in u-boot :).
Did you read this code comment ?

It clearly states that is not efficient.
It may be OK for a boot loader, because nobody cares much about it
performance.

Let me repeat my point. I _do_ know how to write self-modifying code,
I don't _like_ this approach mostly because it's not very efficient.

Eugene.

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

  parent reply	other threads:[~2004-03-12 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12  1:48 [RFC] "indirect" DCR access (40x, BookE) Eugene Surovegin
2004-03-12  2:46 ` Dan Malek
2004-03-12  3:05   ` Eugene Surovegin
2004-03-12  4:44     ` Stephen Williams
2004-03-12  4:54       ` Eugene Surovegin
2004-03-12 14:25         ` Kumar Gala
2004-03-12 14:53           ` Chuck Meade
2004-03-12 16:20           ` Eugene Surovegin [this message]
2004-03-12 18:01           ` Dan Malek
2004-03-19  4:00           ` Benjamin Herrenschmidt
2004-03-23  2:47             ` Eugene Surovegin
2004-04-01  5:36               ` Kumar Gala

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=20040312162023.GA24851@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=kumar.gala@motorola.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).