From: Denys Dmytriyenko <denys@ti.com>
To: "Nelson, Sam" <sam.nelson@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
"Karicheri, Muralidharan" <m-karicheri2@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Subject: Re: Help needed: Devkit header files not upto date with kernel headers
Date: Tue, 9 Jul 2013 11:40:17 -0400 [thread overview]
Message-ID: <20130709154017.GD14185@edge> (raw)
In-Reply-To: <4F9216F96E5DF9428610502835A9F49054937C49@DLEE11.ent.ti.com>
On Tue, Jul 09, 2013 at 11:30:35AM -0400, Nelson, Sam wrote:
> Hello all,
>
> The header files under sysroots/armv7ahf-vfp-neon-oe-linux-gnueabi does
> not match the same file from the kernel tree.
That's normal. There's a difference between kernel and user-space facing
headers.
http://kernelnewbies.org/KernelHeaders
> For example
>
> Comparing the following 2 files, they are different.
>
> sysroots/armv7ahf-vfp-neon-oe-linux-gnueabi/usr/include/linux/ethtool.h
>
> and
>
> sysroots/armv7ahf-vfp-neon-oe-linux-gnueabi/usr/src/kernel/include/uapi/linux/ethtool.h
>
>
>
> Looking into some details, the /usr/include/linux/ethtool.h, seems to come
> from the libc package.
Yes, those are different even on my host machine. The first is marked as
_LINUX_ETHTOOL_H and the second one as _UAPI_LINUX_ETHTOOL_H
http://lwn.net/Articles/113349/
http://lwn.net/Articles/507794/
> Any ideas on what can be wrong in the recipes will be helpful. Is there
> any way to update the user space header files to match the kernel header
> files?
There is a special recipe for that - linux-libc-headers.
--
Denys
next prev parent reply other threads:[~2013-07-09 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:30 Help needed: Devkit header files not upto date with kernel headers Nelson, Sam
2013-07-09 15:40 ` Denys Dmytriyenko [this message]
2013-07-09 16:00 ` Nelson, Sam
2013-07-09 16:07 ` Denys Dmytriyenko
2013-07-09 18:18 ` Nelson, Sam
2013-07-09 18:37 ` Denys Dmytriyenko
2013-07-10 16:02 ` Nelson, Sam
2013-07-10 16:32 ` Denys Dmytriyenko
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=20130709154017.GD14185@edge \
--to=denys@ti.com \
--cc=m-karicheri2@ti.com \
--cc=meta-arago@arago-project.org \
--cc=sam.nelson@ti.com \
--cc=santosh.shilimkar@ti.com \
/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.