From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Location of headers for IP blocks
Date: Mon, 22 Mar 2010 17:23:56 +0100 [thread overview]
Message-ID: <m2ljdks4tf.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4BA3C74A.1050901@psyent.com> (Scott McNutt's message of "Fri, 19 Mar 2010 14:49:46 -0400")
Hi Scott,
> When an IP block can be shared among several different
> architectures, where should the _header_ files be located?
>
> Examples of such blocks would be OpenCores peripherals,
> Altera peripherals, etc.
>
> Some peripherals may not need to export any interfaces,
> so no header file is necessary. But this certainly is not
> the case for all peripherals.
>
> Any precedents, comments, suggestions?
Linux is always a good precedent, so checking there should give us a
clue.
Apart from that I'd go for include/device-type/... Names of
manufacturers change _way_ too often :)
Cheers
Detlev
--
Another helpful hint for successful MIME processing:
application/msword; rm -f %s; description="MS Word Text";
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
prev parent reply other threads:[~2010-03-22 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 18:49 [U-Boot] Location of headers for IP blocks Scott McNutt
2010-03-22 16:23 ` Detlev Zundel [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=m2ljdks4tf.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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