On Mon, May 07, 2007 at 03:23:21PM +0200, Markus Klotzbücher wrote:
This is why I favor the old way of storing cpu dependant drivers in the appropriate cpu directory. This makes the responsibility clear and allows to cleanly seperate arch and generic code. Isn't this similar to linux where cpu dependant drivers are found in "arch/cpu/"?
No, quite the contrary. In Linux you will find even the cpu-specific drivers (like ethernet, uart, i2c driver etc) in the "drivers" directory. Only the board- and cpu-specific setup code and some additional code like interrupt controller implementation etc is normally found in the Linux "arch" directories.
There are complete drivers in arch/ppc/8260_io or arch/ppc/8xx_io for example, but I agree you're right in general.
Putting drivers into arch/cpu/* is evil, because manufacturers tend to reusing IP cores in other CPUs. So IMHO putting them into drivers/ is the right way to do it.
Robert