All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Ankit Rastogi <Ankit.Rastogi@kpit.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to export kernel specific headers to userspace
Date: Mon, 18 Jun 2018 23:50:55 -0700	[thread overview]
Message-ID: <5f718157-9d74-90c3-777f-47d436e9f814@gmail.com> (raw)
In-Reply-To: <BM1PR0101MB12830193263FDC30B66D225E91700@BM1PR0101MB1283.INDPRD01.PROD.OUTLOOK.COM>



On 6/18/18 10:19 PM, Ankit Rastogi wrote:
> Hi,
> 
> 
> Can someone provide any pointers on how to export kernel specific 
> headers to userspace?
> 
> I am getting below error while building our one of the component which 
> requires kernel uapi headers.
> 
> Error Received:
>   /hdmi-capture/main.c:16:10: fatal error: linux/hdmi_info.h: No such 
> file or directory
>> |  #include <linux/hdmi_info.h>
>> |           ^~~~~~~~~~~~~~~~~~~
>> | compilation terminated.
> 
> In yocto 2.5, userspace is boot strapped with linux-libc-headers package 
> which uses a set of uapi headers from Linux kernel 4.15. Can someone 
> suggest for custom kernels, how to expose uapi headers to userspace? 
> Thus create a separate linux-apl-headers package with those files.
> 

you can write your own kernel headers recipe and make that preferred 
provider.

or you can add patch to existing recipe.

I would suggest that be careful to expose the APIs here, if its already 
an UAPI in later versions of kernel and you are backporting to an older 
version it might be fine but ramdom header export would land you in 
problems later.

> Thanks,
> Ankit
> 
> This message contains information that may be privileged or confidential 
> and is the property of the KPIT Technologies Ltd. It is intended only 
> for the person to whom it is addressed. If you are not the intended 
> recipient, you are not authorized to read, print, retain copy, 
> disseminate, distribute, or use this message or any part thereof. If you 
> receive this message in error, please notify the sender immediately and 
> delete all copies of this message. KPIT Technologies Ltd. does not 
> accept any liability for virus infected mails.
> 


  reply	other threads:[~2018-06-19  6:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  5:16 How to export kernel specific headers to userspace Ankit Rastogi
2018-06-19  5:19 ` Ankit Rastogi
2018-06-19  6:50   ` Khem Raj [this message]
2018-06-19 13:22 ` Richard Purdie
2018-06-19 13:56   ` Bruce Ashfield
2018-06-19 13:44 ` Bas Mevissen
2018-06-19 13:55   ` Bruce Ashfield
2018-06-19 14:06     ` Bas Mevissen

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=5f718157-9d74-90c3-777f-47d436e9f814@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=Ankit.Rastogi@kpit.com \
    --cc=yocto@yoctoproject.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 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.