public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail•com>
To: ppcembed <linuxppc-embedded@ozlabs•org>
Subject: Header files for 440?
Date: Thu, 31 Mar 2005 15:24:38 -0800	[thread overview]
Message-ID: <c3d0340b0503311524702eed28@mail.gmail.com> (raw)

Hi,

Are there any criteria to define things on so many different header
files for 440 family chips? For example, an Ocotea board has the
following header files.

1. <asm/ibm44x.h>
2. <syslib/ibm440gx_common.h>
3. <syslib/ibm44x_common.h>
4. <platforms/4xx/ibm440gx.h>
5. <platforms/4xx/ocotea.h>

I can understand the reasons why there are ibm44x.h, ibm440gx.h, and
ocotea.h. But why do we need to separate ibm44x_common.h from ibm44x.h
and ibm440gx.h from ibm440gx_common.h? Can we just simply combine them
together? It's a little confusing on what definitions and declarations
should be which files.

Is there any guildeline saying what header file should be in
<asm-ppc/*>, <syslib/*>, or <platforms/4xx/*>?

Any explanations?

Thanks,
-Shawn.

                 reply	other threads:[~2005-03-31 23:24 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=c3d0340b0503311524702eed28@mail.gmail.com \
    --to=shawnxjin@gmail$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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