* Kernel header missing for specific Target @ 2015-07-17 12:47 Gorny Krystian 2015-07-17 13:32 ` Bruce Ashfield 2015-07-17 15:18 ` Kernel header files missing Louis Ryan 0 siblings, 2 replies; 6+ messages in thread From: Gorny Krystian @ 2015-07-17 12:47 UTC (permalink / raw) To: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 1286 bytes --] 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? 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/fileadmin/user_upload/Signatur/W_Standard.jpg]<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. [-- Attachment #2: Type: text/html, Size: 3581 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Kernel header missing for specific Target 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:18 ` Kernel header files missing Louis Ryan 1 sibling, 1 reply; 6+ messages in thread From: Bruce Ashfield @ 2015-07-17 13:32 UTC (permalink / raw) To: Gorny Krystian, yocto@yoctoproject.org 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. > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Kernel header missing for specific Target 2015-07-17 13:32 ` Bruce Ashfield @ 2015-07-17 13:55 ` Gorny Krystian 2015-07-17 15:39 ` Bruce Ashfield 0 siblings, 1 reply; 6+ messages in thread From: Gorny Krystian @ 2015-07-17 13:55 UTC (permalink / raw) To: Bruce Ashfield, yocto@yoctoproject.org 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 } 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. > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Kernel header missing for specific Target 2015-07-17 13:55 ` Gorny Krystian @ 2015-07-17 15:39 ` Bruce Ashfield [not found] ` <10D57FBA9FD7C14FB49EE17590E1AF9453C90E9E@svr-exc-03.intern.wipotec.de> 0 siblings, 1 reply; 6+ messages in thread From: Bruce Ashfield @ 2015-07-17 15:39 UTC (permalink / raw) To: Gorny Krystian, yocto@yoctoproject.org 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. >> >> > > ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <10D57FBA9FD7C14FB49EE17590E1AF9453C90E9E@svr-exc-03.intern.wipotec.de>]
* Re: Kernel header missing for specific Target [not found] ` <10D57FBA9FD7C14FB49EE17590E1AF9453C90E9E@svr-exc-03.intern.wipotec.de> @ 2015-07-23 13:33 ` Bruce Ashfield 0 siblings, 0 replies; 6+ messages in thread From: Bruce Ashfield @ 2015-07-23 13:33 UTC (permalink / raw) To: Gorny Krystian, yocto@yoctoproject.org On 15-07-23 09:31 AM, Gorny Krystian wrote: > So my drv_iointerrupt.c is a standard *.ko driver. It's still missing the include files asm/atomic.h and linux/cdev.h when I try to build it ($bitbake iointerrupt). > > Can I compile and install the driver module to the kernel with normal *.bb files (like a normal recipe)? I'm still not sure about this. > If the driver follows kernel conventions, then yes, you can write a recipe that builds and packages the modules. If you look in meta-skeleton, there is a hello-mod example of a kmod recipe. 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 > > > _____________________________________________________________________ > > 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 5:40 PM > To: Gorny Krystian; yocto@yoctoproject.org > Subject: Re: [yocto] Kernel header missing for specific Target > > 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. >>> >>> >> >> > > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Kernel header files missing 2015-07-17 12:47 Kernel header missing for specific Target Gorny Krystian 2015-07-17 13:32 ` Bruce Ashfield @ 2015-07-17 15:18 ` Louis Ryan 1 sibling, 0 replies; 6+ messages in thread From: Louis Ryan @ 2015-07-17 15:18 UTC (permalink / raw) To: yocto@yoctoproject.org [-- Attachment #1: Type: text/plain, Size: 1019 bytes --] Hi, I am trying to do loadable kernel module development using the yocto produced sdk. I can create the sdk and it works fine for application development. There appears to be some header files missing for kernel module development. These are the steps I went through ( I am using Beaglebone Black ) mkdir bb-yocto cd bb-yocto git clone -b daisy git://git.yoctoproject.org/poky.git cd poky source oe-init-build-env build vi conf/local.conf MACHINE ?= "beaglebone" bitbake core-image-minimal bitbake core-image-minimal -c populate_sdk cd tmp/deploy/sdk ./poky-eglibc-x86_64-core-image-minimal-cortexa8hf-vfp-neon-toolchain-1.6.3.sh some header files I want to use fro kernel module development like kernel.h, kdev_t.h appear in /opt/poky/bb-linux/sysroots/cortexa8hf-vfp-neon-poky-linux-gnueabi/usr/include/linux but some are missing like, module.h, device.h, cdev.h,uaccess.h. Is there something else I need to do to get the missing files? Thanks Louis [-- Attachment #2: Type: text/html, Size: 1312 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-07-23 13:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
[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
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.