All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Kavan <pkavan@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Including AT91 *.h files in arm-linux-gcc
Date: Fri, 30 Mar 2007 12:58:52 -0600	[thread overview]
Message-ID: <61c0054e0703301158sdb771a8p9ffa4150289d7de0@mail.gmail.com> (raw)

Hello All:

I am working on some code that requires me to include some of the
AT91-specific header files (e.g. gpio.h) that are in the
buildroot/build_arm/linux-2.6.20.3/include/asm-arm directory. I am
more of a hardware engineer than a software engineer, so this may seem
basic, but what is the best way to be able to include these files and
the others (e.g. asm/irq.h) without having to specify the paths, which
can get sticky when one *.h gile calls another and so on?

By the way, I am using buildroot configured for an AT91SAM9260.


Thanks.

Paul

-- 
***************************************
Paul David Kavan
Project Engineer
GRH Electronics, Inc.
402-734-4900
pkavan at gmail.com
***************************************

             reply	other threads:[~2007-03-30 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 18:58 Paul Kavan [this message]
2007-03-30 19:12 ` [Buildroot] Including AT91 *.h files in arm-linux-gcc Ulf Samuelsson

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=61c0054e0703301158sdb771a8p9ffa4150289d7de0@mail.gmail.com \
    --to=pkavan@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.