* [U-Boot-Users] SoC Drivers: Where do they go?
@ 2008-05-06 16:21 McMullan, Jason
2008-05-06 17:49 ` Ben Warren
0 siblings, 1 reply; 2+ messages in thread
From: McMullan, Jason @ 2008-05-06 16:21 UTC (permalink / raw)
To: u-boot
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
And register header files go in:
include/asm-mips/arch-qux
ddr.h
spi.h
nand.h
ether.h
And the board-specific stuff (like DDR configs, PHY addresses, etc)
would go in:
board/foo/bar
config.mk
ether.c
ddr.c
...
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
jason.mcmullan at netapp.com
www.netapp.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080506/36d90e83/attachment.pgp
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot-Users] SoC Drivers: Where do they go?
2008-05-06 16:21 [U-Boot-Users] SoC Drivers: Where do they go? McMullan, Jason
@ 2008-05-06 17:49 ` Ben Warren
0 siblings, 0 replies; 2+ messages in thread
From: Ben Warren @ 2008-05-06 17:49 UTC (permalink / raw)
To: u-boot
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
> jason.mcmullan at netapp.com
> www.netapp.com
>
>
regards,
Ben
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-05-06 17:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-06 16:21 [U-Boot-Users] SoC Drivers: Where do they go? McMullan, Jason
2008-05-06 17:49 ` Ben Warren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox