Re: [yocto] problems with yocto eclipse ADT and beaglebone
Hi Larry, Is it latest eclipse plug-in you’re using is the 1.5 release? I’d expect our QA should test the scenario of build derived toolchain usage case and reported issue. Anyhow, I’m traveling atm and will try to reproduce the issue when I’m back in office next week. 2nd issue for requirement of tcf-agent, I don’t think we require that to be mandatory, we’ve been supporting both ssh and tcf connection for remote debugging for quite some time. My question is what eclipse version are you using? It’s not Yocto eclipse plug-in but the eclipse IDE itself, Juno or Kepler? If you install Yocto kepler plugin into Juno IDE, then that’ll definitely have some unpredictable behavior. Also, what is your remote target that you tried to debug against, real HW or qemu instance? And what image are you booted remote target with? E.g. core-image-minimal or core-image-sato-sdk, etc. You said you had previous success with eclipse plugin prior to upgrade to latest kepler release, what is the prior setup that has been working for you? The ML is the right venue to report issues and seek quick responses, but given the fact that the issues you’re reporting need some further investigation, could you please file bugs in our bugzilla to better track these issues? Thanks, Jessica From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Larry Weaver Sent: Thursday, October 24, 2013 2:50 PM To: 'Yocto discussion list' Subject: [yocto] problems with yocto eclipse ADT and beaglebone I apologize in advance for my inexperience in this type of endeavor. I've been a windows and microchip guy for some time, but the low cost machines like the beaglebone have all my clients moving over to linux so I need to become immersed in linux as well. I've spent the last month studying and working with linux and have reached something of an impasse (no forward progress for over 3 days now). I'm not sure if this is the right platform to ask for eclipse ADT help or if there is a better mailing list, but hopefully you will let me know that. I also need to know if this is considered for text only or can I include captured screen images (cut to only the info needed). I have reinstalled a virtual Ubuntu machine, downloaded the yocto angstrom scripts, compiled the kernel (and uboot) too many times to count (and deployed to sd cards with success). While doing this I tried various eclipse setups to do cross compiling and debugging with a lot of success. A few days ago I saw that there was a new version of eclipse (kepler) with new ADT tools that should make the cross compiling and debugging much more elegant. I installed a new Ubuntu virtual machine, got the angstrom scripts set up and the kernel compiled and then tried to get the eclipse setup going. I've run into two problems that have me completely stopped. The first is a configuration problem that I hope will be easy to get past. When I try to set up the Build system derived toolchain debug configuration (following the instructions in the Yocto Project Development Manual) I have been completely stumped. I have run the meta-ide-support with no problem, and the build directory and tmp directory are there. No matter what directory off of setup-scripts I use for a Toolchain Root Location it is rejected saying that the toolchain directory does not contain a toolchain generated with bitbake meta-ide-support. I've rerun meta-ide-support many times, but no subdirectory seems to contain the correct information when it is finished. Where (and how) can I find the correct subdirectory that contains the correct meta-ide-suport data? Since that is a complete dead end for me at the moment, I bitbaked the meta-toolchain and ran the resultant shell to extract the toolchain into the /usr/local subdirectory. I then changed the debug configuration to Standalone pre-built toolchain and selected the oecore-i686 directory created off /usr/local as the toolchain root and it's subdirectory sysroots as the sysroots directory. Eclipse is quite happy with this so I thought I was finally to the next stage. I started a Yocto ADT C++ project (again following the Yocto Project Development Manual), but ran into some warnings when I compile the hello world project. These seem to be warnings so I kind of ignored them (still currently doing that) since I had other things I considered more important. T Description Resource Path Location Type Missing PROG dlltool HelloWorld -1 Configure Problem Missing PROG arm-angstrom-linux-gnueabi-dlltool HelloWorld -1Configure Problem Missing PROG arm-angstrom-linux-gnueabi-mt HelloWorld -1Configure Problem I then found that the new eclipse Yocto ADE setup requires the target to be
[yocto] Problem with staging dir in Makefile.am
Hi. I have a package that tries to point to a staged/installed source file (shared) in the list of files to be compiled. But how should the Makefile.am properly pick-up the current staging dir for my target? Currently it is simply using /usr/share/foo/foo.c, but obviously that will not work when cross-compiling or using native staging dirs. Any suggestion to in what way a Makefile.am should be written to handle such a case? I tried using $(DESTDIR) but that does not seem to be populated in this context. Thanks. Hans ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
Bruce,
Regarding the defconfig not used, I've found this thread on Angstrom devel
ML:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html
I've replaced FILESEXTRAPATHS_prepend with FILESPATH_prepend and
removed the custom do_configure_prepend function and bitbake is now using
my defconfig.
So, it seems that there is an issue with FILESEXTRAPATHS variable.
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
2013/10/23 Bruce Ashfield bruce.ashfi...@windriver.com
On 13-10-22 12:23 PM, Mike Lewis wrote:
Hi Bruce,
I'm trying to accomplish the nearly the same thing (i.e. adding config
fragment) and I'm having the same issue at the do_patch step. Were you
able to reproduce this on your end?
Mike,
Is you config/layer somewhere than I can have a look at it ? I was trying
some builds here, and my tests are working. But I'd like to try it
with your config as well.
Bruce
Thanks,
Mike
On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
On 13-10-18 05:17 AM, Diego Sueiro wrote:
2013/10/18 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfield@**windriver.com bruce.ashfi...@windriver.com
I fell behind today .. i had 2300 unread email to start this
morning :)
Is there a way that I can get a copy of your recipes and layers ? If
I can do a build myself, I can easily debug and fix this ..
otherwise, we'll
go back and forth many times debugging.
Cheers,
Bruce
I'm using the environment provided by Angstrom from it's github setup
scripts.
If you want to exactly reproduce it you need to:
git clone https://github.com/Angstrom-**
distribution/setup-scripts.githttps://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
git checkout angstrom-v2013.06-yocto1.4
MACHINE=beaglebone ./oebb.sh config beaglebone
Here is the setup and files for meta-mine:
bblayers.conf:
BBLAYERS = \
...
${TOPDIR}/sources/meta-mine \
meta-mine/conf/layer.conf:
# We have a conf and classes directory, append to BBPATH
BBPATH .= :${LAYERDIR}
# We have a recipes directory, add to BBFILES
BBFILES += ${LAYERDIR}/recipes*/*/*.bb
${LAYERDIR}/recipes*/*/*.**bbappend
BBFILE_COLLECTIONS += mine-layer
BBFILE_PATTERN_mine-layer := ^${LAYERDIR}/
BBFILE_PRIORITY_mine-layer = 10
LAYERDEPENDS_mine-layer = angstrom-layer
meta-mine/recipes-kernel/**linux/linux-mainline_3.8.**bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}-3.8:
inherit kernel
require recipes-kernel/linux/linux-**yocto.inc
COMPATIBLE_MACHINE_beaglebone = (beaglebone)
SRC_URI += file://config-addons.cfg
meta-mine/recipes-kernel/**linux/linux-mainline-3.8/**
config-addons.cfg:
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
But I think that instead of using the whole Angstrom you can just use
poky and meta-beagleboard/common-bsp on dylan branch.
Great. I'll launch some test builds and see what breaks (or works) :)
Bruce
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto
__**_
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.**org/listinfo/yoctohttps://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Remote debugging with Yocto
Hi Yocto,
Thanks for all the support. I'm just working 2 weeks on Yocto and still no
expert. Adding extra features is working great when I want to do remote-debug:
EXTRA_IMAGE_FEATURES = debug-tweaks tools-debug eclipse-debug
Next problem I have is related to the 5150 evaluation board from TI. I have
soldered the BT.656 cable.
There are several ways to add this to my project:
1. Add in the program and call the I2C driver... but that's really ugly.
2. Add a kernel module for this chip. Following things I can do:
A) Create a new Board Support Layer:
yocto-bsp list karch
yocto-bsp create sogeti arm
After doing this, I am completely lost. It is using kernel 3.8, but the
ATMEL Sama5d3s is using 3.6.9, so this will not work...
B) Create a kernel driver in Eclipse.
But I can create a project, but not a kernel project... strange?
C) Use the C file, create a Makefile and cross compile.
I can compile a kernel-module and use insmod, but never done this with
Yocto... how to do this in the Yocto environment.
After doing this, I still have no idea if I should add this file to a
BB file or BBapend?
D) Some websites tell this driver is inside omap3-isp. Where to add this in
Yocto?
What do you think is the fastest/decent solution?
greetings from Holland,
Bart
From: Voicu, Cristiana [cristiana.vo...@intel.com]
Sent: Tuesday, October 22, 2013 4:12 PM
To: Houkes, Bart
Cc: yocto@yoctoproject.org; Rifenbark, Scott M
Subject: RE: [yocto] Remote debugging with Yocto
Hi Bart,
It seems that tcf-agent was moved to eclipse-debug package group. So, instead
of adding tools-debug to image features, you should add eclipse-debug.
I think that the documentation for tcf-agent is not updated. Scott, can you
please update this?
Thank you,
Cristiana
-Original Message-
From: Houkes, Bart [mailto:bart.hou...@sogeti.nl]
Sent: Tuesday, October 22, 2013 4:11 PM
To: Voicu, Cristiana
Subject: RE: [yocto] Remote debugging with Yocto
Hi Cristiana,
I did step 2 from
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#getting-the-images,
and changed the makefile a lot. I copied the file stubs-hard.h to
stubs-soft.h, but in the end I miss a dependency lssl, which I can't find yet.
When I try to do the same with hob and add tcf-agent, it becomes red and hob
stops without any result. Maybe I should hire the young girl from Yocto's
movie, for her it is simple.
I added tools-debug to my local-conf and start bitbake again. For HOB, I get
the RPM file which is useless... I need the sama5d34.dtb, uImage (kernel
binary) and a core-image[a-z]*.tar.gz
My local.conf has following:
BB_NUMBER_THREADS = 4
PARALLEL_MAKE = -j 4
MACHINE ??= sama5d3xek
DL_DIR ?= /home/mensfort/workspace_poky/downloads
DISTRO ?= poky
EXTRA_IMAGE_FEATURES = debug-tweaks tools-debug=== Just added
tools-debug.
USER_CLASSES ?= buildstats image-mklibs image-prelink
PATCHRESOLVE = noop
BB_DISKMON_DIRS = \
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K
CONF_VERSION = 1
SSTATE_MIRRORS =
PACKAGE_CLASSES = package_rpm package_ipk
I get following output from bitbake, no working output anymore.
| Error: packagegroup-core-boot not found in the base feeds (sama5d3xek
cortexa9t2hf-vfp cortexa9hf-vfp armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp
armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp noarch any all).
| ERROR: Function failed: do_rootfs (see
| /home/mensfort/workspace_poky/poky/build-atmel/tmp/work/sama5d3xek-pok
| y-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.28222 for
| further information)
ERROR: Task 7
(/home/mensfort/workspace_poky/poky/meta/recipes-core/images/core-image-minimal.bb,
do_rootfs) failed with exit code '1'
Currently 1 running tasks (1864 of 1870):
0: perl-5.14.3-r1 do_package_write_ipk (pid 28220)
Next time to try HOB, I will make a screenshot.
Maybe I am using the 'old' version 1.4.1. How to change to 1.4.2 or 1.5 ?
greetings,
Bart
Hi Bart,
On 10/21/2013 07:31 PM, Houkes, Bart wrote:
Hi,
2 issues are blocking for my development:
last few weeks I was able to download my own kernel on the ARM board with
SAMA5d3S.
However, with HOB I cannot add TCF-agent or any other project.. HOB will give
some error, becomes red and stops. I cannot compile anymore.
I need TCF-agent to do remote debugging.
Regarding tcf-agent, you can find documentation at
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#getting-the-images.
If you already have tools-debug as extra feature in local.conf, and you receive
an error in Hob, can you please provide a screenshot with it?
Cristiana
Another:
There are some presentations about standard projects. How about kernel
drivers with cross compilers or Video 4 Linux.
[yocto] yocto-dora problems building python
Hello, I got this QA error when build python: ERROR: QA Issue: python: The compile log indicates that host include and/or library paths were used. Any hint? Build Configuration: BB_VERSION= 1.20.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-13.04 TARGET_SYS= i586-poky-linux MACHINE = qemux86 DISTRO= poky DISTRO_VERSION= 1.5 TUNE_FEATURES = m32 i586 TARGET_FPU= meta = dora:faf8f8660fae26a14578738b642fdeb08bcb9d54 meta-oe meta-systemd = dora:513e7ca20ddd0a5c3b649bf292a67c3e0473d3a8 meta-yocto= dora:faf8f8660fae26a14578738b642fdeb08bcb9d54 meta-padtec meta-otns = master:b2db43d21f303e4e02956cc9f2e9ad2bf547dd95 meta-intel meta-crownbay = custom:fa3b568222f87fc557f01bb5acb5d362e6bde301 NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: QA Issue: python: The compile log indicates that host include and/or library paths were used. Please check the log '/srv/build/yocto/build/work/i586-poky-linux/python/2.7.3-r0.3/temp/log.do_compile' for more information. ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: /srv/build/yocto/build/work/i586-poky-linux/python/2.7.3-r0.3/temp/log.do_package.29112 ERROR: Task 12 (/home/jfreitas/yocto/poky/meta/recipes-devtools/python/ python_2.7.3.bb, do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 872 tasks of which 540 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory No currently running tasks (872 of 876) Summary: 1 task failed: /home/jfreitas/yocto/poky/meta/recipes-devtools/python/python_2.7.3.bb, do_package Summary: There were 3 ERROR messages shown, returning a non-zero exit code. Thanks. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working
Folks, I'm using dylan branch and package management is ipk. I'm trying to remove qt-demo-init package from my custom image with both BAD_RECOMMENDATIONS and BAD_RECOMMENDS variables but it is still being installed on rootfs. I've already did a cleansstate on my image recipe but no success. I can use the ROOTFS_POSTPROCESS_COMMAND to remove the initscript from /etc/init.d but it seems to be an workaround to get this working. Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working
BAD_RECOMMENDATIONS work only for packages which are installed because something has them in RRECOMMENDS, if your custom image has qt-demo-init in IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be removed (and shouldn't be). Use bitbake -g to see why and how it's pulled to your image. On Fri, Oct 25, 2013 at 3:16 PM, Diego Sueiro diego.sue...@gmail.comwrote: Folks, I'm using dylan branch and package management is ipk. I'm trying to remove qt-demo-init package from my custom image with both BAD_RECOMMENDATIONS and BAD_RECOMMENDS variables but it is still being installed on rootfs. I've already did a cleansstate on my image recipe but no success. I can use the ROOTFS_POSTPROCESS_COMMAND to remove the initscript from /etc/init.d but it seems to be an workaround to get this working. Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems with yocto eclipse ADT and beaglebone
The system is the kepler release with the Yocto kepler 1.5 plugin (the Yocto manual says to use 1.6, but that doesn’t seem to exist). I’m setting things up totally from the manual and it says to use the tcf-agent with the Yocto plugin for eclipse kepler (also has some juno information, but says kepler is preferred). Hopefully you saw my second email where I sorted out the tcf-agent by setting up the beagleboard to compile and then compiled it on the board. It is now working except for one problem. When I tell the system to start it on system start up, it only works for about 5 minutes. Eclipse suddenly loses contact with it. If I putty over and start it up again it works until I terminate the putty session. I’m running the youto angstrom distribution on the beaglebone. Now the problem I have left is the build derived toolchain not finding any subdirectory with the meta-ide-support information in it. I will figure out how to do the bugzilla later today. Thanks, Larry From: Zhang, Jessica [mailto:jessica.zh...@intel.com] Sent: Thursday, October 24, 2013 11:43 PM To: Larry Weaver; 'Yocto discussion list' Subject: RE: [yocto] problems with yocto eclipse ADT and beaglebone Hi Larry, Is it latest eclipse plug-in you’re using is the 1.5 release? I’d expect our QA should test the scenario of build derived toolchain usage case and reported issue. Anyhow, I’m traveling atm and will try to reproduce the issue when I’m back in office next week. 2nd issue for requirement of tcf-agent, I don’t think we require that to be mandatory, we’ve been supporting both ssh and tcf connection for remote debugging for quite some time. My question is what eclipse version are you using? It’s not Yocto eclipse plug-in but the eclipse IDE itself, Juno or Kepler? If you install Yocto kepler plugin into Juno IDE, then that’ll definitely have some unpredictable behavior. Also, what is your remote target that you tried to debug against, real HW or qemu instance? And what image are you booted remote target with? E.g. core-image-minimal or core-image-sato-sdk, etc. You said you had previous success with eclipse plugin prior to upgrade to latest kepler release, what is the prior setup that has been working for you? The ML is the right venue to report issues and seek quick responses, but given the fact that the issues you’re reporting need some further investigation, could you please file bugs in our bugzilla to better track these issues? Thanks, Jessica From: yocto-boun...@yoctoproject.org mailto:yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Larry Weaver Sent: Thursday, October 24, 2013 2:50 PM To: 'Yocto discussion list' Subject: [yocto] problems with yocto eclipse ADT and beaglebone I apologize in advance for my inexperience in this type of endeavor. I've been a windows and microchip guy for some time, but the low cost machines like the beaglebone have all my clients moving over to linux so I need to become immersed in linux as well. I've spent the last month studying and working with linux and have reached something of an impasse (no forward progress for over 3 days now). I'm not sure if this is the right platform to ask for eclipse ADT help or if there is a better mailing list, but hopefully you will let me know that. I also need to know if this is considered for text only or can I include captured screen images (cut to only the info needed). I have reinstalled a virtual Ubuntu machine, downloaded the yocto angstrom scripts, compiled the kernel (and uboot) too many times to count (and deployed to sd cards with success). While doing this I tried various eclipse setups to do cross compiling and debugging with a lot of success. A few days ago I saw that there was a new version of eclipse (kepler) with new ADT tools that should make the cross compiling and debugging much more elegant. I installed a new Ubuntu virtual machine, got the angstrom scripts set up and the kernel compiled and then tried to get the eclipse setup going. I've run into two problems that have me completely stopped. The first is a configuration problem that I hope will be easy to get past. When I try to set up the Build system derived toolchain debug configuration (following the instructions in the Yocto Project Development Manual) I have been completely stumped. I have run the meta-ide-support with no problem, and the build directory and tmp directory are there. No matter what directory off of setup-scripts I use for a Toolchain Root Location it is rejected saying that the toolchain directory does not contain a toolchain generated with bitbake meta-ide-support. I've rerun meta-ide-support many times, but no subdirectory seems to contain the correct information when it is finished. Where (and how) can I find the correct subdirectory that contains the correct meta-ide-suport data? Since that
Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working
2013/10/25 Martin Jansa martin.ja...@gmail.com BAD_RECOMMENDATIONS work only for packages which are installed because something has them in RRECOMMENDS, if your custom image has qt-demo-init in IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be removed (and shouldn't be). Thanks Martin, qt-demo-init is listed as RDEPENDS on packagegroup-core-qt4e. As soon as my image recipe have a IMAGE_INSTALL = packagegroup-core-qt4e, I'll have to remove the init script with ROOTFS_POSTPROCESS_COMMAND. That is it? The renaming question is: packagegroup-core-qt4e should include qt-demo-init with RRECOMENDS instead of RDEPENDS? Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] problems with yocto eclipse ADT and beaglebone
I have managed to answer one of my questions. The tcf-agent from the beagleboard build is apparently not complete. I set up a toolchain on the beaglebone and compiled the tcf-agent from the git. The previous tcf-agent didn’t have terminal or shell capability. The new one does. . So now if I can get the Build system derived toolchain directory figured out I will have a full beaglebone development system. Any ideas? Thanks, Larry From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Larry Weaver Sent: Thursday, October 24, 2013 2:50 PM To: 'Yocto discussion list' Subject: [yocto] problems with yocto eclipse ADT and beaglebone I apologize in advance for my inexperience in this type of endeavor. I've been a windows and microchip guy for some time, but the low cost machines like the beaglebone have all my clients moving over to linux so I need to become immersed in linux as well. I've spent the last month studying and working with linux and have reached something of an impasse (no forward progress for over 3 days now). I'm not sure if this is the right platform to ask for eclipse ADT help or if there is a better mailing list, but hopefully you will let me know that. I also need to know if this is considered for text only or can I include captured screen images (cut to only the info needed). I have reinstalled a virtual Ubuntu machine, downloaded the yocto angstrom scripts, compiled the kernel (and uboot) too many times to count (and deployed to sd cards with success). While doing this I tried various eclipse setups to do cross compiling and debugging with a lot of success. A few days ago I saw that there was a new version of eclipse (kepler) with new ADT tools that should make the cross compiling and debugging much more elegant. I installed a new Ubuntu virtual machine, got the angstrom scripts set up and the kernel compiled and then tried to get the eclipse setup going. I've run into two problems that have me completely stopped. The first is a configuration problem that I hope will be easy to get past. When I try to set up the Build system derived toolchain debug configuration (following the instructions in the Yocto Project Development Manual) I have been completely stumped. I have run the meta-ide-support with no problem, and the build directory and tmp directory are there. No matter what directory off of setup-scripts I use for a Toolchain Root Location it is rejected saying that the toolchain directory does not contain a toolchain generated with bitbake meta-ide-support. I've rerun meta-ide-support many times, but no subdirectory seems to contain the correct information when it is finished. Where (and how) can I find the correct subdirectory that contains the correct meta-ide-suport data? Since that is a complete dead end for me at the moment, I bitbaked the meta-toolchain and ran the resultant shell to extract the toolchain into the /usr/local subdirectory. I then changed the debug configuration to Standalone pre-built toolchain and selected the oecore-i686 directory created off /usr/local as the toolchain root and it's subdirectory sysroots as the sysroots directory. Eclipse is quite happy with this so I thought I was finally to the next stage. I started a Yocto ADT C++ project (again following the Yocto Project Development Manual), but ran into some warnings when I compile the hello world project. These seem to be warnings so I kind of ignored them (still currently doing that) since I had other things I considered more important. T Description Resource Path Location Type Missing PROG dlltool HelloWorld -1 Configure Problem Missing PROG arm-angstrom-linux-gnueabi-dlltool HelloWorld -1Configure Problem Missing PROG arm-angstrom-linux-gnueabi-mt HelloWorld -1Configure Problem I then found that the new eclipse Yocto ADE setup requires the target to be running a tcf-agent. According to the instructions I can add a definition to my conf/local.conf file that will cause the tcf-agent to be installed. I added this to the local.conf and recompiled. The scripts sensed something had changed and gave me a new kernel image file. Thinking I had success I put that on an sd card and booted, but still no tcf-agent. I extracted the images and checked the differences between them and it was very minimal. The image that was supposed to have tcf-agent in it had some extra .sh files installed. While not an expert on sh files these seem to have nothing to do with tcf-agent. According to the Yocto Project Application Developers Guide the prebuilt images of e-image-sato-sdk have the tcf-agent in them so I downloaded the file for the beagleboard (if I compile using machine =beagleboard instead of
Re: [yocto] Custom defconfig is not used
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro diego.sue...@gmail.com wrote:
Bruce,
Regarding the defconfig not used, I've found this thread on Angstrom devel
ML:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html
I've replaced FILESEXTRAPATHS_prepend with FILESPATH_prepend and removed
the custom do_configure_prepend function and bitbake is now using my
defconfig.
So, it seems that there is an issue with FILESEXTRAPATHS variable.
Aha. That does make sense.
Mike: does that same change fix your issues ?
Bruce
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
2013/10/23 Bruce Ashfield bruce.ashfi...@windriver.com
On 13-10-22 12:23 PM, Mike Lewis wrote:
Hi Bruce,
I'm trying to accomplish the nearly the same thing (i.e. adding config
fragment) and I'm having the same issue at the do_patch step. Were you
able to reproduce this on your end?
Mike,
Is you config/layer somewhere than I can have a look at it ? I was trying
some builds here, and my tests are working. But I'd like to try it
with your config as well.
Bruce
Thanks,
Mike
On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
On 13-10-18 05:17 AM, Diego Sueiro wrote:
2013/10/18 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com
I fell behind today .. i had 2300 unread email to start this
morning :)
Is there a way that I can get a copy of your recipes and layers ?
If
I can do a build myself, I can easily debug and fix this ..
otherwise, we'll
go back and forth many times debugging.
Cheers,
Bruce
I'm using the environment provided by Angstrom from it's github setup
scripts.
If you want to exactly reproduce it you need to:
git clone
https://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
git checkout angstrom-v2013.06-yocto1.4
MACHINE=beaglebone ./oebb.sh config beaglebone
Here is the setup and files for meta-mine:
bblayers.conf:
BBLAYERS = \
...
${TOPDIR}/sources/meta-mine \
meta-mine/conf/layer.conf:
# We have a conf and classes directory, append to BBPATH
BBPATH .= :${LAYERDIR}
# We have a recipes directory, add to BBFILES
BBFILES += ${LAYERDIR}/recipes*/*/*.bb
${LAYERDIR}/recipes*/*/*.bbappend
BBFILE_COLLECTIONS += mine-layer
BBFILE_PATTERN_mine-layer := ^${LAYERDIR}/
BBFILE_PRIORITY_mine-layer = 10
LAYERDEPENDS_mine-layer = angstrom-layer
meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}-3.8:
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
COMPATIBLE_MACHINE_beaglebone = (beaglebone)
SRC_URI += file://config-addons.cfg
meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
But I think that instead of using the whole Angstrom you can just use
poky and meta-beagleboard/common-bsp on dylan branch.
Great. I'll launch some test builds and see what breaks (or works) :)
Bruce
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long
On MIPS64, __u64 is unsigned long type, so the %llu specifier will cause
build error on MIPS64.
Convert __u64 to unsigned long long in those sprintf calls to avoid the build
error.
Signed-off-by: Yang Shi yang@windriver.com
---
tools/perf/tests/attr.c | 20 ++--
tools/perf/tests/bp_signal.c |2 +-
tools/perf/tests/bp_signal_overflow.c |2 +-
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 00218f5..f045c2c 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -71,7 +71,7 @@ static int store_event(struct perf_event_attr *attr, pid_t
pid, int cpu,
char path[PATH_MAX];
snprintf(path, PATH_MAX, %s/event-%d-%llu-%d, dir,
-attr-type, attr-config, fd);
+attr-type, (unsigned long long)attr-config, fd);
file = fopen(path, w+);
if (!file) {
@@ -80,7 +80,7 @@ static int store_event(struct perf_event_attr *attr, pid_t
pid, int cpu,
}
if (fprintf(file, [event-%d-%llu-%d]\n,
- attr-type, attr-config, fd) 0) {
+ attr-type, (unsigned long long)attr-config, fd) 0) {
perror(test attr - failed to write event file);
fclose(file);
return -1;
@@ -96,10 +96,10 @@ static int store_event(struct perf_event_attr *attr, pid_t
pid, int cpu,
/* struct perf_event_attr */
WRITE_ASS(type, PRIu32);
WRITE_ASS(size, PRIu32);
- WRITE_ASS(config, llu);
- WRITE_ASS(sample_period, llu);
- WRITE_ASS(sample_type, llu);
- WRITE_ASS(read_format, llu);
+ __WRITE_ASS(config,llu, (unsigned long long)attr-config);
+ __WRITE_ASS(sample_period, llu, (unsigned long
long)attr-sample_period);
+ __WRITE_ASS(sample_type, llu, (unsigned long
long)attr-sample_type);
+ __WRITE_ASS(read_format, llu, (unsigned long
long)attr-read_format);
WRITE_ASS(disabled, d);
WRITE_ASS(inherit,d);
WRITE_ASS(pinned, d);
@@ -124,10 +124,10 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
WRITE_ASS(exclude_callchain_user, d);
WRITE_ASS(wakeup_events, PRIu32);
WRITE_ASS(bp_type, PRIu32);
- WRITE_ASS(config1, llu);
- WRITE_ASS(config2, llu);
- WRITE_ASS(branch_sample_type, llu);
- WRITE_ASS(sample_regs_user, llu);
+ __WRITE_ASS(config1,llu, (unsigned long
long)attr-config1);
+ __WRITE_ASS(config2,llu, (unsigned long
long)attr-config2);
+ __WRITE_ASS(branch_sample_type, llu, (unsigned long
long)attr-branch_sample_type);
+ __WRITE_ASS(sample_regs_user, llu, (unsigned long
long)attr-sample_regs_user);
WRITE_ASS(sample_stack_user, PRIu32);
fclose(file);
diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
index 68daa28..bf3a094 100644
--- a/tools/perf/tests/bp_signal.c
+++ b/tools/perf/tests/bp_signal.c
@@ -74,7 +74,7 @@ static int bp_event(void *fn, int setup_signal)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
diff --git a/tools/perf/tests/bp_signal_overflow.c
b/tools/perf/tests/bp_signal_overflow.c
index fe7ed28..3662b15 100644
--- a/tools/perf/tests/bp_signal_overflow.c
+++ b/tools/perf/tests/bp_signal_overflow.c
@@ -87,7 +87,7 @@ int test__bp_signal_overflow(void)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long
Wouldn't it be better to change %llu to PRIu64 (from inttypes.h)?
Notice that PRIu32 is already used in places.
You can use string catenation where necessary, e.g.
%s/event-%d- PRIu64 -%d
On 10/25/13 12:17 PM, Yang Shi yang@windriver.com wrote:
On MIPS64, __u64 is unsigned long type, so the %llu specifier will
cause
build error on MIPS64.
Convert __u64 to unsigned long long in those sprintf calls to avoid the
build
error.
Signed-off-by: Yang Shi yang@windriver.com
---
tools/perf/tests/attr.c | 20 ++--
tools/perf/tests/bp_signal.c |2 +-
tools/perf/tests/bp_signal_overflow.c |2 +-
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 00218f5..f045c2c 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -71,7 +71,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
char path[PATH_MAX];
snprintf(path, PATH_MAX, %s/event-%d-%llu-%d, dir,
- attr-type, attr-config, fd);
+ attr-type, (unsigned long long)attr-config, fd);
file = fopen(path, w+);
if (!file) {
@@ -80,7 +80,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
}
if (fprintf(file, [event-%d-%llu-%d]\n,
- attr-type, attr-config, fd) 0) {
+ attr-type, (unsigned long long)attr-config, fd) 0) {
perror(test attr - failed to write event file);
fclose(file);
return -1;
@@ -96,10 +96,10 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
/* struct perf_event_attr */
WRITE_ASS(type, PRIu32);
WRITE_ASS(size, PRIu32);
- WRITE_ASS(config, llu);
- WRITE_ASS(sample_period, llu);
- WRITE_ASS(sample_type, llu);
- WRITE_ASS(read_format, llu);
+ __WRITE_ASS(config,llu, (unsigned long long)attr-config);
+ __WRITE_ASS(sample_period, llu, (unsigned long
long)attr-sample_period);
+ __WRITE_ASS(sample_type, llu, (unsigned long
long)attr-sample_type);
+ __WRITE_ASS(read_format, llu, (unsigned long
long)attr-read_format);
WRITE_ASS(disabled, d);
WRITE_ASS(inherit,d);
WRITE_ASS(pinned, d);
@@ -124,10 +124,10 @@ static int store_event(struct perf_event_attr
*attr, pid_t pid, int cpu,
WRITE_ASS(exclude_callchain_user, d);
WRITE_ASS(wakeup_events, PRIu32);
WRITE_ASS(bp_type, PRIu32);
- WRITE_ASS(config1, llu);
- WRITE_ASS(config2, llu);
- WRITE_ASS(branch_sample_type, llu);
- WRITE_ASS(sample_regs_user, llu);
+ __WRITE_ASS(config1,llu, (unsigned long
long)attr-config1);
+ __WRITE_ASS(config2,llu, (unsigned long
long)attr-config2);
+ __WRITE_ASS(branch_sample_type, llu, (unsigned long
long)attr-branch_sample_type);
+ __WRITE_ASS(sample_regs_user, llu, (unsigned long
long)attr-sample_regs_user);
WRITE_ASS(sample_stack_user, PRIu32);
fclose(file);
diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
index 68daa28..bf3a094 100644
--- a/tools/perf/tests/bp_signal.c
+++ b/tools/perf/tests/bp_signal.c
@@ -74,7 +74,7 @@ static int bp_event(void *fn, int setup_signal)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
diff --git a/tools/perf/tests/bp_signal_overflow.c
b/tools/perf/tests/bp_signal_overflow.c
index fe7ed28..3662b15 100644
--- a/tools/perf/tests/bp_signal_overflow.c
+++ b/tools/perf/tests/bp_signal_overflow.c
@@ -87,7 +87,7 @@ int test__bp_signal_overflow(void)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long
I guess for that example, you have to add % yourself
%s/event-%d-% PRIu64 -%d
but for all the WRITE_ASS examples, simply replace llu with PRIu64
On 10/25/13 1:11 PM, Billie Alsup billie.al...@ericsson.com wrote:
Wouldn't it be better to change %llu to PRIu64 (from inttypes.h)?
Notice that PRIu32 is already used in places.
You can use string catenation where necessary, e.g.
%s/event-%d- PRIu64 -%d
On 10/25/13 12:17 PM, Yang Shi yang@windriver.com wrote:
On MIPS64, __u64 is unsigned long type, so the %llu specifier will
cause
build error on MIPS64.
Convert __u64 to unsigned long long in those sprintf calls to avoid the
build
error.
Signed-off-by: Yang Shi yang@windriver.com
---
tools/perf/tests/attr.c | 20 ++--
tools/perf/tests/bp_signal.c |2 +-
tools/perf/tests/bp_signal_overflow.c |2 +-
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 00218f5..f045c2c 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -71,7 +71,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
char path[PATH_MAX];
snprintf(path, PATH_MAX, %s/event-%d-%llu-%d, dir,
- attr-type, attr-config, fd);
+ attr-type, (unsigned long long)attr-config, fd);
file = fopen(path, w+);
if (!file) {
@@ -80,7 +80,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
}
if (fprintf(file, [event-%d-%llu-%d]\n,
- attr-type, attr-config, fd) 0) {
+ attr-type, (unsigned long long)attr-config, fd) 0) {
perror(test attr - failed to write event file);
fclose(file);
return -1;
@@ -96,10 +96,10 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
/* struct perf_event_attr */
WRITE_ASS(type, PRIu32);
WRITE_ASS(size, PRIu32);
- WRITE_ASS(config, llu);
- WRITE_ASS(sample_period, llu);
- WRITE_ASS(sample_type, llu);
- WRITE_ASS(read_format, llu);
+ __WRITE_ASS(config,llu, (unsigned long long)attr-config);
+ __WRITE_ASS(sample_period, llu, (unsigned long
long)attr-sample_period);
+ __WRITE_ASS(sample_type, llu, (unsigned long
long)attr-sample_type);
+ __WRITE_ASS(read_format, llu, (unsigned long
long)attr-read_format);
WRITE_ASS(disabled, d);
WRITE_ASS(inherit,d);
WRITE_ASS(pinned, d);
@@ -124,10 +124,10 @@ static int store_event(struct perf_event_attr
*attr, pid_t pid, int cpu,
WRITE_ASS(exclude_callchain_user, d);
WRITE_ASS(wakeup_events, PRIu32);
WRITE_ASS(bp_type, PRIu32);
- WRITE_ASS(config1, llu);
- WRITE_ASS(config2, llu);
- WRITE_ASS(branch_sample_type, llu);
- WRITE_ASS(sample_regs_user, llu);
+ __WRITE_ASS(config1,llu, (unsigned long
long)attr-config1);
+ __WRITE_ASS(config2,llu, (unsigned long
long)attr-config2);
+ __WRITE_ASS(branch_sample_type, llu, (unsigned long
long)attr-branch_sample_type);
+ __WRITE_ASS(sample_regs_user, llu, (unsigned long
long)attr-sample_regs_user);
WRITE_ASS(sample_stack_user, PRIu32);
fclose(file);
diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
index 68daa28..bf3a094 100644
--- a/tools/perf/tests/bp_signal.c
+++ b/tools/perf/tests/bp_signal.c
@@ -74,7 +74,7 @@ static int bp_event(void *fn, int setup_signal)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
diff --git a/tools/perf/tests/bp_signal_overflow.c
b/tools/perf/tests/bp_signal_overflow.c
index fe7ed28..3662b15 100644
--- a/tools/perf/tests/bp_signal_overflow.c
+++ b/tools/perf/tests/bp_signal_overflow.c
@@ -87,7 +87,7 @@ int test__bp_signal_overflow(void)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long
On 10/25/2013 1:14 PM, Billie Alsup wrote:
I guess for that example, you have to add % yourself
%s/event-%d-% PRIu64 -%d
but for all the WRITE_ASS examples, simply replace llu with PRIu64
Thanks for the suggestion. I had a try, but it failed to build for x86_64.
| tests/attr.c:74:4: error: format '%lu' expects argument of type 'long
unsigned int', but argument 6 has type '__u64' [-Werror=format=]
| attr-type, attr-config, fd);
Yang
On 10/25/13 1:11 PM, Billie Alsup billie.al...@ericsson.com wrote:
Wouldn't it be better to change %llu to PRIu64 (from inttypes.h)?
Notice that PRIu32 is already used in places.
You can use string catenation where necessary, e.g.
%s/event-%d- PRIu64 -%d
On 10/25/13 12:17 PM, Yang Shi yang@windriver.com wrote:
On MIPS64, __u64 is unsigned long type, so the %llu specifier will
cause
build error on MIPS64.
Convert __u64 to unsigned long long in those sprintf calls to avoid the
build
error.
Signed-off-by: Yang Shi yang@windriver.com
---
tools/perf/tests/attr.c | 20 ++--
tools/perf/tests/bp_signal.c |2 +-
tools/perf/tests/bp_signal_overflow.c |2 +-
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/tools/perf/tests/attr.c b/tools/perf/tests/attr.c
index 00218f5..f045c2c 100644
--- a/tools/perf/tests/attr.c
+++ b/tools/perf/tests/attr.c
@@ -71,7 +71,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
char path[PATH_MAX];
snprintf(path, PATH_MAX, %s/event-%d-%llu-%d, dir,
-attr-type, attr-config, fd);
+attr-type, (unsigned long long)attr-config, fd);
file = fopen(path, w+);
if (!file) {
@@ -80,7 +80,7 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
}
if (fprintf(file, [event-%d-%llu-%d]\n,
- attr-type, attr-config, fd) 0) {
+ attr-type, (unsigned long long)attr-config, fd) 0) {
perror(test attr - failed to write event file);
fclose(file);
return -1;
@@ -96,10 +96,10 @@ static int store_event(struct perf_event_attr *attr,
pid_t pid, int cpu,
/* struct perf_event_attr */
WRITE_ASS(type, PRIu32);
WRITE_ASS(size, PRIu32);
- WRITE_ASS(config, llu);
- WRITE_ASS(sample_period, llu);
- WRITE_ASS(sample_type, llu);
- WRITE_ASS(read_format, llu);
+ __WRITE_ASS(config,llu, (unsigned long long)attr-config);
+ __WRITE_ASS(sample_period, llu, (unsigned long
long)attr-sample_period);
+ __WRITE_ASS(sample_type, llu, (unsigned long
long)attr-sample_type);
+ __WRITE_ASS(read_format, llu, (unsigned long
long)attr-read_format);
WRITE_ASS(disabled, d);
WRITE_ASS(inherit,d);
WRITE_ASS(pinned, d);
@@ -124,10 +124,10 @@ static int store_event(struct perf_event_attr
*attr, pid_t pid, int cpu,
WRITE_ASS(exclude_callchain_user, d);
WRITE_ASS(wakeup_events, PRIu32);
WRITE_ASS(bp_type, PRIu32);
- WRITE_ASS(config1, llu);
- WRITE_ASS(config2, llu);
- WRITE_ASS(branch_sample_type, llu);
- WRITE_ASS(sample_regs_user, llu);
+ __WRITE_ASS(config1,llu, (unsigned long
long)attr-config1);
+ __WRITE_ASS(config2,llu, (unsigned long
long)attr-config2);
+ __WRITE_ASS(branch_sample_type, llu, (unsigned long
long)attr-branch_sample_type);
+ __WRITE_ASS(sample_regs_user, llu, (unsigned long
long)attr-sample_regs_user);
WRITE_ASS(sample_stack_user, PRIu32);
fclose(file);
diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
index 68daa28..bf3a094 100644
--- a/tools/perf/tests/bp_signal.c
+++ b/tools/perf/tests/bp_signal.c
@@ -74,7 +74,7 @@ static int bp_event(void *fn, int setup_signal)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
diff --git a/tools/perf/tests/bp_signal_overflow.c
b/tools/perf/tests/bp_signal_overflow.c
index fe7ed28..3662b15 100644
--- a/tools/perf/tests/bp_signal_overflow.c
+++ b/tools/perf/tests/bp_signal_overflow.c
@@ -87,7 +87,7 @@ int test__bp_signal_overflow(void)
fd = sys_perf_event_open(pe, 0, -1, -1, 0);
if (fd 0) {
- pr_debug(failed opening event %llx\n, pe.config);
+ pr_debug(failed opening event %llx\n, (unsigned long
long)pe.config);
return TEST_FAIL;
}
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
[yocto] 3.10 Kernel module loading
I am having an issue getting a custom touchscreen kernel driver to load. It's a pixcir touchscreen and I've modified the driver found below to work with this particular display: http://lii-enac.fr/cgi-bin/gitweb.cgi?p=linux-input/drivers.git;a=shortlog;h=refs/heads/pixcir The driver works perfectly with 3.2.32 kernel. Upgrading to 3.10.11 the driver will load when the system starts, but is not responding to touches using evtest. If I unload and reload the driver, (rmmod, modprobe) it works perfectly. Also, if I blacklist the driver on start, then load it, it will not work. Again, unload, reload works. I've tried with 3.8 also with similar results. The display registers itself as both a mouse (usually /dev/input/event2) and a touchscreen (/dev/input/event5). event2 responds to evtest, but when used in QT, the motions are way off. This display has no external calibration capabilities and is connected via usb. The machine is an atom board. Image was built with yocto 1.5 as a genericx86 machine type and kernel configed to include custom driver. I wondering if anyone here knows what might have changed in the kernel versions on how the modules are loaded. Relevant kernel messages below. In this case, I booted normally, unloaded the module and reloaded as can be seen by the last messages. I can provide more info if necessary. Thanks! -- Michael Gloff [1.414612] input: PIXCIR HID Touch Panel as /devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.1/input/input2 [1.414802] hid-generic 0003:040B:2230.0002: input: USB HID v1.00 Mouse [PIXCIR HID Touch Panel] on usb-:00:1d.2-1/input1 [1.620535] usb 5-1: new low-speed USB device number 2 using uhci_hcd [1.799174] ata4.01: failed to resume link (SControl 0) [1.810053] ata4.00: SATA link down (SStatus 0 SControl 310) [1.810129] ata4.01: SATA link down (SStatus 0 SControl 0) [1.812866] kjournald starting. Commit interval 5 seconds [1.812917] EXT3-fs (sda1): mounted filesystem with ordered data mode [1.812942] VFS: Mounted root (ext3 filesystem) readonly on device 8:1. [1.813832] devtmpfs: mounted [1.813926] Freeing unused kernel memory: 480k freed [1.814276] Write protecting the kernel text: 5660k [1.814406] Write protecting the kernel read-only data: 2200k [1.826189] input: Logitech USB Keyboard as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.0/input/input3 [1.826431] hid-generic 0003:046D:C31D.0003: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-:00:1d.3-1/input0 [1.876337] input: Logitech USB Keyboard as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.1/input/input4 [1.876543] hid-generic 0003:046D:C31D.0004: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:1d.3-1/input1 [2.057877] udevd[91]: starting version 182 [ 12.304518] pixcir 0003:040B:2230.0001: usb_submit_urb(ctrl) failed: -1 [ 12.304594] pixcir 0003:040B:2230.0001: timeout initializing reports [ 12.304785] input: PIXCIR HID Touch Panel as /devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.0/input/input5 [ 12.305048] pixcir 0003:040B:2230.0001: input: USB HID v1.00 Device [PIXCIR HID Touch Panel] on usb-:00:1d.2-1/input0 [ 12.361395] EXT3-fs (sda1): using internal journal [ 12.653933] e1000e :00:19.0: irq 41 for MSI/MSI-X [ 12.754413] e1000e :00:19.0: irq 41 for MSI/MSI-X [ 12.754585] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 22.096102] uvesafb: Intel Corporation, Intel(r)PineView Graphics Controller, Hardware Version 0.0, OEM: Intel(r)PineView Graphics Chip Accelerated VGA BIOS, VBE v3.0 [ 22.127124] uvesafb: VBIOS/hardware doesn't support DDC transfers [ 22.127182] uvesafb: no monitor limits have been set, default refresh rate will be used [ 22.127365] uvesafb: scrolling: redraw [ 22.284754] Console: switching to colour frame buffer device 100x30 [ 22.289705] uvesafb: framebuffer at 0xd000, mapped to 0xf828, using 3000k, total 8128k [ 22.289850] fb0: VESA VGA frame buffer device [ 28.170923] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 28.173135] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 28.175451] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 72.660551] pixcir 0003:040B:2230.0001: usb_submit_urb(ctrl) failed: -1 [ 72.661522] pixcir 0003:040B:2230.0001: timeout initializing reports [ 72.665381] input: PIXCIR HID Touch Panel as /devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.0/input/input6 [ 72.668159] pixcir 0003:040B:2230.0001: input: USB HID v1.00 Device [PIXCIR HID Touch Panel] on usb-:00:1d.2-1/input0 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Custom defconfig is not used
Bruce: yep, fixed my issue. Sorry for the bother!
Diego: thanks for the solution!
- Mike
On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro diego.sue...@gmail.com wrote:
Bruce,
Regarding the defconfig not used, I've found this thread on Angstrom devel
ML:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html
I've replaced FILESEXTRAPATHS_prepend with FILESPATH_prepend and removed
the custom do_configure_prepend function and bitbake is now using my
defconfig.
So, it seems that there is an issue with FILESEXTRAPATHS variable.
Aha. That does make sense.
Mike: does that same change fix your issues ?
Bruce
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
2013/10/23 Bruce Ashfield bruce.ashfi...@windriver.com
On 13-10-22 12:23 PM, Mike Lewis wrote:
Hi Bruce,
I'm trying to accomplish the nearly the same thing (i.e. adding config
fragment) and I'm having the same issue at the do_patch step. Were you
able to reproduce this on your end?
Mike,
Is you config/layer somewhere than I can have a look at it ? I was trying
some builds here, and my tests are working. But I'd like to try it
with your config as well.
Bruce
Thanks,
Mike
On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
On 13-10-18 05:17 AM, Diego Sueiro wrote:
2013/10/18 Bruce Ashfield bruce.ashfi...@windriver.com
mailto:bruce.ashfi...@windriver.com
I fell behind today .. i had 2300 unread email to start this
morning :)
Is there a way that I can get a copy of your recipes and layers ?
If
I can do a build myself, I can easily debug and fix this ..
otherwise, we'll
go back and forth many times debugging.
Cheers,
Bruce
I'm using the environment provided by Angstrom from it's github setup
scripts.
If you want to exactly reproduce it you need to:
git clone
https://github.com/Angstrom-distribution/setup-scripts.git
cd setup-scripts
git checkout angstrom-v2013.06-yocto1.4
MACHINE=beaglebone ./oebb.sh config beaglebone
Here is the setup and files for meta-mine:
bblayers.conf:
BBLAYERS = \
...
${TOPDIR}/sources/meta-mine \
meta-mine/conf/layer.conf:
# We have a conf and classes directory, append to BBPATH
BBPATH .= :${LAYERDIR}
# We have a recipes directory, add to BBFILES
BBFILES += ${LAYERDIR}/recipes*/*/*.bb
${LAYERDIR}/recipes*/*/*.bbappend
BBFILE_COLLECTIONS += mine-layer
BBFILE_PATTERN_mine-layer := ^${LAYERDIR}/
BBFILE_PRIORITY_mine-layer = 10
LAYERDEPENDS_mine-layer = angstrom-layer
meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}-3.8:
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
COMPATIBLE_MACHINE_beaglebone = (beaglebone)
SRC_URI += file://config-addons.cfg
meta-mine/recipes-kernel/linux/linux-mainline-3.8/config-addons.cfg:
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
But I think that instead of using the whole Angstrom you can just use
poky and meta-beagleboard/common-bsp on dylan branch.
Great. I'll launch some test builds and see what breaks (or works) :)
Bruce
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] telnetd is not running with core-image-basic
Hi, I tried to run the telnetd with core-image-basic. I follow up the following step to enable the telnetd support in my layer. I have build the latest inetutils recipe with my layer, the latest version of inteutils is intetutils_1.9.1. I have build the packages successful. But the telnetd is not available in my core-image-basic. When i run the the image under QEMU, there is no telnetd under /usr/sbin/ or /usr/bin. It's not present at all. I have also tried to add the initscript-telnetd refer from meta-arago. But not succeed. Please guild me- how can i will get it with my core-image-basic image. Am i missing any step here for that? Thanks Regards Amit K The contents of this e-mail and any attachment(s) may contain confidential or privileged information for the intended recipient(s). Unintended recipients are prohibited from taking action on the basis of information in this e-mail and using or disseminating the information, and must notify the sender and delete it from their system. LT Infotech will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in this e-mail ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [PATCH 0/1] meta (linux-yocto_3.10): Enable haswell-wc BSP cfg and scc
On 13-10-22 05:46 AM, boon.leong@intel.com wrote: From: Ong Boon Leong boon.leong@intel.com This patch is to enable haswell-wc BSP on linux-yocto_3.10 meta branch. Please pull this into linux-yocto_3.10 meta branch. I'm catching up with merges now. this is now merged, and after some build testing, I'll push it by monday. Bruce Thank you, Ong Boon Leong The following changes since commit 452f0679ea93a6cb4433bebd7177629228a5cf68: lxc: Add lxc kernel config (2013-10-08 15:46:30 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib boonleong/meta/v3.10 http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=boonleong/meta/v3.10 Ong Boon Leong (1): meta: add haswell-wc bsp for Intel Haswell Platform (Walnut Canyon CRB) scc and config files .../bsp/haswell-wc/haswell-wc-preempt-rt.scc | 15 .../bsp/haswell-wc/haswell-wc-standard.scc | 13 ++ .../cfg/kernel-cache/bsp/haswell-wc/haswell-wc.cfg | 25 .../cfg/kernel-cache/bsp/haswell-wc/haswell-wc.scc | 11 + 4 files changed, 64 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc.cfg create mode 100644 meta/cfg/kernel-cache/bsp/haswell-wc/haswell-wc.scc ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
