On Wed, 3 Oct 2001, Jun Sun wrote:
> I talked about machine detection a while back. My idea is following:
> 0. all machines that are *configured* into the image will supply <my>_detect()
> and <my>_setup() functions.
> 1. at MIPS start up, we loop through all <my>_detect(), which returns three
> values, a) run-time detection negative, b) run-time detection positive, and c)
> no run-time detection code, but I return positive because I am configured in.
> 2. the startup code resolves conflicts (which sometimes may panic); and decide
> on one machine.
> 3. then the startup code calls the right <my>_setup() code which will set up
> the mach_type and other stuff.
I suppose you want to have struct containing pointers to both the detect() and
setup() functions, so you know which setup() function you have to call?
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- email@example.com
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds