All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Gorny Krystian <krystian.gorny@wipotec.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Kernel header missing for specific Target
Date: Fri, 17 Jul 2015 11:39:34 -0400	[thread overview]
Message-ID: <55A921B6.7050902@windriver.com> (raw)
In-Reply-To: <10D57FBA9FD7C14FB49EE17590E1AF9453C901FD@svr-exc-03.intern.wipotec.de>

On 15-07-17 09:55 AM, Gorny Krystian wrote:
> I'm using the fido branch. My iointerrupt.bb file looks as follow:
>
>
> DESCRIPTION = "Simple IO-interrupt driver"
> SECTION = "iointerrupt"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
> PR = "r0"
>
> SRC_URI = "file://drv_iointerrupt.c"
> S = "${WORKDIR}"
> do_compile() {
>               ${CC} drv_iointerrupt.c -o iointerrupt
> }

And so I'm clear .. this is a standard .ko ? Or a userspace kernel driver ?

If you are looking for the internal kernel sources to be on the include
path, you need to reference STAGING_KERNEL_DIR (and something has to
depend on the kernel do_shared_workdir task to get the right bits
in place).

  recipes-kernel/lttng/lttng-modules_2.6.1.bb

Is an example of both.

Bruce

> do_install() {
>               install -d ${D}${bindir}
>               install -m 0755 iointerrupt ${D}${bindir}
> }
>
> Thanks,
> Krystian
>
> _____________________________________________________________________
>
> Krystian Gorny
> Research & Development
>
> Wipotec GmbH
> Adam-Hoffmann-Str. 26
> 67657 Kaiserslautern
>
> T +49.631.34146-0
> F +49.631.34146-8640
> http://www.wipotec.com
>
>
> _____________________________________________________________________
>
> Weigh Cells | Weighing systems
>
> See our solutions. Visit us at our events
> http://www.wipotec.com/de/aktuelles/veranstaltungen/
>
> _____________________________________________________________________
>
> Legal information:
> Wipotec Wiege- und Positioniersysteme GmbH
> HRB 2317 Kaiserslautern, Management: T. D?ppre, U. Wagner
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any unauthorized
> copying, disclosure or distribution of the material in this e-mail is strictly
> forbidden.
>
> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
> Sent: Friday, July 17, 2015 3:32 PM
> To: Gorny Krystian; yocto@yoctoproject.org
> Subject: Re: [yocto] Kernel header missing for specific Target
>
> On 15-07-17 08:47 AM, Gorny Krystian wrote:
>> Hi
>>
>> I try add to my core-image-rt image on a x86 arch my own IO driver. I
>> have already my own recipe, for normal user space programs everything
>> is working fine.
>>
>> For the kernel space driver Yocto is missing at do_comile task the
>> asm/atomic.h header file. I have searched for the atomic.h file and
>> found a lot of them in the ./build/tmp/work folder. Yocto should use
>> one of them for the right hardware architecture right? Or is the a
>> something else I have forget to do?
>
> What Yocto branch are you using ?
>
> atomic.h is placed in the right location by the kernel build, assuming that your driver recipe has the proper dependencies.  Without seeing that recipe, it is hard to say more.
>
> Cheers,
>
> Bruce
>
>>
>> Many thanks
>>
>> Krystian
>>
>>
>> _____________________________________________________________________
>>
>> *Krystian Gorny*
>> Research & Development
>>
>> Wipotec GmbH
>> Adam-Hoffmann-Str. 26
>> 67657 Kaiserslautern
>>
>> T +49.631.34146-0
>> F +49.631.34146-8640
>> http://www.wipotec.com
>>
>>
>>
>> <http://www.wipotec.com>
>>
>> Legal information:
>> Wipotec Wiege- und Positioniersysteme GmbH HRB 2317 Kaiserslautern,
>> Management: T. Düppre, U. Wagner
>>
>> This e-mail may contain confidential and/or privileged information.
>> If you are not the intended recipient (or have received this e-mail in
>> error)
>> please notify the sender immediately and delete this e-mail. Any
>> unauthorized copying, disclosure or distribution of the material in
>> this e-mail is strictly forbidden.
>>
>>
>
>



  reply	other threads:[~2015-07-17 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 12:47 Kernel header missing for specific Target Gorny Krystian
2015-07-17 13:32 ` Bruce Ashfield
2015-07-17 13:55   ` Gorny Krystian
2015-07-17 15:39     ` Bruce Ashfield [this message]
     [not found]       ` <10D57FBA9FD7C14FB49EE17590E1AF9453C90E9E@svr-exc-03.intern.wipotec.de>
2015-07-23 13:33         ` Bruce Ashfield
2015-07-17 15:18 ` Kernel header files missing Louis Ryan

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=55A921B6.7050902@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=krystian.gorny@wipotec.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.