From: Paul M. <le...@li...> - 2003-04-19 04:36:59
|
On Fri, Apr 18, 2003 at 02:13:18PM +0900, Masahiro Abe wrote: > We needed to distinguish each configuration from software standpoint, > both in driver and in user-mode apps. So, we've modified machvec a > little and also added entry to /proc for being able to see the machine > information. > > Mr. Hiroki HATTORI of Computron have developed those code for us. He'd > been inspired by the idea in linux-arm/xscale tree. > > Any suggestions/opinions welcomed. > In 2.5 we deal with this a little differently, and there are some more changes pending that'll clean up most of the rest of the machvec identification stuff. At the moment each board is responsible for defining its own get_system_type(), which is a unique string identifying the board. cpuinfo reports that, the processor family, and the processor subtype. One thing I liked that the ARM tree had done was the mach-types generation scripts in arch/arm/tools. For 2.5, I wrote something similar (which hasn't been commited yet) which dynamically built a lot of the machvec identification info. This in turn also allows for things like checking mach_is_dreamcast(), which are all built up dynamically. All that is necessary is to keep the board list up to date with the corresponding Kconfig entry and a few other minor things. If there is interest in something like that, I'll tidy up what i have sitting around and post it. I'd like to avoid seeing too much being shoved into the machvec, since ideally it'll be removed in the not too distant future in its entirety. Thoughts? |