Thread (2 messages) 2 messages, 2 authors, 2002-07-25

Re: [RFC/Patch] 4xx idle loop

From: Matthew Locke <hidden>
Date: 2002-07-25 16:51:05

Possibly related (same subject, not in this thread)

cort@fsmlabs.com wrote:
There's need for the indirection for this sort of thing.  The only reason
I created ppc_md was to allow for different machines to run off a single
binary but not different chip families.

A big #ifdef for the chip-type would work fine since the chip family is
known at compile time.  The machine type isn't always know which is the
reason for ppc_md.
I thought one of the linuxppc desgin goals was to keep the ifdefs to a
minimum.  I can see idle.c growing quite large and full of #ifdefs if we
do it that way.  Rather than using ppc_md, make power_save an
abstraction similar to platform_init.

} This sounds like a good idea if we could use
}   if( ppc_md.powersave != NULL)
}        ppc_md.powersave();
}
} If it is determined that calling power_save() which is resides in an
} arch/processor specific file then we are talking about many files being
} hit.  and the current power_save seems to common for many other ppc
} platforms other than 4xx & 8xx

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help