linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christian Zankel <chris@mvista.com>,
	cort@fsmlabs.com, linuxppc-dev@lists.linuxppc.org,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: bootloader & head.S weirdness & restructuring
Date: Thu, 25 Nov 1999 14:49:35 -0500	[thread overview]
Message-ID: <383D92CF.6ECD12D3@netx4.com> (raw)
In-Reply-To: Pine.LNX.4.05.9911251809390.7807-100000@callisto.of.borg


Geert Uytterhoeven wrote:


> Alternatively, you can base your decisions on specific features that are shared
> among different machine types, and say
> 
>     if (has_feature_a) {
>         ...
>     }
> 
> instead of
> 
>     #if defined(CONFIG_x) || defined(CONFIG_y) || defined(CONFIG_z)
>     ...
>     #endif


Yes, but one of the things I am trying to do is reduce the
code size and instructions to execute.  On a 500 MHz G4 with
a Gigabyte of memory, a few extra instructions is no big deal.
On a 33 MHz 8xx with 8 Mbytes of memory, you watch all of this
pretty closely :-).


	-- Dan

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

  reply	other threads:[~1999-11-25 19:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-22 11:04 bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-22 21:37 ` Cort Dougan
1999-11-22 23:17   ` bootloader & head.S weirdness & restructuring Christian Zankel
1999-11-22 23:55     ` Cort Dougan
1999-11-23  3:31       ` Christian Zankel
1999-11-23  3:40         ` Cort Dougan
1999-11-23  6:37           ` Dan Malek
1999-11-23 18:22             ` Christian Zankel
1999-11-23 20:20               ` Dan Malek
1999-11-25 17:13                 ` Geert Uytterhoeven
1999-11-25 19:49                   ` Dan Malek [this message]
1999-11-26  9:06                     ` Geert Uytterhoeven
1999-11-26  9:42                       ` Michael Schmitz
1999-11-26 12:06                         ` Wolfgang Denk
1999-11-28 22:41                       ` Dan Malek
1999-11-29  7:12                         ` Geert Uytterhoeven
1999-11-23 16:12       ` Michael Schmitz
1999-11-23 16:17       ` David Edelsohn
1999-11-23 17:46         ` Cort Dougan
1999-11-23 16:15     ` Gabriel Paubert
1999-11-23 16:52       ` Marcus Sundberg
1999-11-23 17:01         ` Gabriel Paubert
1999-11-23 17:45           ` Cort Dougan
1999-11-23 10:35   ` bootloader & head.S weirdness Benjamin Herrenschmidt
1999-11-23 10:50     ` Momchil Velikov

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=383D92CF.6ECD12D3@netx4.com \
    --to=dan@netx4.com \
    --cc=chris@mvista.com \
    --cc=cort@fsmlabs.com \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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).