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: Wed, 10 Jul 2013 12:32:58 -0400 [thread overview]
Message-ID: <20130710163258.GB16407@edge> (raw)
In-Reply-To: <4F9216F96E5DF9428610502835A9F490549380FD@DLEE11.ent.ti.com>
On Wed, Jul 10, 2013 at 12:02:35PM -0400, Nelson, Sam wrote:
> If I have to back port, can you give me a list of files I may need to merge.
Sam,
Just one file linux-libc-headers_3.8.bb should be enough.
--
Denys
> -----Original Message-----
> From: Dmytriyenko, Denys
> Sent: Tuesday, July 09, 2013 2:38 PM
> To: Nelson, Sam
> Cc: meta-arago@arago-project.org; Karicheri, Muralidharan; Shilimkar, Santosh
> Subject: Re: Help needed: Devkit header files not upto date with kernel headers
>
> On Tue, Jul 09, 2013 at 02:18:24PM -0400, Nelson, Sam wrote:
> > Thanks for the detailed information.
> > So to update the headers I need to make changes in the linux-libc-headers recipe?
> >
> > Specifically, any update needed in
> > oe-core/meta/recipes-kernel/linux-libc-headers/linux-libc-header.inc
> > or
> > do I need to add a new recipe for the 3.8.4 header similar to the other recipes?
> >
> > oe-core/meta/recipes-kernel/linux-libc-headers$ ls
> > linux-libc-headers linux-libc-headers_3.4.3.bb
> > linux-libc-headers_3.0.8.bb linux-libc-headers.inc
> > linux-libc-headers_3.2.bb
> >
> > Any guidelines on what to update to get the latest headers for 3.8.4 kernel will be helpful.
>
> The easiest solution is to switch to using Dylan branches, once meta-arago is fully converted in the near future, which gives you linux-libc-headers-3.8 for free. Another option is to back-port it to Danny.
>
> --
> Denys
>
>
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Tuesday, July 09, 2013 12:07 PM
> > To: Nelson, Sam
> > Cc: meta-arago@arago-project.org; Karicheri, Muralidharan; Shilimkar, Santosh
> > Subject: Re: Help needed: Devkit header files not upto date with kernel headers
> >
> > Sam,
> >
> > Please see my last comment - there's a separate recipe for user-space kernel headers. The headers need to be properly exported, you cannot just use the ones from the kernel directly. Hence they are detached - updating the header in the kernel tree does not automatically update exported headers for the user space in linux-libc-headers.
> >
> > --
> > Denys
> >
> >
> > On Tue, Jul 09, 2013 at 12:00:34PM -0400, Nelson, Sam wrote:
> > > Understand the user space headers and kernel space headers are different in
> > > general. But in this case, I am comparing the files under "uapi" directory.
> > > Which I assume is actually meant for user space api. Am I wrong on this?
> > > Given that , I expected the header file will be updated in building the
> > > devkit.
> > >
> > > For example if we have update on an "uapi" header file , as part of a kernel
> > > patch, Don't we expect the corresponding header file in devkit to be
> > > updated? Appreciate your comments.
> > >
> > > With regards,
> > > Sam
> > >
> > >
> > > -----Original Message-----
> > > From: Dmytriyenko, Denys
> > > Sent: Tuesday, July 09, 2013 11:40 AM
> > > To: Nelson, Sam
> > > Cc: meta-arago@arago-project.org; Karicheri, Muralidharan; Shilimkar, Santosh
> > > Subject: Re: Help needed: Devkit header files not upto date with kernel headers
> > >
> > > 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/uap
> > > > i/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
prev parent reply other threads:[~2013-07-10 16:33 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
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 [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=20130710163258.GB16407@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.