From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SDK for BeagleBoard development - how do I add linux-omap headers?
Date: Thu, 08 Apr 2010 08:50:04 +0200 [thread overview]
Message-ID: <4BBD7C9C.2020404@gmail.com> (raw)
In-Reply-To: <mailman.2582.1270656222.24517.openembedded-devel@lists.openembedded.org>
>
> Like the topic says I'm trying to create an SDK to let people develop
> > for a BeagleBoard running Angstrom. I have followed the instructions in
> > the manual on creating an SDK, and have a basic one compiled.
> >
> > I included linux-libc-headers, but found out that it gives me only the
> > "vanilla" kernel-headers, while I need the linux-omap-headers with all
> > the needed patches. How do I get those into the SDK?
>
> Why do you need these headers?
>
We have code that writes video directly into framebuffer, and it needs
to include <"linux/omapfb.h">.
next parent reply other threads:[~2010-04-08 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2582.1270656222.24517.openembedded-devel@lists.openembedded.org>
2010-04-08 6:50 ` Tasslehoff Kjappfot [this message]
2010-04-07 11:01 SDK for BeagleBoard development - how do I add linux-omap headers? Tasslehoff Kjappfot
2010-04-07 12:18 ` Holger Hans Peter Freyther
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=4BBD7C9C.2020404@gmail.com \
--to=tasskjapp@gmail.com \
--cc=openembedded-devel@lists.openembedded.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