[yocto] wpa_supplicant on Raspberry Pi 2B
Hello all,I am using a Wi-Pi wireless adapter. My image has the following packages installed. wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon Do I need any additional packages? My wired eth0 works okay. Which document has the most current information on setting up wireless networking?From the information at http://trac.gateworks.com/wiki/Yocto/Wireless I modified my /etc/wpa_supplicant.conf as below without success. ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 update_config=1 network={ scan_ssid=1 ssid="myssid" psk="mypsk" proto=WPA key_mgmt=WPA-PSK }Below is the results I get when I run iwconfig. iwconfig wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off lo no wireless extensions. eth0 no wireless extensions. Thanks in advance. Any help is appreciated. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Safely cleaning 'downloads'
Hi Garry, It's probably a little late (I'm not reading the Yocto mailing lists very often now) but sometime ago I ran out of space myself and I wrote this script that I sent out on oe-core mailing list. It did the job for me. For some reason it didn't make it in master but maybe you find it useful. I didn't test it since then though. Maybe things changed, I don't know. Give it a try if you wish. If you want to play safe, I recommend making a copy of your downloads directory (if you have space left). :) http://lists.openembedded.org/pipermail/openembedded-core/2015-June/106026.html laurentiu On Wed, Sep 30, 2015 at 06:13:39AM -0600, Gary Thomas wrote: > Over time, I tend to build in the same build tree many, many > times. This leads to some really big trees as many things are > duplicated, especially in the 'downloads' directory. > > I use local mirrors and hence my 'downloads' directory is > _mostly_ populated with symbolic links. However, there are > also expanded SCM packages, e.g. git2/xxx > > How can I safely clean up the 'downloads' directory? I already > copy any created tarballs (I use BB_GENERATE_MIRROR_TARBALLS="1" > to preclude unneeded downloads) to my mirror, but I'd like to > periodically clean out the whole directory (without disturbing > my builds of course). I've found out the hard way that just > emptying seems to be unsafe, at least for some recipes like > the [RaspberryPi] Linux kernel recipe which once built seems > to expect the expanded git2/xxx tree to remain. > > Just trying to find ways to recover my lost GB... > > Thanks for any ideas > > -- > > Gary Thomas | Consulting for the > MLB Associates |Embedded world > > -- > ___ > 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] [linux-yocto] [raspberryp2] Error during the build of linux kernel
On 10/02/15 07:58, Karim ATIKI wrote: > Hello Trevor, > > Thanks for your feedback. > You really think that "Fido" is an older release ? Sorry, I didn't mean to imply it was "old" and therefore should be avoided, I meant to point out that it was something that was released before the switch to gcc5 by default :-) > Is the 1.9 release of Yocto stable enough yet ? And will this pb be > fixed as well ? I think the next release will be 2.0. Whether or not it is stable enough is something you will have to evaluate for yourself :-) I'm rather certain this issue is already fixed in master, therefore it should be available for the next release. > > Karim Did you really mean to reply personally? I've re-CC'ed the list, hope you don't mind. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
On 10/02/2015 10:27 AM, Edward Vidal wrote: > Hello all,I am using a Wi-Pi wireless adapter. > My image has the following packages installed. > wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon > Do I need any additional packages? > My wired eth0 works okay. > Which document has the most current information on setting up wireless > networking?From the information at > http://trac.gateworks.com/wiki/Yocto/Wireless > > I modified my /etc/wpa_supplicant.conf as below without success. > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=0 > update_config=1 > Try modifying /etc/network/interfaces like this: https://github.com/EttusResearch/meta-ettus/commit/da86e76d116798e386d073a18453aabb6179a09a#diff-063964fa6e41065c7868b13b1b1644eaR11 it seems wireless extensions are deprecated and you should use the nl80211 driver now. Philip > network={ > scan_ssid=1 > ssid="myssid" > psk="mypsk" > proto=WPA > key_mgmt=WPA-PSK > }Below is the results I get when I run iwconfig. > iwconfig > wlan0 IEEE 802.11bgn ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > > lono wireless extensions. > > eth0 no wireless extensions. > Thanks in advance. Any help is appreciated. > > Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] FILESEXTRAPATHS_prepend fails for systemd
I'm trying to change my /etc/systemd/journald.conf file. I have created a file in: our_system/recipe-core/systemd_%.bbappend With the contents: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" I created a directory in the same path called "systemd" and placed our new version of journald.conf in it. Then I did: bitbake -c cleanall systemd && bitbake systemd bitbake -c cleanall our_image && bitbake our_image Then I checked and the old journald.conf is still installed. What am I doing wrong? Frederick -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW40
Current Dev Position: YP 2.0 Final (rc1 build in QA) Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015 SWAT team rotation: Ross -> Cristian https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * Two failures were encountered during the rc1 build. There is fix queued for the wic selftest issue, the other -lsb kernel module test sanity failures are still being investigated. * Many fixes for issues were merged into master including some of the 'random' failures, thanks to all who've worked on them! * The rc1 build is being put through tests by QA * Prelink looks like it may be broken in release for non FHS/LSB library setups * A successful fido 1.8.1 point release build was queued for QA, 2.0 is taking priority * Now the sstate issue is fixed, a 1.7.3 build will also be made soon as autobuilder time is available. * Reminder: * We have renamed YP 1.9 to YP 2.0. * The current version that is in development will launch as YP 2.0 in October, 2015. * The release name for YP 2.0 is 'jethro'. Key YP 1.9/2.0 Dates: YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA) YP 2.0 final Release Target: Before Oct. 30, 2015 Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features Tracking Metrics: WDD 2170 (last week 2165 ) (https://wiki.yoctoproject.org/charts/combo.html) [If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 * Work Telephone: (503) 712-0534 *Cell:(208) 244-4460 * Email: stephen.k.jol...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project Status WW40
Stephen, Isn't the next meeting next Tuesday? Will there be a meeting since ELCE is in full swing next week? - armin On 10/02/2015 08:26 AM, Jolley, Stephen K wrote: > Current Dev Position: YP 2.0 Final (rc1 build in QA) > Next Deadline: YP 2.0 Final Release Target: Before Oct. 30, 2015 > > SWAT team rotation: Ross -> Cristian > https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team > > Key Status/Updates: > > * Two failures were encountered during the rc1 build. There is fix queued > for the wic selftest issue, the other -lsb kernel module test sanity failures > are still being investigated. > * Many fixes for issues were merged into master including some of the > 'random' failures, thanks to all who've worked on them! > * The rc1 build is being put through tests by QA > * Prelink looks like it may be broken in release for non FHS/LSB library > setups > * A successful fido 1.8.1 point release build was queued for QA, 2.0 is > taking priority > * Now the sstate issue is fixed, a 1.7.3 build will also be made soon as > autobuilder time is available. > * Reminder: > * We have renamed YP 1.9 to YP 2.0. > * The current version that is in development will launch as YP 2.0 in > October, 2015. > * The release name for YP 2.0 is 'jethro'. > > Key YP 1.9/2.0 Dates: > YP 2.0 Final - 2.0 Cut off: Sept. 28, 2015 noon GMT (rc1 build in QA) > YP 2.0 final Release Target: Before Oct. 30, 2015 > > Key Status Links for YP: > https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status > https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule > https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features > > Tracking Metrics: > WDD 2170 (last week 2165 ) > (https://wiki.yoctoproject.org/charts/combo.html) > > [If anyone has suggestions for other information you'd like to see on this > weekly status update, let us know!] > Thanks, > > Stephen K. Jolley > Yocto Project Program Manager > INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 > * Work Telephone: (503) 712-0534 > *Cell:(208) 244-4460 > * Email: stephen.k.jol...@intel.com > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
What `wpa_cli stat' returns? Regards, 2015-10-02 11:56 GMT-03:00 Philip Balister: > On 10/02/2015 10:27 AM, Edward Vidal wrote: >> Hello all,I am using a Wi-Pi wireless adapter. >> My image has the following packages installed. >> wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon >> wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon >> wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon >> wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon >> wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon >> Do I need any additional packages? >> My wired eth0 works okay. >> Which document has the most current information on setting up wireless >> networking?From the information at >> http://trac.gateworks.com/wiki/Yocto/Wireless >> >> I modified my /etc/wpa_supplicant.conf as below without success. >> ctrl_interface=/var/run/wpa_supplicant >> ctrl_interface_group=0 >> update_config=1 >> > > Try modifying /etc/network/interfaces like this: > > https://github.com/EttusResearch/meta-ettus/commit/da86e76d116798e386d073a18453aabb6179a09a#diff-063964fa6e41065c7868b13b1b1644eaR11 > > it seems wireless extensions are deprecated and you should use the > nl80211 driver now. > > Philip > > >> network={ >> scan_ssid=1 >> ssid="myssid" >> psk="mypsk" >> proto=WPA >> key_mgmt=WPA-PSK >> }Below is the results I get when I run iwconfig. >> iwconfig >> wlan0 IEEE 802.11bgn ESSID:off/any >> Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm >> Retry short limit:7 RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> >> lono wireless extensions. >> >> eth0 no wireless extensions. >> Thanks in advance. Any help is appreciated. >> >> Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 >> >> >> > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- "Do or do not. There is no try" Yoda Master -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
Linux kernel recipe which once built seems > to expect the expanded git2/xxx tree to remain. > > Just trying to find ways to recover my lost GB... > > Thanks for any ideas > > -- > > Gary Thomas | Consulting for the > MLB Associates | Embedded world > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Message: 3 Date: Fri, 2 Oct 2015 08:02:49 -0400 From: Trevor Woerner <twoer...@gmail.com> To: Karim ATIKI <karim_at...@hotmail.com> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the build of linux kernel Message-ID: <560e7269.6090...@gmail.com> Content-Type: text/plain; charset=windows-1252 On 10/02/15 07:58, Karim ATIKI wrote: > Hello Trevor, > > Thanks for your feedback. > You really think that "Fido" is an older release ? Sorry, I didn't mean to imply it was "old" and therefore should be avoided, I meant to point out that it was something that was released before the switch to gcc5 by default :-) > Is the 1.9 release of Yocto stable enough yet ? And will this pb be > fixed as well ? I think the next release will be 2.0. Whether or not it is stable enough is something you will have to evaluate for yourself :-) I'm rather certain this issue is already fixed in master, therefore it should be available for the next release. > > Karim Did you really mean to reply personally? I've re-CC'ed the list, hope you don't mind. -- Message: 4 Date: Fri, 2 Oct 2015 14:27:58 + (UTC) From: Edward Vidal <devel...@sbcglobal.net> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: [yocto] wpa_supplicant on Raspberry Pi 2B Message-ID: <1006153332.270433.1443796078701.javamail.ya...@mail.yahoo.com> Content-Type: text/plain; charset="utf-8" Hello all,I am using a Wi-Pi wireless adapter.? My image has the following packages installed. wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon Do I need any additional packages? My wired eth0 works okay. Which document has the most current information on setting up wireless networking?From the information at http://trac.gateworks.com/wiki/Yocto/Wireless I modified my /etc/wpa_supplicant.conf as below without success. ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 update_config=1 network={ ??? scan_ssid=1 ??? ssid="myssid" ??? psk="mypsk" ??? proto=WPA ??? key_mgmt=WPA-PSK }Below is the results I get when I run iwconfig. iwconfig wlan0 IEEE 802.11bgn? ESSID:off/any? ? Mode:Managed? Access Point: Not-Associated?? Tx-Power=0 dBm?? ? Retry short limit:7?? RTS thr:off?? Fragment thr:off ? Encryption key:off ? Power Management:off ????? lo??? no wireless extensions. eth0? no wireless extensions. Thanks in advance.? Any help is appreciated. Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20151002/a3a81a97/attachment-0001.html> -- Message: 5 Date: Fri, 2 Oct 2015 10:56:37 -0400 From: Philip Balister <phi...@balister.org> To: Edward Vidal <devel...@sbcglobal.net>, "yocto@yoctoproject.org" <yocto@yoctoproject.org> Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B Message-ID: <560e9b25.5030...@balister.org> Content-Type: text/plain; charset=windows-1252 On 10/02/2015 10:27 AM, Edward Vidal wrote: > Hello all,I am using a Wi-Pi wireless adapter. > My image has the following packages installed. > wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon > Do I need any additional packages? > My wired eth0 works okay. > Which document has the most current information on setting up wireless > networking?From the information at > http://trac.gateworks.com/wiki/Yocto/Wireless > > I modified my /etc/wpa_supplicant.conf as below without success. > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=0 > update
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
On Fri, Oct 02, 2015 at 03:58:04PM +, Fred Ollinger wrote: > I'm trying to change my /etc/systemd/journald.conf file. > > > I have created a file in: > > > our_system/recipe-core/systemd_%.bbappend > > > With the contents: > > > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" This works only for files listed in SRC_URI, that's not the case for journald.conf which is included directly in systemd sources. > > I created a directory in the same path called "systemd" and placed our new > version of journald.conf in it. > > Then I did: > > bitbake -c cleanall systemd && bitbake systemd > bitbake -c cleanall our_image && bitbake our_image > > Then I checked and the old journald.conf is still installed. > > What am I doing wrong? > > Frederick > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
On Fri, Oct 2, 2015 at 11:22 AM, Daniel.wrote: > Where can I find this recipetool!? It seems a nice tool to have :) > It's in oe-core/scripts or poky/scripts in any recent release. It'll be in the PATH after sourcing the setup scripts. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] [PATCH 0/3] i915 graphics driver bug fixes for Braswell
On 15-09-29 09:39 PM, Chang Rebecca Swee Fun wrote: Hi, This patches are bug fixes patch backported from upstream mainline kernel. We encountered GPU hang issue during MediaSDK encoding. The patches will remove redundant gen8_ppgtt_unmap_pages and set up a page table making all pt entries pointing to the scratch page before mapping to avoid out of bound access or proactive prefetch. Systems without LLC require an explicit flush, which eventually solves MediaSDK encoding gpu hang issue. The patches have been tested and validated on Cherry Hill platform using Common BSP build. Please merge these patches into linux-yocto-4.1 standard/base branch. Please provide feedback if you have any concern on merging this patchset. merged. SRCREV updates will be out shortly (once my build test completes). Bruce Thank you. Regards, Rebecca Michel Thierry (3): drm/i915: Remove _entry from PPGTT page structures drm/i915: Remove unnecessary gen8_ppgtt_unmap_pages drm/i915/gen8: Initialize page tables drivers/gpu/drm/i915/i915_gem_gtt.c | 108 drivers/gpu/drm/i915/i915_gem_gtt.h | 16 +++--- drivers/gpu/drm/i915/i915_trace.h | 4 +- 3 files changed, 57 insertions(+), 71 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
On Fri, Oct 2, 2015 at 11:11 AM, Daniel.wrote: > But this will only work if journald.conf are the same in all systemd > versions (since you use a _%.bbappend). A better solution would be append > install task with a copy from your custom journald.conf to install folder, > something like: > > do_install_append() { > cp ${S}/myjournald.conf ${D}/propper/path/to/journald.conf > } Which is precisely what recipetool appendfile will do for you :) -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
Where can I find this recipetool!? It seems a nice tool to have :) 2015-10-02 15:21 GMT-03:00 Christopher Larson: > > On Fri, Oct 2, 2015 at 11:11 AM, Daniel. wrote: > >> But this will only work if journald.conf are the same in all systemd >> versions (since you use a _%.bbappend). A better solution would be append >> install task with a copy from your custom journald.conf to install folder, >> something like: >> >> do_install_append() { >> cp ${S}/myjournald.conf ${D}/propper/path/to/journald.conf >> } > > > Which is precisely what recipetool appendfile will do for you :) > -- > Christopher Larson > clarson at kergoth dot com > Founder - BitBake, OpenEmbedded, OpenZaurus > Maintainer - Tslib > Senior Software Engineer, Mentor Graphics > -- *"Do or do not. There is no try"* *Yoda Master* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
On Fri, Oct 2, 2015 at 8:58 AM, Fred Ollingerwrote: > I'm trying to change my /etc/systemd/journald.conf file. > recipetool appendfile sounds like exactly what you want here. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
But this will only work if journald.conf are the same in all systemd versions (since you use a _%.bbappend). A better solution would be append install task with a copy from your custom journald.conf to install folder, something like: do_install_append() { cp ${S}/myjournald.conf ${D}/propper/path/to/journald.conf } Cheers, 2015-10-02 14:26 GMT-03:00 Daniel.: > You can solve this by editing the original journal.conf, creating a > patch with modifications and adding it to your .bbappend > > 2015-10-02 13:44 GMT-03:00 Christopher Larson : > > > > On Fri, Oct 2, 2015 at 8:58 AM, Fred Ollinger > > > wrote: > >> > >> I'm trying to change my /etc/systemd/journald.conf file. > > > > > > recipetool appendfile sounds like exactly what you want here. > > -- > > Christopher Larson > > clarson at kergoth dot com > > Founder - BitBake, OpenEmbedded, OpenZaurus > > Maintainer - Tslib > > Senior Software Engineer, Mentor Graphics > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > -- > "Do or do not. There is no try" > Yoda Master > -- *"Do or do not. There is no try"* *Yoda Master* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
mbedded-core/2015-June/106026.html > > laurentiu > > On Wed, Sep 30, 2015 at 06:13:39AM -0600, Gary Thomas wrote: > > Over time, I tend to build in the same build tree many, many > > times. This leads to some really big trees as many things are > > duplicated, especially in the 'downloads' directory. > > > > I use local mirrors and hence my 'downloads' directory is > > _mostly_ populated with symbolic links. However, there are > > also expanded SCM packages, e.g. git2/xxx > > > > How can I safely clean up the 'downloads' directory? I already > > copy any created tarballs (I use BB_GENERATE_MIRROR_TARBALLS="1" > > to preclude unneeded downloads) to my mirror, but I'd like to > > periodically clean out the whole directory (without disturbing > > my builds of course). I've found out the hard way that just > > emptying seems to be unsafe, at least for some recipes like > > the [RaspberryPi] Linux kernel recipe which once built seems > > to expect the expanded git2/xxx tree to remain. > > > > Just trying to find ways to recover my lost GB... > > > > Thanks for any ideas > > > > -- > > > > Gary Thomas| Consulting for the > > MLB Associates |Embedded world > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- > > Message: 3 > Date: Fri, 2 Oct 2015 08:02:49 -0400 > From: Trevor Woerner <twoer...@gmail.com> > To: Karim ATIKI <karim_at...@hotmail.com> > Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> > Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the > build of linux kernel > Message-ID: <560e7269.6090...@gmail.com> > Content-Type: text/plain; charset=windows-1252 > > On 10/02/15 07:58, Karim ATIKI wrote: > > Hello Trevor, > > > > Thanks for your feedback. > > You really think that "Fido" is an older release ? > > Sorry, I didn't mean to imply it was "old" and therefore should be > avoided, I meant to point out that it was something that was released > before the switch to gcc5 by default :-) > > > Is the 1.9 release of Yocto stable enough yet ? And will this pb be > > fixed as well ? > > I think the next release will be 2.0. Whether or not it is stable enough > is something you will have to evaluate for yourself :-) I'm rather > certain this issue is already fixed in master, therefore it should be > available for the next release. > > > > > Karim > > Did you really mean to reply personally? I've re-CC'ed the list, hope > you don't mind. > > > -- > > Message: 4 > Date: Fri, 2 Oct 2015 14:27:58 + (UTC) > From: Edward Vidal <devel...@sbcglobal.net> > To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> > Subject: [yocto] wpa_supplicant on Raspberry Pi 2B > Message-ID: > <1006153332.270433.1443796078701.javamail.ya...@mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Hello all,I am using a Wi-Pi wireless adapter.? > My image has the following packages installed. > wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon > Do I need any additional packages? > My wired eth0 works okay. > Which document has the most current information on setting up wireless > networking?From the information at > http://trac.gateworks.com/wiki/Yocto/Wireless > > I modified my /etc/wpa_supplicant.conf as below without success. > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=0 > update_config=1 > > network={ > ??? scan_ssid=1 > ??? ssid="myssid" > ??? psk="mypsk" > ??? proto=WPA > ??? key_mgmt=WPA-PSK > }Below is the results I get when I run iwconfig. > iwconfig > wlan0 IEEE 802.11bgn? ESSID:off/any? > ? Mode:Managed? Access Point: Not-Associated?? Tx-Power=0 dBm?? > ? Retry short limit:7?? RTS thr:off?? Fragment thr:off > ? Encryption key:off > ? Power Management:off > ? > lo??? no wireless extensions. > > eth0? no wireless extensions. > Thanks in advance.?
Re: [yocto] FILESEXTRAPATHS_prepend fails for systemd
Daisy doesn't have it :( Thank you for this information :) Cheers, 2015-10-02 15:24 GMT-03:00 Christopher Larson: > > On Fri, Oct 2, 2015 at 11:22 AM, Daniel. wrote: > >> Where can I find this recipetool!? It seems a nice tool to have :) >> > > It's in oe-core/scripts or poky/scripts in any recent release. It'll be in > the PATH after sourcing the setup scripts. > -- > Christopher Larson > clarson at kergoth dot com > Founder - BitBake, OpenEmbedded, OpenZaurus > Maintainer - Tslib > Senior Software Engineer, Mentor Graphics > -- *"Do or do not. There is no try"* *Yoda Master* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
t; my builds of course). I've found out the hard way that just > > emptying seems to be unsafe, at least for some recipes like > > the [RaspberryPi] Linux kernel recipe which once built seems > > to expect the expanded git2/xxx tree to remain. > > > > Just trying to find ways to recover my lost GB... > > > > Thanks for any ideas > > > > -- > > > > Gary Thomas| Consulting for the > > MLB Associates |Embedded world > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- > > Message: 3 > Date: Fri, 2 Oct 2015 08:02:49 -0400 > From: Trevor Woerner <twoer...@gmail.com> > To: Karim ATIKI <karim_at...@hotmail.com> > Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org> > Subject: Re: [yocto] [linux-yocto] [raspberryp2] Error during the > build of linux kernel > Message-ID: <560e7269.6090...@gmail.com> > Content-Type: text/plain; charset=windows-1252 > > On 10/02/15 07:58, Karim ATIKI wrote: > > Hello Trevor, > > > > Thanks for your feedback. > > You really think that "Fido" is an older release ? > > Sorry, I didn't mean to imply it was "old" and therefore should be > avoided, I meant to point out that it was something that was released > before the switch to gcc5 by default :-) > > > Is the 1.9 release of Yocto stable enough yet ? And will this pb be > > fixed as well ? > > I think the next release will be 2.0. Whether or not it is stable enough > is something you will have to evaluate for yourself :-) I'm rather > certain this issue is already fixed in master, therefore it should be > available for the next release. > > > > > Karim > > Did you really mean to reply personally? I've re-CC'ed the list, hope > you don't mind. > > > -- > > Message: 4 > Date: Fri, 2 Oct 2015 14:27:58 + (UTC) > From: Edward Vidal <devel...@sbcglobal.net> > To: "yocto@yoctoproject.org" <yocto@yoctoproject.org> > Subject: [yocto] wpa_supplicant on Raspberry Pi 2B > Message-ID: > <1006153332.270433.1443796078701.javamail.ya...@mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Hello all,I am using a Wi-Pi wireless adapter.? > My image has the following packages installed. > wpa-supplicant-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-cli-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-dev-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-doc-2.4-r0.cortexa7hf_vfp_vfpv4_neon > wpa-supplicant-passphrase-2.4-r0.cortexa7hf_vfp_vfpv4_neon > Do I need any additional packages? > My wired eth0 works okay. > Which document has the most current information on setting up wireless > networking?From the information at > http://trac.gateworks.com/wiki/Yocto/Wireless > > I modified my /etc/wpa_supplicant.conf as below without success. > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=0 > update_config=1 > > network={ > ??? scan_ssid=1 > ??? ssid="myssid" > ??? psk="mypsk" > ??? proto=WPA > ??? key_mgmt=WPA-PSK > }Below is the results I get when I run iwconfig. > iwconfig > wlan0 IEEE 802.11bgn? ESSID:off/any? > ? Mode:Managed? Access Point: Not-Associated?? Tx-Power=0 dBm?? > ? Retry short limit:7?? RTS thr:off?? Fragment thr:off > ? Encryption key:off > ? Power Management:off > ? > lo??? no wireless extensions. > > eth0? no wireless extensions. > Thanks in advance.? Any help is appreciated. > > Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613 > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.yoctoproject.org/pipermail/yocto/attachments/20151002/a3a81a97/attachment-0001.html > > > > -- > > Message: 5 > Date: Fri, 2 Oct 2015 10:56:37 -0400 > From: Philip Balister <phi...@balister.org> > To: Edward Vidal <devel...@sbcglobal.net>,"yocto@yoctoproject.org" > <yocto@yoctoproject.org> > Subject: Re: [yocto] wpa_supplicant on Raspberry Pi 2B > Message-ID: <560e9b25.5030...@balister.org> > Content-Type: text/plain; charset=windows-1252 > > > On 10/02/2015 10:27 AM, Edward Vidal wrote: > > Hello all,I am using a Wi-Pi wirel
Re: [yocto] [meta-raspberrypi] compiling userland
On Sun, Sep 27, 2015 at 10:24:28PM +0200, Andreas Müller wrote: > On Fri, Sep 25, 2015 at 6:42 AM, Khem Rajwrote: > > Can you try the patches from > > https://github.com/kraj/meta-raspberrypi/commits/kraj/master > > > Hi Khem, > > Because of running into same issues I've tried your branch and get > errors as attached with current oe-core. > > Off-topic note: I think this layer is totally under-maintained. There > were many patches send that were not even commented. This ends up in > forks (e.g yours - and yes I've seen your efforts in sending patches) > which should be avoided. > Started to get back on track. Hope this won't happen again. -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] userland: Fix multiple inline issues while building with gcc 5.x
On Sun, Sep 27, 2015 at 03:34:14PM +0200, Tom Doehring wrote: > Building userland source with gcc 5.x causes multiple issues such as: > > vcos_thread.h:186:15: warning: inline function 'vcos_thread_get_affinity' > declared but never defined > | VCOS_UNSIGNED vcos_thread_get_affinity(VCOS_THREAD_T *thread); > > The following patches fixes these issues and allows building userland on the > current > poky master branch. > > Signed-off-by: Tom Doehring> --- > .../userland/0001-Use-newer-POSIX-macro.patch | 35 > -- > .../userland/0001-fix-gcc-5.x-inlines.patch| 26 > .../userland/userland/0002-fix-musl-build.patch| 22 ++ > .../0003-fix-alloc-size-uninitialized.patch| 13 > recipes-graphics/userland/userland_git.bb | 13 +--- > 5 files changed, 70 insertions(+), 39 deletions(-) > delete mode 100644 > recipes-graphics/userland/userland/0001-Use-newer-POSIX-macro.patch > create mode 100644 > recipes-graphics/userland/userland/0001-fix-gcc-5.x-inlines.patch > create mode 100644 > recipes-graphics/userland/userland/0002-fix-musl-build.patch > create mode 100644 > recipes-graphics/userland/userland/0003-fix-alloc-size-uninitialized.patch > Tested on GCC 5.2.0 and worked fine. Merged to master. Thank you. -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] compiling userland
Hi Tom, On Fri, Sep 25, 2015 at 01:19:43AM +0200, Tom Martin wrote: > i'm completly new to yocta and doing my first steps. > > plan is to build a system with a small footprint for low-latency video > wifibroadcast. > > first steps are trying to build rpi-test-image including omxplayer. but > compiling fails when compiling userland. > > last lines before the failure are. am i missing just something basic? This should be now fixed in master. Could you give it a try? -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wpa_supplicant on Raspberry Pi 2B
Hi all,Still no success getting wifi working.Any and all help appreciated. Created a new image which installed 46 new rpms linux-firmware see below. ps -ax | grep wpa_supplicant 503 ? S 0:00 /usr/sbin/wpa_supplicant -u 704 pts/0 R+ 0:00 grep wpa_supplicant root@raspberrypi2:~# wpa_cli stat Failed to connect to non-global ctrl_ifname: (nil) error: Success root@raspberrypi2:~# wpa_cli stat Failed to connect to non-global ctrl_ifname: (nil) error: Success root@raspberrypi2:~# wpa_supplicant -ddd -B -i wlan0 -D nl80211 -c /etc/wpa_supplicant.conf wpa_supplicant v2.4 random: Trying to read entropy from /dev/random Successfully initialized wpa_supplicant Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group='0' update_config=1 Line: 5 - start of a new network block scan_ssid=1 (0x1) ssid - hexdump_ascii(len=10): 41 54 54 39 78 32 78 39 6a 37 ATT9x2x9j7 PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED] proto: 0x1 key_mgmt: 0x2 PSK (from passphrase) - hexdump(len=32): [REMOVED] Priority group 0 id=0 ssid='ATT9x2x9j7' rfkill: initial event: idx=0 type=1 op=0 soft=1 hard=0 rfkill: WLAN soft blocked nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported cipher 00-0f-ac:2 nl80211: Supported cipher 00-0f-ac:4 nl80211: Using driver-based off-channel TX nl80211: interface wlan0 in phy phy0 nl80211: Set mode ifindex 3 iftype 2 (STATION) nl80211: Subscribe to mgmt frames with non-AP handle 0x5a6e68 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=06 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=0a07 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=0a11 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=1101 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=1102 nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5a6e68 match=0505 nl80211: Could not yet enable interface 'wlan0' due to rfkill netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT) nl80211: driver param='(null)' Add interface wlan0 to a new radio phy0 nl80211: Regulatory information - country=00 nl80211: 2402-2472 @ 40 MHz 20 mBm nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR) nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR) nl80211: 5170-5250 @ 160 MHz 20 mBm (no IR) nl80211: 5250-5330 @ 160 MHz 20 mBm (DFS) (no IR) nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR) nl80211: Added 802.11b mode based on 802.11g information wlan0: Own MAC address: 40:a5:ef:05:4d:01 wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 nl80211: set_key failed; err=-100 Network is down) wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0 nl80211: set_key failed; err=-100 Network is down) wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0 nl80211: set_key failed; err=-100 Network is down) wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0 nl80211: set_key failed; err=-100 Network is down) wlan0: RSN: flushing PMKID list in the driver nl80211: Flush PMKIDs wlan0: Setting scan request: 0.10 sec wlan0: WPS: UUID based on MAC address: 50fb4973-c5e3-5899-b3c0-27a64501d294 GnuTLS: Library version 3.3.14 (runtime) - 3.3.14 (build) EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized nl80211: Skip set_supp_port(unauthorized) while not associated EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED Using existing control interface directory. ctrl_interface_group=0 wlan0: Added interface wlan0 wlan0: State: DISCONNECTED -> DISCONNECTED nl80211: Set wlan0 operstate 0->0 (DORMANT) netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT) Daemonize.. root@raspberrypi2:~# wpa_cli stat Selected interface 'wlan0' wpa_state=INTERFACE_DISABLED address=40:a5:ef:05:4d:01 uuid=50fb4973-c5e3-5899-b3c0-27a64501d294 root@raspberrypi2:~# ifconfig wlan0 wlan0 Link encap:Ethernet HWaddr 40:A5:EF:05:4D:01 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Thanks +linux-firmware-0.0+git0+3161bfa479-r0.all +linux-firmware-ar3k-0.0+git0+3161bfa479-r0.all
Re: [yocto] [meta-raspberrypi][PATCH V3 2/5] userland: Add wayland support
On Wed, Sep 23, 2015 at 04:52:46PM -0700, Khem Raj wrote: > Andrei > > > On Sep 23, 2015, at 3:58 PM, Andrei Gherzanwrote: > > > > On Mon, Aug 24, 2015 at 12:51:38AM -0700, Khem Raj wrote: > >> backport and fix needed patches for supporting wayland-egl > >> use PACKAGECONFIG for wayland so we can add proper DEPENDS on wayland > >> Fix QA warnings about dev-so > >> > >> Signed-off-by: Khem Raj > >> --- > >> ...-applications-to-set-next-resource-handle.patch | 210 +++ > >> ...ayland-Add-support-for-the-Wayland-winsys.patch | 1847 > >> > >> .../0006-wayland-Add-Wayland-example.patch | 864 + > >> ...-wayland-egl-Add-bcm_host-to-dependencies.patch | 30 + > >> recipes-graphics/userland/userland_git.bb | 13 +- > >> 5 files changed, 2963 insertions(+), 1 deletion(-) > >> create mode 100644 > >> recipes-graphics/userland/userland/0004-Allow-applications-to-set-next-resource-handle.patch > >> create mode 100644 > >> recipes-graphics/userland/userland/0005-wayland-Add-support-for-the-Wayland-winsys.patch > >> create mode 100644 > >> recipes-graphics/userland/userland/0006-wayland-Add-Wayland-example.patch > >> create mode 100644 > >> recipes-graphics/userland/userland/0007-wayland-egl-Add-bcm_host-to-dependencies.patch > >> > > > > Hello, > > > > Any ideas why I encounter difficulties while applying this patch? > > > > it was send few weeks back, I don’t know if something got into upstream in > between thats causing it. In any case > I have rebased the branch on my github fork > > https://github.com/kraj/meta-raspberrypi/commits/kraj/master > > Let me know if that will be convenient to pick up > I had to rebase your patches again. I created a temporary branch: khem_wayland in git.yoctoproject.org:meta-raspberrypi . Now userland build fails with: interface/vmcs_host/wayland-dispmanx-server-protocol.h: No such file or directory Who should provide this header file? Userland? Could you throw a look on the branch above and try to replicate this? Thanks, -- Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.0.rc1.rc1 now available.
A release candidate build for yocto-2.0.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 84c049b9cb80b50fd32b716c2ae97e3f0d4e3cd7 meta-fsl-arm : 10471566d2868b07f8ac832b94d5e98a463826ba meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae meta-qt3 : 5233565c80db869f6f539f37f26ea6662d9dc5f6 meta-fsl-ppc : 59fc0c33d2de5db65af4c09c4d28fd78fa0f7b4f poky : eac61f37e36099f74485dab398b57f3812826d17 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH V3 2/5] userland: Add wayland support
Andrei Userland have been updated plus some of my patches to userland has been applied via another commit from different person but not all and so on, not even me am certain as to whats needed and what not anymore. So I have rebased my remaining changes here. https://github.com/kraj/meta-raspberrypi/commits/kraj/master I am doing a build and will update if I see any issues or otherwise. Thanks -Khem On Fri, Oct 2, 2015 at 3:31 PM, Andrei Gherzanwrote: > On Wed, Sep 23, 2015 at 04:52:46PM -0700, Khem Raj wrote: >> Andrei >> >> > On Sep 23, 2015, at 3:58 PM, Andrei Gherzan wrote: >> > >> > On Mon, Aug 24, 2015 at 12:51:38AM -0700, Khem Raj wrote: >> >> backport and fix needed patches for supporting wayland-egl >> >> use PACKAGECONFIG for wayland so we can add proper DEPENDS on wayland >> >> Fix QA warnings about dev-so >> >> >> >> Signed-off-by: Khem Raj >> >> --- >> >> ...-applications-to-set-next-resource-handle.patch | 210 +++ >> >> ...ayland-Add-support-for-the-Wayland-winsys.patch | 1847 >> >> >> >> .../0006-wayland-Add-Wayland-example.patch | 864 + >> >> ...-wayland-egl-Add-bcm_host-to-dependencies.patch | 30 + >> >> recipes-graphics/userland/userland_git.bb | 13 +- >> >> 5 files changed, 2963 insertions(+), 1 deletion(-) >> >> create mode 100644 >> >> recipes-graphics/userland/userland/0004-Allow-applications-to-set-next-resource-handle.patch >> >> create mode 100644 >> >> recipes-graphics/userland/userland/0005-wayland-Add-support-for-the-Wayland-winsys.patch >> >> create mode 100644 >> >> recipes-graphics/userland/userland/0006-wayland-Add-Wayland-example.patch >> >> create mode 100644 >> >> recipes-graphics/userland/userland/0007-wayland-egl-Add-bcm_host-to-dependencies.patch >> >> >> > >> > Hello, >> > >> > Any ideas why I encounter difficulties while applying this patch? >> > >> >> it was send few weeks back, I don’t know if something got into upstream in >> between thats causing it. In any case >> I have rebased the branch on my github fork >> >> https://github.com/kraj/meta-raspberrypi/commits/kraj/master >> >> Let me know if that will be convenient to pick up >> > > I had to rebase your patches again. I created a temporary branch: khem_wayland > in git.yoctoproject.org:meta-raspberrypi . Now userland build fails with: > > interface/vmcs_host/wayland-dispmanx-server-protocol.h: No such file or > directory > > Who should provide this header file? Userland? Could you throw a look on the > branch above and try to replicate this? > > Thanks, > > -- > Andrei Gherzan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto