Hi Jason, McMullan, Jason wrote: > I'm writing the drivers for a MIPS 4KEc based SoC, and was wondering > where they should go in the source code tree. > > Having done ARM in the past, my first guess would be (calling the SoC > 'qux', made by company 'foo', and a 'bar' eval board for now): > > cpu/mips/qux > spi.c > nand.c > ether.c > > It's definitely preferable to put drivers in the 'drivers' directory than tied to the CPU. You'll see subdirectories for spi, mtd/nand and net. > And register header files go in: > > include/asm-mips/arch-qux > ddr.h > spi.h > nand.h > ether.h > > Network driver headers typically go with the C code (drivers/net). I'll let other people chime in about the other peripherals, because I'm not clear on the preferred approach. > And the board-specific stuff (like DDR configs, PHY addresses, etc) > would go in: > > board/foo/bar > config.mk > ether.c > ddr.c > ... > > In general this is correct, although a lot of board-specific stuff is #defined in config files. > I only ask, because there is no SoC directories under 'cpu/mips', nor > any SoC directories under 'include/asm-mips' > > > Jason McMullan > MTS SW > System Firmware > > NetApp > 724.741.5011 Fax > 724.741.5166 Direct > 412.656.3519 Mobile > [EMAIL PROTECTED] > www.netapp.com > > regards, Ben
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
