From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SoC Drivers: Where do they go?
Date: Tue, 06 May 2008 10:49:35 -0700 [thread overview]
Message-ID: <48209A2F.20408@gmail.com> (raw)
In-Reply-To: <1210090863.8220.16.camel@mcmullan-linux.cifs.lab.netapp.com>
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
prev parent reply other threads:[~2008-05-06 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 16:21 [U-Boot-Users] SoC Drivers: Where do they go? McMullan, Jason
2008-05-06 17:49 ` Ben Warren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48209A2F.20408@gmail.com \
--to=biggerbadderben@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox