From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Where to store a header file
Date: Tue, 12 Oct 2010 10:28:04 +0200 [thread overview]
Message-ID: <201010121028.04871.jbe@pengutronix.de> (raw)
Hi,
currently I'm adding the i.MX28 architecture to barebox. This new CPU is the
successor of the i.MX23. So, it shares the most parts with it. But it also
shares the fact, its not a real i.MX like the i.MX27 is (STM378x-SigmaTel ->
i.MX23-Freescale).
But new to the i.MX28 is the FEC known from the i.MX family. To be able to
reuse the i.MX FEC driver (fec_imx.c) on the i.MX28 I need the "mach/iim.h"
from the "mach-imx" tree. As the i.MX23/28 itself is "mach-stm" this files
must be shared between these architectures. But where to store this
headerfile? In "arch/arm/include/asm/"? In "include/" (perhaps
as "include/imx_iim.h")? Or in "drivers/net/" as a local header file? Any
ideas?
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-8766-939 228 |
Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2010-10-12 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201010121028.04871.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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