Re: [yocto] QA cycle report for 2.5.3 RC3
>-Original Message- >From: richard.pur...@linuxfoundation.org >Sent: Tuesday, 23 April, 2019 10:31 PM >To: Jain, Sangeeta ; 'yocto@yoctoproject.org' >; Eggleton, Paul ; 'Michael >Halstead' ; Erway, Tracey M >; 'sjolley.yp...@gmail.com' >; 'openembedded-core- >requ...@lists.openembedded.org' requ...@lists.openembedded.org> >Cc: Sangal, Apoorv ; Yeoh, Ee Peng >; Graydon, Tracy ; >Tummalapalli, Vineela >Subject: Re: QA cycle report for 2.5.3 RC3 > >On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: >> >> QA cycle report for 2.5.3 RC3: >> >> No high milestone defects. >> Test results are available at following location: >> ·For results of all automated tests, refer to results at >> public AB [1]. >> ·For other test results, refer to attachment [2]. >> ·For test report for test cases run by Intel and WR team, >> refer attachment [3] >> ·For full test report, refer attachment [4] >> ·For ptest results, please refer to results at public AB [5] >> ·For ptest report, refer to attachment [6] >> No new defects are found in this cycle. >> Number of existing issues observed in this release is 2- toaster [7] >> and Build-appliance [8] For ptest, regression data is not available >> for this release. No timeout issues. >> Test result report on Public AB shows no failures. > >I've been discussing with Tracy and Vineela how to best handle the test >results for >the release for 2.5.3. In the end I: > >a) Copied in the ptest results to the right place. This will happen >automagically in >all future builds: > >https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults/qemux86-64- >ptest/ > >b) Copied in the intel test results to their own directory: > >https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults-intel/ > >c) Manually generated an updated test report for the combined results with the >commands: > >$ cd /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.5.3 >$resulttool report . > testreport.txt > >d) Added a header to the report which consisted of the report from QA with >details of the bugs etc. > >This means we have a top level testreport file which contains all the test >information about the release. > >I'd like to make this the standard procedure for release. The release notes and >announcement can refer to the test report included with the release and the >test >results as its there all together. > >Ultimately I'd like to improve the formatting of the report (separate out ptest >regressions from the other regressions, maybe html, maybe graphs, better >regression information) but that is something for the future. > >Does that work for everyone? That looks great to me. As a further improvement for sharing of test results, I am working to create a wiki page for consolidated test results. For 2.5.3, it can be viewed at: https://wiki.yoctoproject.org/wiki/WW16_-_2019-04-18_-_Full_Test_Cycle_2.5.3_RC3 After you have added more results on AB, I will change some existing links on this web page with the new ones. Another thought I have is that since for any release, all data will be removed from public AB after few days of release, Should I include here a link to "yocto-testresults" git repo? It will make this wiki page more useful for reference in future as well. > >Cheers, > >Richard > Thanks & Regards, Sangeeta Jain -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What is the right SRC_URI syntax for g...@bitbucket.org?
Hi,
This works for me. I've have setup ssh my identity for Bitbucket.
I use this in my recipes:
SRC_URI = "gitsm://g...@bitbucket.org//.git;protocol=ssh;branch=${BRANCH}"
Cheers,
Erik
On 21 Apr 2019, 02:58 +0200, JH , wrote:
Hi,
Could someone kindly clarify what is the syntax to access git source
from bitbucket.org? I tried following different patterns, nothing
works:
SRC_URI = "git://bitbucket.org//;protocol=http;branch=${BRANCH}"
SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"
Thank you.
Kind regards,
- jupiter
On 4/20/19, JH wrote:
Hi,
Sorry for a new starter questions, I searched Internet, there are a
few examples to set up:
SRC_URI = "git://@bitbucket.org//.git;protocol=ssh";branch=${BRANCH}"
Not only that does not work, I have set up the public key to access
the git bitbucket repository:
$ ssh -v g...@bitbucket.org
The Yocto also complained SRCREV, following some blog to add the
SRCREV = "${AUTOREV}" that not work either.
Thank you.
Kind regards,
- jh
--
___
yocto mailing list
yocto@yoctoproject.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7C5e970c621c2e4a0f349108d6c5f47377%7C84df9e7fe9f640afb435%7C1%7C0%7C636914051024571809&sdata=Ck9czRr02QsCIpJKbRtJTmcOAgQMPg64v7km9%2FAv3Ik%3D&reserved=0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 1/2] meta-tpm/conf/layer.conf: update layer dependencies
Add openembedded-layer to layer dependencies. Fix the following build errors: ERROR: Required build target 'tpm2-pkcs11' has no buildable providers. Missing or unbuildable dependency chain was: ['tpm2-pkcs11', 'dstat'] ERROR: Required build target 'cryptsetup-tpm-incubator' has no buildable providers. Missing or unbuildable dependency chain was: ['cryptsetup-tpm-incubator', 'libdevmapper'] ERROR: Required build target 'tpm2-totp' has no buildable providers. Missing or unbuildable dependency chain was: ['tpm2-totp', 'qrencode'] Signed-off-by: Yi Zhao --- meta-tpm/conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-tpm/conf/layer.conf b/meta-tpm/conf/layer.conf index 15a2bef..bf9a76e 100644 --- a/meta-tpm/conf/layer.conf +++ b/meta-tpm/conf/layer.conf @@ -12,4 +12,5 @@ LAYERSERIES_COMPAT_tpm-layer = "thud warrior" LAYERDEPENDS_tpm-layer = " \ core \ +openembedded-layer \ " -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH 2/2] meta-tpm/README: update
Add more description Signed-off-by: Yi Zhao --- meta-tpm/README | 57 + 1 file changed, 57 insertions(+) diff --git a/meta-tpm/README b/meta-tpm/README index bbc70bb..dd662b3 100644 --- a/meta-tpm/README +++ b/meta-tpm/README @@ -2,3 +2,60 @@ meta-tpm layer == This layer contains base TPM recipes. + +Dependencies + + +This layer depends on: + + URI: git://git.openembedded.org/openembedded-core + branch: master + revision: HEAD + prio: default + + URI: git://git.openembedded.org/meta-openembedded/meta-oe + branch: master + revision: HEAD + prio: default + +Adding the meta-tpm layer to your build + + +In order to use this layer, you need to make the build system aware of +it. + +Assuming this layer exists at the top-level of your +yocto build tree, you can add it to the build system by adding the +location of the meta-tpm layer to bblayers.conf, along with any +other layers needed. e.g.: + + BBLAYERS ?= " \ +/path/to/oe-core/meta \ +/path/to/meta-openembedded/meta-oe \ +/path/to/layer/meta-tpm \ + + +Maintenance +--- + +Send pull requests, patches, comments or questions to yocto@yoctoproject.org + +When sending single patches, please using something like: +'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-security][PATCH' + +These values can be set as defaults for this repository: + +$ git config sendemail.to yocto@yoctoproject.org +$ git config format.subjectPrefix meta-security][PATCH + +Now you can just do 'git send-email origin/master' to send all local patches. + +Maintainers:Armin Kuster + + +License +=== + +All metadata is MIT licensed unless otherwise stated. Source code included +in tree for individual recipes is under the LICENSE stated in each recipe +(.bb file) unless otherwise stated. -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] WARNING message: Building library didn't pass LDFLAGS? [ldflags]
It means that the compile didn't respect LDFLAGS from the environment (which sets the ELF hashing type). Most usual build systems handle this for you, but if your recipe uses hand-coded Makefiles then you'll need to figure out what they're doing and how to make it respect $LDFLAGS. Ross On Tue, 23 Apr 2019 at 23:49, JH wrote: > > Hi, > > What is the following WARNING means, how can I fix it? > > yocto-sample-1.0.0-0 do_package_qa: QA Issue: No GNU_HASH in the ELF > binary my_library, didn't pass LDFLAGS? [ldflags] > > Thank you. > > Kind regards, > > - jupiter > -- > ___ > 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] WARNING message: Building library didn't pass LDFLAGS? [ldflags]
Hi, What is the following WARNING means, how can I fix it? yocto-sample-1.0.0-0 do_package_qa: QA Issue: No GNU_HASH in the ELF binary my_library, didn't pass LDFLAGS? [ldflags] Thank you. Kind regards, - jupiter -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH v2 01/10] conf/machine: add support for rk3399
On Tue 2019-04-23 @ 09:25:05 PM, Randy 'ayaka' Li wrote: > RK3399 is a new generation powerful SoC from Rockchip, which has > Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU. > > Signed-off-by: Randy 'ayaka' Li > --- > conf/machine/excavator-rk3399.conf | 12 > conf/machine/firefly-rk3399.conf | 14 ++ > conf/machine/include/rk3399.inc| 17 + > 3 files changed, 43 insertions(+) > create mode 100644 conf/machine/excavator-rk3399.conf > create mode 100644 conf/machine/firefly-rk3399.conf > create mode 100644 conf/machine/include/rk3399.inc > > diff --git a/conf/machine/excavator-rk3399.conf > b/conf/machine/excavator-rk3399.conf > new file mode 100644 > index 000..8506a50 > --- /dev/null > +++ b/conf/machine/excavator-rk3399.conf > @@ -0,0 +1,12 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: EXCAVATOR 3399 > + > +include conf/machine/include/rk3399.inc > + > +KERNEL_DEVICETREE = "rockchip/rk3399-sapphire-excavator.dtb" > +UBOOT_MACHINE = "evb-rk3399_defconfig" > + > +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=B921B045-1DF0 > rootfstype=ext4 init=/sbin/init" > diff --git a/conf/machine/firefly-rk3399.conf > b/conf/machine/firefly-rk3399.conf > new file mode 100644 > index 000..4e35c3d > --- /dev/null > +++ b/conf/machine/firefly-rk3399.conf > @@ -0,0 +1,14 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: Firefly RK3399 > +#@DESCRIPTION: Firefly-RK3399 is a Six-Core 64-bit High-Performance Platform. > +#http://www.t-firefly.com/en/ > + > +include conf/machine/include/rk3399.inc > + > +KERNEL_DEVICETREE = "rockchip/rk3399-firefly.dtb" > +UBOOT_MACHINE = "evb-rk3399_defconfig" > + > +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=B921B045-1DF0 > rootfstype=ext4 init=/sbin/init" > diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc > new file mode 100644 > index 000..9237616 > --- /dev/null > +++ b/conf/machine/include/rk3399.inc > @@ -0,0 +1,17 @@ > +# Copyright (C) 2019 SUMOMO Computer Association > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +SOC_FAMILY = "rk3399" > + > +require conf/machine/include/tune-cortexa72.inc > +require conf/machine/include/soc-family.inc > +require conf/machine/include/rockchip-defaults.inc > + > +SERIAL_CONSOLES = "150;ttyS2" > +KERNEL_IMAGETYPE = "Image" > +KBUILD_DEFCONFIG = "defconfig" > + > +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" Using u-boot-rockchip causes build failures. In both cases (excavator-rk3399 and firefly-rk3399) I get: | # | # configuration written to .config | # | make[1]: Leaving directory '/z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/build' | make: Leaving directory '/z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/git' | /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/run.do_configure.27647: line 113: merge_config.sh: command not found | WARNING: /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/run.do_configure.27647:1 exit 127 from 'merge_config.sh -m .config' | ERROR: Function failed: do_configure (log file is located at /z/build-master/meta-rockchip/build/tmp-glibc/work/firefly_rk3399-oe-linux/u-boot-rockchip/20171218-r0/temp/log.do_configure.27647) Do you have an updated recipe for u-boot-rockchip? > + > +IMAGE_FSTYPES = "rockchip-gpt-img" > +IMAGE_CLASSES = "rockchip-gpt-img" > -- > 2.20.1 > > -- > ___ > 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] [OE-core] QA cycle report for 2.5.3 RC3
On 4/23/19 7:35 AM, richard.pur...@linuxfoundation.org wrote: > On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: >> >> QA cycle report for 2.5.3 RC3: >> >> No high milestone defects. >> Test results are available at following location: >> ·For results of all automated tests, refer to results at >> public AB [1]. >> ·For other test results, refer to attachment [2]. >> ·For test report for test cases run by Intel and WR team, >> refer attachment [3] >> ·For full test report, refer attachment [4] >> ·For ptest results, please refer to results at public AB [5] >> ·For ptest report, refer to attachment [6] >> No new defects are found in this cycle. >> Number of existing issues observed in this release is 2- toaster [7] >> and Build-appliance [8] >> For ptest, regression data is not available for this release. No >> timeout issues. >> Test result report on Public AB shows no failures. > I've been discussing with Tracy and Vineela how to best handle the test > results for the release for 2.5.3. In the end I: > > a) Copied in the ptest results to the right place. This will happen > automagically in all future builds: > > https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults/qemux86-64-ptest/ > > b) Copied in the intel test results to their own directory: > > https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults-intel/ > > c) Manually generated an updated test report for the combined results > with the commands: > > $ cd /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto- > 2.5.3 > $resulttool report . > testreport.txt > > d) Added a header to the report which consisted of the report from QA > with details of the bugs etc. > > This means we have a top level testreport file which contains all the > test information about the release. > > I'd like to make this the standard procedure for release. The release > notes and announcement can refer to the test report included with the > release and the test results as its there all together. > > Ultimately I'd like to improve the formatting of the report (separate > out ptest regressions from the other regressions, maybe html, maybe > graphs, better regression information) but that is something for the > future. > > Does that work for everyone? This works for me. - armin > > Cheers, > > Richard > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [OE-core] Yocto Project Status WW17'19
Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA) Next Deadline: YP 2.7 Release Target April 26, 2019 SWAT Team Rotation: SWAT lead is currently: ArminSWAT team rotation: Armin -> Anuj on Apr. 26, 2019SWAT team rotation: Armin -> Paul on May. 3, 2019 https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Next Team Meetings: Bug Triage meeting Thursday April 25th at 7:30am PDT ( https://zoom.us/j/454367603)YP 2.8 Planning meeting Tuesday May 7th at 8am PDT (https://zoom.us/j/990892712) Key Status/Updates: Stephen is going to be unavailable for several weeks, please refer any queries to RichardYP 2.6.2 was released!YP 2.5.3 is likely to be released imminentlyYP 2.7 rc2 (warrior) is currently going through QA.The final two members of the new YP TSC were elected, Denys and Armin. The TSC will therefore now start to discuss how its going to establish itself and operate.Huge thanks to Joshua Watt for diving in and helping file some ptest bugs and helping sort some missing tweaks with resulttool, it was just appreciatedPatches are continuing to flow into master, slightly impeded by holidays/vacation in some parts of the world.WDD, our bug tracking metric is sharply rising as there are few people helping with bugs.The 2.8 planning discussions are starting and there is a google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/If people are planning to work on specific things in 2.8 please let us know so we can incorporate this into our plans. If you’re interested in working on anything in the document, please also let us know or talk with us in one of the planning meetings. Planned Releases for YP 2.7: YP 2.7 M4 Cutoff was Apr. 1, 2019YP 2.7 M4 Release Target is Apr. 26, 2019 Planned upcoming dot releases: YP 2.5.3 (Sumo) is due for release. Tracking Metrics: WDD 2598 (last week 2523) ( https://wiki.yoctoproject.org/charts/combo.html)Poky Patch Metrics Total patches found: 1553 (last week 1553)Patches in the Pending State: 654 (42%) [last week 654 (42%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA cycle report for 2.5.3 RC3
On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: > > QA cycle report for 2.5.3 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results, refer to attachment [2]. > ·For test report for test cases run by Intel and WR team, > refer attachment [3] > ·For full test report, refer attachment [4] > ·For ptest results, please refer to results at public AB [5] > ·For ptest report, refer to attachment [6] > No new defects are found in this cycle. > Number of existing issues observed in this release is 2- toaster [7] > and Build-appliance [8] > For ptest, regression data is not available for this release. No > timeout issues. > Test result report on Public AB shows no failures. I've been discussing with Tracy and Vineela how to best handle the test results for the release for 2.5.3. In the end I: a) Copied in the ptest results to the right place. This will happen automagically in all future builds: https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults/qemux86-64-ptest/ b) Copied in the intel test results to their own directory: https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults-intel/ c) Manually generated an updated test report for the combined results with the commands: $ cd /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto- 2.5.3 $resulttool report . > testreport.txt d) Added a header to the report which consisted of the report from QA with details of the bugs etc. This means we have a top level testreport file which contains all the test information about the release. I'd like to make this the standard procedure for release. The release notes and announcement can refer to the test report included with the release and the test results as its there all together. Ultimately I'd like to improve the formatting of the report (separate out ptest regressions from the other regressions, maybe html, maybe graphs, better regression information) but that is something for the future. Does that work for everyone? Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA cycle report for 2.5.3 RC3
On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: > > QA cycle report for 2.5.3 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results, refer to attachment [2]. > ·For test report for test cases run by Intel and WR team, > refer attachment [3] > ·For full test report, refer attachment [4] > ·For ptest results, please refer to results at public AB [5] > ·For ptest report, refer to attachment [6] > No new defects are found in this cycle. > Number of existing issues observed in this release is 2- toaster [7] > and Build-appliance [8] > For ptest, regression data is not available for this release. No > timeout issues. > Test result report on Public AB shows no failures. I've been discussing with Tracy and Vineela how to best handle the test results for the release for 2.5.3. In the end I: a) Copied in the ptest results to the right place. This will happen automagically in all future builds: https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults/qemux86-64-ptest/ b) Copied in the intel test results to their own directory: https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults-intel/ c) Manually generated an updated test report for the combined results with the commands: $ cd /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.5.3 $resulttool report . > testreport.txt d) Added a header to the report which consisted of the report from QA with details of the bugs etc. This means we have a top level testreport file which contains all the test information about the release. I'd like to make this the standard procedure for release. The release notes and announcement can refer to the test report included with the release and the test results as its there all together. Ultimately I'd like to improve the formatting of the report (separate out ptest regressions from the other regressions, maybe html, maybe graphs, better regression information) but that is something for the future. Does that work for everyone? Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 10/10] conf: use rockchip kernel 4.4 for firefly release
From: ayaka Signed-off-by: ayaka --- conf/machine/firefly-rk3288.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/firefly-rk3288.conf b/conf/machine/firefly-rk3288.conf index 0fbac06..46a596b 100644 --- a/conf/machine/firefly-rk3288.conf +++ b/conf/machine/firefly-rk3288.conf @@ -8,5 +8,7 @@ require conf/machine/include/rk3288.inc +PREFERRED_PROVIDER_virtual/kernel = "linux-rockchip" + KERNEL_DEVICETREE = "rk3288-firefly.dtb" UBOOT_MACHINE = "firefly-rk3288_defconfig" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 09/10] conf/machine: rk3288: adding some machine files
Evb-rk3288 is the offical evaluate board. Fennec-rk3288 is a rk3288 based SBCs. Signed-off-by: Randy 'ayaka' Li --- conf/machine/evb-rk3288.conf| 10 ++ conf/machine/fennec-rk3288.conf | 10 ++ 2 files changed, 20 insertions(+) create mode 100644 conf/machine/evb-rk3288.conf create mode 100644 conf/machine/fennec-rk3288.conf diff --git a/conf/machine/evb-rk3288.conf b/conf/machine/evb-rk3288.conf new file mode 100644 index 000..e6c1f1e --- /dev/null +++ b/conf/machine/evb-rk3288.conf @@ -0,0 +1,10 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: EVB 3288 + +include conf/machine/include/rk3288.inc + +KERNEL_DEVICETREE = "rk3288-evb-act8846.dtb" +UBOOT_MACHINE = "evb-rk3288_defconfig" diff --git a/conf/machine/fennec-rk3288.conf b/conf/machine/fennec-rk3288.conf new file mode 100644 index 000..23e3ee7 --- /dev/null +++ b/conf/machine/fennec-rk3288.conf @@ -0,0 +1,10 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: FENNEC RK3288 + +include conf/machine/include/rk3288.inc + +KERNEL_DEVICETREE = "rk3288-fennec.dtb" +UBOOT_MACHINE = "fennec-rk3288_defconfig" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 08/10] conf/machine: add support for rk3308
RK3308 is a high-performance quad-core application processor designed for intelligent voice interaction. Signed-off-by: Randy 'ayaka' Li --- conf/machine/include/rk3308.inc | 17 + 1 file changed, 17 insertions(+) create mode 100644 conf/machine/include/rk3308.inc diff --git a/conf/machine/include/rk3308.inc b/conf/machine/include/rk3308.inc new file mode 100644 index 000..81e4def --- /dev/null +++ b/conf/machine/include/rk3308.inc @@ -0,0 +1,17 @@ +# Copyright (C) SUMOMO Computer Assocation +# Released under the MIT license (see COPYING.MIT for the terms) + +SOC_FAMILY = "rk3308" + +require conf/machine/include/tune-cortexa35.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" +KERNEL_IMAGETYPE = "Image" +KBUILD_DEFCONFIG = "defconfig" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 07/10] conf/machine: add support for rk3368
RK3368 is integrated with a qual-core Cortex-A53 processor and separately NEON coprocessor. RK3368 supports H.264 decoder up to 4Kx2K@30fps, H.265 decoder by 4Kx2K@60fps. Signed-off-by: Randy 'ayaka' Li --- conf/machine/include/rk3368.inc | 17 + 1 file changed, 17 insertions(+) create mode 100644 conf/machine/include/rk3368.inc diff --git a/conf/machine/include/rk3368.inc b/conf/machine/include/rk3368.inc new file mode 100644 index 000..1738f74 --- /dev/null +++ b/conf/machine/include/rk3368.inc @@ -0,0 +1,17 @@ +# Copyright (C) 2019 SUMOMO Computer Assocation +# Released under the MIT license (see COPYING.MIT for the terms) + +SOC_FAMILY = "rk3368" + +require conf/machine/include/tune-cortexa53.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" +KERNEL_IMAGETYPE = "Image" +KBUILD_DEFCONFIG = "defconfig" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 06/10] conf/machine: add support for rk3326
RK3326 is a high-performance quad-core application processor, it supports both H.264 and H.265 decoding up to 1920x1080@30fps. Signed-off-by: Randy 'ayaka' Li --- conf/machine/include/rk3326.inc | 18 ++ 1 file changed, 18 insertions(+) create mode 100644 conf/machine/include/rk3326.inc diff --git a/conf/machine/include/rk3326.inc b/conf/machine/include/rk3326.inc new file mode 100644 index 000..1208b65 --- /dev/null +++ b/conf/machine/include/rk3326.inc @@ -0,0 +1,18 @@ +# Copyright (C) 2019 SUMOMO Computer Association +# Released under the MIT license (see COPYING.MIT for the terms) + +# PX30 is the same SoC as rk3326. +SOC_FAMILY = "rk3326" + +require conf/machine/include/tune-cortexa35.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" +KERNEL_IMAGETYPE = "Image" +KBUILD_DEFCONFIG = "defconfig" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 04/10] conf/machine: add support for rk3036
RK3036 is a SoC from Rockchip which has Dual-Core ARM Cortex-A7 CPU, for low-end OTT TV Box. Supporting video acceleration for the HEVC and AVC up to 1080P video. With a HDMI sink. Signed-off-by: Randy 'ayaka' Li Signed-off-by: Randy Li --- conf/machine/include/rk3036.inc | 16 conf/machine/kylin-rk3036.conf | 12 2 files changed, 28 insertions(+) create mode 100644 conf/machine/include/rk3036.inc create mode 100644 conf/machine/kylin-rk3036.conf diff --git a/conf/machine/include/rk3036.inc b/conf/machine/include/rk3036.inc new file mode 100644 index 000..196f5a3 --- /dev/null +++ b/conf/machine/include/rk3036.inc @@ -0,0 +1,16 @@ +# Copyright (C) 2018 Randy 'ayaka' Li +# Released under the MIT license (see COPYING.MIT for the terms) + +SOC_FAMILY = "rk3036" + +require conf/machine/include/tune-cortexa7.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "115200;ttyS2" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" +SPL_BINARY ?= "u-boot-spl-nodtb.bin" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" diff --git a/conf/machine/kylin-rk3036.conf b/conf/machine/kylin-rk3036.conf new file mode 100644 index 000..e47a3be --- /dev/null +++ b/conf/machine/kylin-rk3036.conf @@ -0,0 +1,12 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: Kylin rk3036 + +include conf/machine/include/rk3036.inc + +KERNEL_DEVICETREE = "rk3036-kylin.dtb" +UBOOT_MACHINE = "kylin-rk3036_defconfig" + +GPTIMG_APPEND = "console=ttyS2,115200n8 rw root=PARTUUID=69DAD710-2CE4 rootfstype=ext4 init=/sbin/init" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 05/10] conf/machine: add support for rk312x
RK312X are a serial called RK audio. All of them sharing the simliar hardware configure. A quad-core ARM Cortex-A7 processor with separately Neon and FPU coprocessor, they also share a 256KB L2 Cache. All chips in this serial have a Mali 400 MP2 GPU. Signed-off-by: Randy 'ayaka' Li --- conf/machine/include/rk312x.inc | 17 + 1 file changed, 17 insertions(+) create mode 100644 conf/machine/include/rk312x.inc diff --git a/conf/machine/include/rk312x.inc b/conf/machine/include/rk312x.inc new file mode 100644 index 000..675c699 --- /dev/null +++ b/conf/machine/include/rk312x.inc @@ -0,0 +1,17 @@ +# Copyright (C) 2019 SUMOMO Computer Assocation +# Released under the MIT license (see COPYING.MIT for the terms) + +# a serial of chips +SOC_FAMILY = "rk312x" + +require conf/machine/include/tune-cortexa7.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "115200;ttyS2" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" +SPL_BINARY ?= "u-boot-spl-nodtb.bin" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 03/10] conf/machine: add support for rv1108
RV1108 is a SoC specific for video enhanced and recording. It is embedded with a DSP for digital process and an ARM Cortex-A7 single core processor for system and application. Signed-off-by: Randy 'ayaka' Li --- conf/machine/evb-rv1108.conf| 10 ++ conf/machine/include/rv1108.inc | 16 2 files changed, 26 insertions(+) create mode 100644 conf/machine/evb-rv1108.conf create mode 100644 conf/machine/include/rv1108.inc diff --git a/conf/machine/evb-rv1108.conf b/conf/machine/evb-rv1108.conf new file mode 100644 index 000..3e85d80 --- /dev/null +++ b/conf/machine/evb-rv1108.conf @@ -0,0 +1,10 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: EVB rv1108 + +include conf/machine/include/rv1108.inc + +KERNEL_DEVICETREE = "rv1108-evb.dtb" +UBOOT_MACHINE = "evb-rk3288_defconfig" diff --git a/conf/machine/include/rv1108.inc b/conf/machine/include/rv1108.inc new file mode 100644 index 000..c1bb584 --- /dev/null +++ b/conf/machine/include/rv1108.inc @@ -0,0 +1,16 @@ +# Copyright (C) 2019 Randy 'ayaka' Li +# Released under the MIT license (see COPYING.MIT for the terms) + +SOC_FAMILY = "rv1108" + +require conf/machine/include/tune-cortexa7.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" +SPL_BINARY ?= "u-boot-spl-nodtb.bin" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 02/10] conf/machine: add support for rk3328
The RK3328 is a SoC with Quad-core Cortex-A53 for Smart OTT/IPTV. Signed-off-by: Randy 'ayaka' Li --- conf/machine/evb-rk3328.conf| 11 +++ conf/machine/include/rk3328.inc | 18 ++ 2 files changed, 29 insertions(+) create mode 100644 conf/machine/evb-rk3328.conf create mode 100644 conf/machine/include/rk3328.inc diff --git a/conf/machine/evb-rk3328.conf b/conf/machine/evb-rk3328.conf new file mode 100644 index 000..ae2c0f8 --- /dev/null +++ b/conf/machine/evb-rk3328.conf @@ -0,0 +1,11 @@ +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: EVB 3388 + +include conf/machine/include/rk3328.inc + +KERNEL_DEVICETREE = "rockchip/rk3328-evb.dtb" +UBOOT_MACHINE = "evb-rk3328_defconfig" + +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=B921B045-1DF0 rootfstype=ext4 init=/sbin/init" diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc new file mode 100644 index 000..de5c9f4 --- /dev/null +++ b/conf/machine/include/rk3328.inc @@ -0,0 +1,18 @@ +# Copyright (C) 2017 Randy Li +# Released under the MIT license (see COPYING.MIT for the terms) + +# RK3228H is the same SoC as rk3328. +SOC_FAMILY = "rk3328" + +require conf/machine/include/tune-cortexa53.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" +KERNEL_IMAGETYPE = "Image" +KBUILD_DEFCONFIG = "defconfig" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2 01/10] conf/machine: add support for rk3399
RK3399 is a new generation powerful SoC from Rockchip, which has Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU. Signed-off-by: Randy 'ayaka' Li --- conf/machine/excavator-rk3399.conf | 12 conf/machine/firefly-rk3399.conf | 14 ++ conf/machine/include/rk3399.inc| 17 + 3 files changed, 43 insertions(+) create mode 100644 conf/machine/excavator-rk3399.conf create mode 100644 conf/machine/firefly-rk3399.conf create mode 100644 conf/machine/include/rk3399.inc diff --git a/conf/machine/excavator-rk3399.conf b/conf/machine/excavator-rk3399.conf new file mode 100644 index 000..8506a50 --- /dev/null +++ b/conf/machine/excavator-rk3399.conf @@ -0,0 +1,12 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: EXCAVATOR 3399 + +include conf/machine/include/rk3399.inc + +KERNEL_DEVICETREE = "rockchip/rk3399-sapphire-excavator.dtb" +UBOOT_MACHINE = "evb-rk3399_defconfig" + +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=B921B045-1DF0 rootfstype=ext4 init=/sbin/init" diff --git a/conf/machine/firefly-rk3399.conf b/conf/machine/firefly-rk3399.conf new file mode 100644 index 000..4e35c3d --- /dev/null +++ b/conf/machine/firefly-rk3399.conf @@ -0,0 +1,14 @@ +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd +# Released under the MIT license (see COPYING.MIT for the terms) + +#@TYPE: Machine +#@NAME: Firefly RK3399 +#@DESCRIPTION: Firefly-RK3399 is a Six-Core 64-bit High-Performance Platform. +#http://www.t-firefly.com/en/ + +include conf/machine/include/rk3399.inc + +KERNEL_DEVICETREE = "rockchip/rk3399-firefly.dtb" +UBOOT_MACHINE = "evb-rk3399_defconfig" + +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=B921B045-1DF0 rootfstype=ext4 init=/sbin/init" diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc new file mode 100644 index 000..9237616 --- /dev/null +++ b/conf/machine/include/rk3399.inc @@ -0,0 +1,17 @@ +# Copyright (C) 2019 SUMOMO Computer Association +# Released under the MIT license (see COPYING.MIT for the terms) + +SOC_FAMILY = "rk3399" + +require conf/machine/include/tune-cortexa72.inc +require conf/machine/include/soc-family.inc +require conf/machine/include/rockchip-defaults.inc + +SERIAL_CONSOLES = "150;ttyS2" +KERNEL_IMAGETYPE = "Image" +KBUILD_DEFCONFIG = "defconfig" + +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" + +IMAGE_FSTYPES = "rockchip-gpt-img" +IMAGE_CLASSES = "rockchip-gpt-img" -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-rockchip] [PATCH v2 00/10] add new SoCs supports
Although the upstream kernel may work with the most of chips I sent in the previous time, but there would be broken clock tree there, making everyhing not work or perform badly. I am not sure about the status of u-boot master branch, usually u-boot-rockchip would work better if we don't use the SPL/TPL from u-boot but vendor. Especially for those ARMv8 platform. I also add some SoCs are not merged into upstream kernel yet, so I don't offer a machine files for them. Changelog: v2 Removing the settings applied for vendor kernel v2 Adding some SoCs which are supported by the upstream kernel Randy 'ayaka' Li (9): conf/machine: add support for rk3399 conf/machine: add support for rk3328 conf/machine: add support for rv1108 conf/machine: add support for rk3036 conf/machine: add support for rk312x conf/machine: add support for rk3326 conf/machine: add support for rk3368 conf/machine: add support for rk3308 conf/machine: rk3288: adding some machine files ayaka (1): conf: use rockchip kernel 4.4 for firefly release conf/machine/evb-rk3288.conf | 10 ++ conf/machine/evb-rk3328.conf | 11 +++ conf/machine/evb-rv1108.conf | 10 ++ conf/machine/excavator-rk3399.conf | 12 conf/machine/fennec-rk3288.conf| 10 ++ conf/machine/firefly-rk3288.conf | 2 ++ conf/machine/firefly-rk3399.conf | 14 ++ conf/machine/include/rk3036.inc| 16 conf/machine/include/rk312x.inc| 17 + conf/machine/include/rk3308.inc| 17 + conf/machine/include/rk3326.inc| 18 ++ conf/machine/include/rk3328.inc| 18 ++ conf/machine/include/rk3368.inc| 17 + conf/machine/include/rk3399.inc| 17 + conf/machine/include/rv1108.inc| 16 conf/machine/kylin-rk3036.conf | 12 16 files changed, 217 insertions(+) create mode 100644 conf/machine/evb-rk3288.conf create mode 100644 conf/machine/evb-rk3328.conf create mode 100644 conf/machine/evb-rv1108.conf create mode 100644 conf/machine/excavator-rk3399.conf create mode 100644 conf/machine/fennec-rk3288.conf create mode 100644 conf/machine/firefly-rk3399.conf create mode 100644 conf/machine/include/rk3036.inc create mode 100644 conf/machine/include/rk312x.inc create mode 100644 conf/machine/include/rk3308.inc create mode 100644 conf/machine/include/rk3326.inc create mode 100644 conf/machine/include/rk3328.inc create mode 100644 conf/machine/include/rk3368.inc create mode 100644 conf/machine/include/rk3399.inc create mode 100644 conf/machine/include/rv1108.inc create mode 100644 conf/machine/kylin-rk3036.conf -- 2.20.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove packages from Image coming because of RDEPENDS
On Tue, Apr 23, 2019 at 6:09 AM Priyanshu Sharma < ms.priyanshu.sha...@gmail.com> wrote: > Hi, > > How can we remove inclusion of any package which comes because some other > package RDPENDS on it? > > For example, rpcbind recipe RDEPENDS on shadow and libpam packages, > because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( even > though shadow and libpam are not added like this explicilty) , shadow and > libpam packages get packaged in Image rootfs. > This even includes any bin/sbin provided by shadow/libpam, even when they > are not needed in rootfs. > > Is there an optimum way to control inclusion of RDEPENDS packages? > You need to somehow change the RDEPENDS via one of the mechanisms like PACKAGECONFIG, or by splitting the packaging into smaller, more specific sub-packages, etc. If a package has a RDEPENDS on something else, you can't simply ignore it or filter it out .. whoever wrote the recipe is indicating that it is required at runtime. So if you are saying that it isn't required at runtime, you should be sending patches to the recipes (and using the mechanisms like I mention above) to explain why it really isn't a runtime dependency. Bruce > One way is to use ROOTFS_POST_PROCESS and remove specific files after > do_rootfs task is done. > But is there a way to remove entire package, instead of removing each file > ? > > Warm Regards, > Priyanshu Sharma > > -- > ___ > 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 - "Use the force Harry" - Gandalf, Star Trek II -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What is the right SRC_URI syntax for g...@bitbucket.org?
Thanks Eric, how did you set up SRCREV? I've got an error need to set
a valid SRCREV.
Thank you.
Kind regards,
- jupiter
On 4/23/19, Erik Hoogeveen wrote:
> Hi,
>
> This works for me. I've have setup ssh my identity for Bitbucket.
>
> I use this in my recipes:
>
> SRC_URI = "gitsm://g...@bitbucket.org// name>.git;protocol=ssh;branch=${BRANCH}"
>
> Cheers,
> Erik
> On 21 Apr 2019, 02:58 +0200, JH , wrote:
> Hi,
>
> Could someone kindly clarify what is the syntax to access git source
> from bitbucket.org? I tried following different patterns, nothing
> works:
>
> SRC_URI = "git://bitbucket.org// name>;protocol=http;branch=${BRANCH}"
>
> SRC_URI = "git://@bitbucket.org// name>.git;protocol=ssh";branch=${BRANCH}"
>
> Thank you.
>
> Kind regards,
>
> - jupiter
> On 4/20/19, JH wrote:
> Hi,
>
> Sorry for a new starter questions, I searched Internet, there are a
> few examples to set up:
>
> SRC_URI = "git://@bitbucket.org// name>.git;protocol=ssh";branch=${BRANCH}"
>
> Not only that does not work, I have set up the public key to access
> the git bitbucket repository:
>
> $ ssh -v g...@bitbucket.org
>
> The Yocto also complained SRCREV, following some blog to add the
> SRCREV = "${AUTOREV}" that not work either.
>
> Thank you.
>
> Kind regards,
>
> - jh
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyocto&data=02%7C01%7C%7C5e970c621c2e4a0f349108d6c5f47377%7C84df9e7fe9f640afb435%7C1%7C0%7C636914051024571809&sdata=Ck9czRr02QsCIpJKbRtJTmcOAgQMPg64v7km9%2FAv3Ik%3D&reserved=0
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to remove packages from Image coming because of RDEPENDS
On Tuesday, April 23, 2019 12:08 PM, Priyanshu Sharma wrote:
> How can we remove inclusion of any package which comes because some other
> package RDPENDS on it?
> For example, rpcbind recipe RDEPENDS on shadow and libpam packages,
> because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe (
> even though shadow and libpam are not added like this explicilty) , shadow
> and libpam packages get packaged in Image rootfs.
> This even includes any bin/sbin provided by shadow/libpam, even when they are
> not needed in rootfs.
> Is there an optimum way to control inclusion of RDEPENDS packages? One
> way is to use ROOTFS_POST_PROCESS and remove specific files after do_rootfs
> task is done.
> But is there a way to remove entire package, instead of removing each file ?
Typically I create .bbappend with following:
RDEPENDS_${PN}_remove = "libpam"
But be careful what dependencies you remove. Sometimes Yocto sets too wide list
of dependencies and in some configurations it is possible to remove them, but
sometimes you may break some things.
Best regards,
Lukasz Zemla
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [poky-container][PATCH] README.md: Add note about using git inside the container
Fixes bug 11385. Signed-off-by: Daniel Ammann --- README.md | 5 + 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index c5276fd..cf49da9 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,11 @@ host. The instructions will be slightly different depending on whether Linux, Windows or Mac is used. There are setup instructions for using **Windows/Mac** at https://github.com/crops/docker-win-mac-docs/wiki. When referring to **Windows/Mac** in the rest of the document, it is assumed the instructions at https://github.com/crops/docker-win-mac-docs/wiki were followed. +Note that the poky-container should *not* be used to obtain the meta-data, but +just to build it. This means that meta-data should be checked out using native +tools that run on the host and not with tools in container. The reason is that +the container has no dummy git user configured. + Running the container - Here a very simple but usable scenario for using the container is described. -- 2.11.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-rockchip] [PATCH 0/5] add new SoCs support
Sent from my iPad > On Apr 23, 2019, at 4:02 PM, Trevor Woerner wrote: > > Hi Randy, > >> On Sun 2019-04-21 @ 11:53:34 PM, Randy 'ayaka' Li wrote: >> After the FOSDEM, my patches for ARMv8 cortex tuning >> are finally merged. So I think it is complete the >> lose piece at meta-rockchip. >> >> Since the big-litte is not supported by OE now, >> I make all the chips' configure to use the big core >> tuning. >> >> Randy 'ayaka' Li (5): >> conf/machine: rk3288: Add some machine files >> conf/machine: add rk3399 support >> conf/machine: add support for rk3328 >> conf/machine: add support for rk3036 >> conf/machine: add support for rv1108 > > I don't get the impression any of these patches were created for > git.yoctoproject.org/meta-rockchip. Although they apply, none of them actually > work. Or if they were intended for git.yoctoproject.org/meta-rockchip, then it > doesn't look like they were intended for the master branch (which is the > assumption when no branch tags are mentioned). I am very sorry, it was based on a old version of meta-rockchip(two years ago) and I thought this project is not that active, when I pick up them from my repository(the one with GPU and VPU support) I didn’t meet any problem, so I thought it would work. I forgot the linux-rockchip is removed now I fix them soon. About the duplication configuration, as the bitbake doesn’t warn them so I didn’t notice this problem. I would sent out a new version later. > > For example, many of these new MACHINEs indicate the Linux kernel > to use is "linux-rockchip" or "linux". Neither of these exist in > git.yoctoproject.org/meta-rockchip (or openembedded-core), so building any of > the MACHINEs introduced in these patches that specify either of these kernels > will fail. > > git.yoctoproject.org/meta-rockchip is a community layer focused on providing > builds composed of upstream and open-source components (i.e. U-Boot from > git.denx.de/u-boot.git and the Linux kernel from kernel.org). Some BSP layers > (e.g. meta-freescale) are able to provide users with a switch so that builds > can be built either from vendor sources or upstream sources by setting one > parameter, but so far git.yoctoproject.org/meta-rockchip doesn't have this > functionality and my attempts to get this functionality integrated at a > higher level (i.e. instead of having every BSP layer implement this logic > independently) haven't met with success. > > Best regards, >Trevor -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to remove packages from Image coming because of RDEPENDS
Hi, How can we remove inclusion of any package which comes because some other package RDPENDS on it? For example, rpcbind recipe RDEPENDS on shadow and libpam packages, because of which if IMAGE_INSTALL+="rpcbind" is mentioned in recipe ( even though shadow and libpam are not added like this explicilty) , shadow and libpam packages get packaged in Image rootfs. This even includes any bin/sbin provided by shadow/libpam, even when they are not needed in rootfs. Is there an optimum way to control inclusion of RDEPENDS packages? One way is to use ROOTFS_POST_PROCESS and remove specific files after do_rootfs task is done. But is there a way to remove entire package, instead of removing each file ? Warm Regards, Priyanshu Sharma -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .pc files are not avilable at build time
Works for me. What is the actual error you're seeing? On Tue, 23 Apr 2019 at 10:17, Archana Polampalli wrote: > > Hi all, > > I am trying to build btrfs-tools recipes.it needs the ex2fs.pc > pkgconfig file.i have alredy installed e2fsprogs recipe it created the > ex2fs.pc in image directory.but btrfstools unable to take the pkgconfig > file. > > plese any help me how to provide ex2fs.pc file for build btrfs-tools > > Regards > Archana > The information contained in this e-mail message and in any > attachments/annexure/appendices is confidential to the > recipient and may contain privileged information. > If you are not the intended recipient, please notify the > sender and delete the message along with any > attachments/annexure/appendices. You should not disclose, > copy or otherwise use the information contained in the > message or any annexure. Any views expressed in this e-mail > are those of the individual sender except where the sender > specifically states them to be the views of > Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. > > Although this transmission and any attachments are believed to be > free of any virus or other defect that might affect any computer > system into which it is received and opened, it is the responsibility > of the recipient to ensure that it is virus free and no responsibility > is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or > damage arising in any way from its use. > -- > ___ > 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] config.guess: unable to guess system type
The problem is that config.guess, last modified 2009-09-18, has failed to recognize the operating system you are using. It is advised that you download the most up to date version of the config scripts from http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD and http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD You're trying to build a piece of software that was released on 2013-08-17 using a config.guess from 2009, both of which predate aarch64 being actually available. There's a perfectly good recipe for libsdl in oe-core, or if you insist on building it on-target then you can either follow the instructions or install the gnu-config package into your image and copy the config.* files from /usr/share/gnu-config/. Ross On Tue, 23 Apr 2019 at 10:22, Peter Balazovic wrote: > > I am trying to compile on my Yocto system from source the SDL > http://www.libsdl.org/release/SDL-1.2.15.tar.gz and by running ./configure I > got error to configure the build > > checking build system type... ./build-scripts/config.guess: unable to guess > system type > > This script, last modified 2009-09-18, has failed to recognize > the operating system you are using. It is advised that you > download the most up to date version of the config scripts from > > > http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD > and > > http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD > > If the version you run (./build-scripts/config.guess) is already up to date, > please > send the following data and any information you think might be > pertinent to in order to provide the needed > information to handle your system. > > config.guess timestamp = 2009-09-18 > uname -m = aarch64 > uname -r = 4.14.78-imx_4.14.78_1.0.0_ga+g66620c3 > uname -s = Linux > uname -v = #1 SMP PREEMPT Fri Feb 1 09:09:25 UTC 2019 > > /usr/bin/uname -p = > /bin/uname -X = > > hostinfo = > /bin/universe = > /usr/bin/arch -k = > /bin/arch = > /usr/bin/oslevel = > /usr/convex/getsysinfo = > > UNAME_MACHINE = aarch64 > UNAME_RELEASE = 4.14.78-imx_4.14.78_1.0.0_ga+g66620c3 > UNAME_SYSTEM = Linux > UNAME_VERSION = #1 SMP PREEMPT Fri Feb 1 09:09:25 UTC 2019 > configure: error: cannot guess build type; you must specify one > > What would be causing the problem? > Thanks. > -- > ___ > 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] Generate an SDK with both 32 and 64 bit versions of the glibc
Hi all, I'm trying to install a third parted developed tool (closed source) into my x86_64 SDK. Unfortunately it is composed by a mix of 32 and 64 bit binaries thus `bitbake myimage -c populate_sdk` fails with: Error: Problem: conflicting requests - nothing provides libpthread.so.0 needed by nativesdk-scw-2019-r0.x86_64_nativesdk I guess that libpthread.so.0 is the missing 32 bit variant of the glibc library. How can I make bitbake to install 32 bit version of the glibc alongside the above mentioned tool? Thanks in advance! Ciao, Alessio -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] .pc files are not avilable at build time
Hi all, I am trying to build btrfs-tools recipes.it needs the ex2fs.pc pkgconfig file.i have alredy installed e2fsprogs recipe it created the ex2fs.pc in image directory.but btrfstools unable to take the pkgconfig file. plese any help me how to provide ex2fs.pc file for build btrfs-tools Regards Archana The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any attachments/annexure/appendices. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or damage arising in any way from its use. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] config.guess: unable to guess system type
I am trying to compile on my Yocto system from source the SDL http://www.libsdl.org/release/SDL-1.2.15.tar.gz and by running ./configure I got error to configure the build checking build system type... ./build-scripts/config.guess: unable to guess system type This script, last modified 2009-09-18, has failed to recognize the operating system you are using. It is advised that you download the most up to date version of the config scripts from http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD and http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD If the version you run (./build-scripts/config.guess) is already up to date, please send the following data and any information you think might be pertinent to in order to provide the needed information to handle your system. config.guess timestamp = 2009-09-18 uname -m = aarch64 uname -r = 4.14.78-imx_4.14.78_1.0.0_ga+g66620c3 uname -s = Linux uname -v = #1 SMP PREEMPT Fri Feb 1 09:09:25 UTC 2019 /usr/bin/uname -p = /bin/uname -X = hostinfo = /bin/universe = /usr/bin/arch -k = /bin/arch = /usr/bin/oslevel = /usr/convex/getsysinfo = UNAME_MACHINE = aarch64 UNAME_RELEASE = 4.14.78-imx_4.14.78_1.0.0_ga+g66620c3 UNAME_SYSTEM = Linux UNAME_VERSION = #1 SMP PREEMPT Fri Feb 1 09:09:25 UTC 2019 configure: error: cannot guess build type; you must specify one What would be causing the problem? Thanks. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Static code analysis
Hi All, I didn't know where to put this else, so here I am. I've been working with YOCTO for quite a while on professional and personal projects. >From time to time I wished I had some static code analysis inside of the build >chain. Esp. when something quite obvious (like a badly written shell-script) flipped the whole build - For most of my professional work I've always used the fail-early principle, which often means dying at build time instead of dying in testing. Over at GitHub (https://github.com/priv-kweihmann/meta-sca) you can find my current implementation of static code analysis tools to be used in YOCTO. If you're interested please have a look at it, and maybe if you like join the further development (or at least the discussion). Hope for some serious feedback, Best regards K. Weihmann -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] QA notification for completed autobuilder build (yocto-2.7.rc2)
A build flagged for QA (yocto-2.7.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2 Build hash information: bitbake: cb185efe9e88cfb12b7a3fd08f3086ca0b69c8e2 meta-gplv2: 106ba6d2a4d08a276205c305f8485d701fe8a8f3 meta-intel: cd2c3bfca97655999cbde645b73be712675dba92 meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4 oecore: f571b188177788d8ed0a7f3efe3569f153b1b0d3 poky: 0e392026ffefee098a890c39bc3ca1f697bacb52 This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/5] conf/machine: rk3288: Add some machine files
On Sun 2019-04-21 @ 11:53:35 PM, Randy 'ayaka' Li wrote: > Evb-rk3288 is the offical evaluate board. > Fennec-rk3288 and Tinker-rk3288 is rk3288 based SBCs. > Tinker Boards is a RPi compatible board made by ASUS. I would rather these were separated out as individual commits. meta-rockchip already has working support for the tinker-rk3288 board, so it's not being added here. > > Signed-off-by: Jacob Chen > Signed-off-by: Randy 'ayaka' Li > --- > conf/machine/evb-rk3288.conf| 10 ++ > conf/machine/fennec-rk3288.conf | 10 ++ > conf/machine/include/rk3288.inc | 5 + > conf/machine/tinker-rk3288.conf | 2 ++ > 4 files changed, 27 insertions(+) > create mode 100644 conf/machine/evb-rk3288.conf > create mode 100644 conf/machine/fennec-rk3288.conf > > diff --git a/conf/machine/evb-rk3288.conf b/conf/machine/evb-rk3288.conf > new file mode 100644 > index 000..e6c1f1e > --- /dev/null > +++ b/conf/machine/evb-rk3288.conf > @@ -0,0 +1,10 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: EVB 3288 > + > +include conf/machine/include/rk3288.inc > + > +KERNEL_DEVICETREE = "rk3288-evb-act8846.dtb" > +UBOOT_MACHINE = "evb-rk3288_defconfig" > diff --git a/conf/machine/fennec-rk3288.conf b/conf/machine/fennec-rk3288.conf > new file mode 100644 > index 000..23e3ee7 > --- /dev/null > +++ b/conf/machine/fennec-rk3288.conf > @@ -0,0 +1,10 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: FENNEC RK3288 > + > +include conf/machine/include/rk3288.inc > + > +KERNEL_DEVICETREE = "rk3288-fennec.dtb" > +UBOOT_MACHINE = "fennec-rk3288_defconfig" > diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc > index 0528e8a..73b39fb 100644 > --- a/conf/machine/include/rk3288.inc > +++ b/conf/machine/include/rk3288.inc > @@ -8,9 +8,14 @@ require conf/machine/include/soc-family.inc > require conf/machine/include/rockchip-defaults.inc > > SERIAL_CONSOLES = "115200;ttyS2" > +SPL_BINARY = "u-boot-spl-dtb.bin" You've put a U-Boot variable in the middle of a Linux block. This variable is already defined in this file just a couple lines down (in the U-Boot section) and uses a ?= to set it to the exact same thing you're setting it to. > +KERNEL_IMAGETYPE = "zImage" > +KBUILD_DEFCONFIG = "multi_v7_defconfig" These two things are defined exactly the same in conf/machine/include/rockchip-defaults.inc, which is already included above with the "require ..." line. > > PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot" > SPL_BINARY ?= "u-boot-spl-dtb.bin" > > IMAGE_FSTYPES = "rockchip-gpt-img" > IMAGE_CLASSES += "rockchip-gpt-img" > + > +APPEND = "console=ttyS2,115200n8 rw root=/dev/mmcblk2p7 rootfstype=ext4 > init=/sbin/init" I'm guessing this was supposed to be 'GPTIMG_APPEND = "..."'? In any case, I'm curious why you're switching from mmcblk0 to mmcblk2 here, classes/rockchip-gpt-img.bbclass already contains this logic. > diff --git a/conf/machine/tinker-rk3288.conf b/conf/machine/tinker-rk3288.conf > index 294bdc7..cf793cd 100644 > --- a/conf/machine/tinker-rk3288.conf > +++ b/conf/machine/tinker-rk3288.conf > @@ -9,3 +9,5 @@ require conf/machine/include/rk3288.inc > > KERNEL_DEVICETREE = "rk3288-tinker.dtb" > UBOOT_MACHINE = "tinker-rk3288_defconfig" > + > +GPTIMG_APPEND = "console=tty1 console=ttyS2,115200n8 rw root=/dev/mmcblk0p7 > rootfstype=ext4 init=/sbin/init" > -- > 2.20.1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 3/5] conf/machine: add support for rk3328
On Sun 2019-04-21 @ 11:53:37 PM, Randy 'ayaka' Li wrote: > The RK3328 is a SoC with Quad-core Cortex-A53 for Smart OTT/IPTV. > > Signed-off-by: Randy 'ayaka' Li > --- > conf/machine/evb-rk3328.conf| 12 > conf/machine/include/rk3328.inc | 18 ++ > 2 files changed, 30 insertions(+) > create mode 100644 conf/machine/evb-rk3328.conf > create mode 100644 conf/machine/include/rk3328.inc > > diff --git a/conf/machine/evb-rk3328.conf b/conf/machine/evb-rk3328.conf > new file mode 100644 > index 000..67d2083 > --- /dev/null > +++ b/conf/machine/evb-rk3328.conf > @@ -0,0 +1,12 @@ > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: EVB 3388 > + > +include conf/machine/include/rk3328.inc > + > +KERNEL_DEVICETREE = "rockchip/rk3328-evb.dtb" > +UBOOT_MACHINE = "evb-rk3328_defconfig" > + > +PREFERRED_PROVIDER_virtual/kernel = "linux-rockchip" There is no "linux-rockchip" > +GPTIMG_APPEND = "console=ttyS20,150n8 rw root=/dev/mmcblk2p5 > rootfstype=ext4 init=/sbin/init" > diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc > new file mode 100644 > index 000..8dc018e > --- /dev/null > +++ b/conf/machine/include/rk3328.inc > @@ -0,0 +1,18 @@ > +# Copyright (C) 2017 Randy Li > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +# RK3228H is the same SoC as rk3328. > +SOC_FAMILY = "rk3328" > + > +require conf/machine/include/tune-cortexa53.inc > +require conf/machine/include/soc-family.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux" This conflicts with what you've just specified above. In any case, neither "linux" nor "linux-rockchip" exist. > +SERIAL_CONSOLES = "150;ttyS2" > +KERNEL_IMAGETYPE = "Image" > +KBUILD_DEFCONFIG = "multi_v8_defconfig" > + > +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" > + > +IMAGE_FSTYPES = "rockchip-gpt-img" > +IMAGE_CLASSES = "rockchip-gpt-img" > -- > 2.20.1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 4/5] conf/machine: add support for rk3036
On Sun 2019-04-21 @ 11:53:38 PM, Randy 'ayaka' Li wrote: > RK3036 is a SoC from Rockchip which has Dual-Core > ARM Cortex-A7 CPU, for low-end OTT TV Box. > > Supporting video acceleration for the HEVC and AVC > up to 1080P video. With a HDMI sink. > > Signed-off-by: Randy 'ayaka' Li > Signed-off-by: Randy Li > --- > conf/machine/include/rk3036.inc | 19 +++ > conf/machine/kylin-rk3036.conf | 12 > 2 files changed, 31 insertions(+) > create mode 100644 conf/machine/include/rk3036.inc > create mode 100644 conf/machine/kylin-rk3036.conf > > diff --git a/conf/machine/include/rk3036.inc b/conf/machine/include/rk3036.inc > new file mode 100644 > index 000..5a9c55e > --- /dev/null > +++ b/conf/machine/include/rk3036.inc > @@ -0,0 +1,19 @@ > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +SOC_FAMILY = "rk3036" > + > +require conf/machine/include/tune-cortexa7.inc > +require conf/machine/include/soc-family.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux" > +SERIAL_CONSOLES = "115200;ttyS2" > +KERNEL_IMAGETYPE = "zImage" > +KBUILD_DEFCONFIG = "multi_v7_defconfig" > + > +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" > +SPL_BINARY ?= "u-boot-spl-nodtb.bin" > + > +IMAGE_FSTYPES = "rockchip-gpt-img" > +IMAGE_CLASSES = "rockchip-gpt-img" > + > +GPTIMG_APPEND = "console=ttyS2,115200n8 rw root=/dev/mmcblk1p7 > rootfstype=ext4 init=/sbin/init rootwait" > diff --git a/conf/machine/kylin-rk3036.conf b/conf/machine/kylin-rk3036.conf > new file mode 100644 > index 000..9e42e87 > --- /dev/null > +++ b/conf/machine/kylin-rk3036.conf > @@ -0,0 +1,12 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: Kylin rk3036 > + > +include conf/machine/include/rk3036.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux-rockchip" There is no "linux-rockchip", maybe you meant "linux-stable"? > + > +KERNEL_DEVICETREE = "rk3036-kylin.dtb" > +UBOOT_MACHINE = "kylin-rk3036_defconfig" > -- > 2.20.1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 5/5] conf/machine: add support for rv1108
On Sun 2019-04-21 @ 11:53:39 PM, Randy 'ayaka' Li wrote: > RV1108 is a SoC specific for video enhanced and > recording. It is embedded with a DSP for digital > process and an ARM Cortex-A7 single core processor > for system and application. > > Signed-off-by: Randy 'ayaka' Li > --- > conf/machine/evb-rv1108.conf| 10 ++ > conf/machine/include/rv1108.inc | 12 > 2 files changed, 22 insertions(+) > create mode 100644 conf/machine/evb-rv1108.conf > create mode 100644 conf/machine/include/rv1108.inc > > diff --git a/conf/machine/evb-rv1108.conf b/conf/machine/evb-rv1108.conf > new file mode 100644 > index 000..3e85d80 > --- /dev/null > +++ b/conf/machine/evb-rv1108.conf > @@ -0,0 +1,10 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: EVB rv1108 > + > +include conf/machine/include/rv1108.inc > + > +KERNEL_DEVICETREE = "rv1108-evb.dtb" > +UBOOT_MACHINE = "evb-rk3288_defconfig" > diff --git a/conf/machine/include/rv1108.inc b/conf/machine/include/rv1108.inc > new file mode 100644 > index 000..1c70ef7 > --- /dev/null > +++ b/conf/machine/include/rv1108.inc > @@ -0,0 +1,12 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +SOC_FAMILY = "rv1108" > + > +require conf/machine/include/tune-cortexa7.inc > +require conf/machine/include/soc-family.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux" There is no "linux", maybe you meant "linux-stable"? > +SERIAL_CONSOLES = "150;ttyS2" > +KERNEL_IMAGETYPE = "zImage" > +KBUILD_DEFCONFIG = "multi_v7_defconfig" > -- > 2.20.1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/5] conf/machine: add rk3399 support
On Sun 2019-04-21 @ 11:53:36 PM, Randy 'ayaka' Li wrote: > RK3399 is a new generation powerful SoC from Rockchip, which has > Dual Cortex-A72 + Quad Cortex-A53, 64-bit CPU. > > Signed-off-by: Randy 'ayaka' Li > --- > conf/machine/excavator-rk3399.conf | 10 ++ > conf/machine/firefly-rk3399.conf | 15 +++ > conf/machine/include/rk3399.inc| 17 + > 3 files changed, 42 insertions(+) > create mode 100644 conf/machine/excavator-rk3399.conf > create mode 100644 conf/machine/firefly-rk3399.conf > create mode 100644 conf/machine/include/rk3399.inc > > diff --git a/conf/machine/excavator-rk3399.conf > b/conf/machine/excavator-rk3399.conf > new file mode 100644 > index 000..c7134d2 > --- /dev/null > +++ b/conf/machine/excavator-rk3399.conf > @@ -0,0 +1,10 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: EXCAVATOR 3399 > + > +include conf/machine/include/rk3399.inc > + > +KERNEL_DEVICETREE = "rk3399-sapphire-excavator-linux.dtb" > +UBOOT_MACHINE = "evb-rk3399_defconfig" > diff --git a/conf/machine/firefly-rk3399.conf > b/conf/machine/firefly-rk3399.conf > new file mode 100644 > index 000..fefafed > --- /dev/null > +++ b/conf/machine/firefly-rk3399.conf > @@ -0,0 +1,15 @@ > +# Copyright (C) 2017 Fuzhou Rockchip Electronics Co., Ltd > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +#@TYPE: Machine > +#@NAME: Firefly RK3399 > +#@DESCRIPTION: Firefly-RK3399 is a Six-Core 64-bit High-Performance Platform. > +#http://www.t-firefly.com/en/ > + > +include conf/machine/include/rk3399.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux-rockchip" linux-rockchip doesn't exist in git.yoctoproject.org/meta-rockchip. Has support for this MACHINE been added upstream (i.e. kernel.org)? > +KERNEL_DEVICETREE = "rockchip/rk3399-firefly-linux.dtb" > +UBOOT_MACHINE = "evb-rk3399_defconfig" > + > +GPTIMG_APPEND = "console=ttyS2,150n8 rw root=PARTUUID=614e- > rootfstype=ext4 init=/sbin/init" > diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc > new file mode 100644 > index 000..6e2af57 > --- /dev/null > +++ b/conf/machine/include/rk3399.inc > @@ -0,0 +1,17 @@ > +# Copyright (C) 2019 SUMOMO Computer Association > +# Released under the MIT license (see COPYING.MIT for the terms) > + > +SOC_FAMILY = "rk3399" > + > +require conf/machine/include/tune-cortexa72.inc > +require conf/machine/include/soc-family.inc > + > +PREFERRED_PROVIDER_virtual/kernel = "linux" This setting conflicts with what you set in firefly-rk3399.conf above. Ideally include files should probably use a weaker assignment? In any case, there is no "linux" kernel defined, maybe you want "linux-stable" instead? > +SERIAL_CONSOLES = "150;ttyS2" > +KERNEL_IMAGETYPE = "Image" > +#KBUILD_DEFCONFIG = "multi_v8_defconfig" > + > +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-rockchip" vendor-u-boot? Does upstream U-Boot support these MACHINEs? > + > +IMAGE_FSTYPES = "rockchip-gpt-img" > +IMAGE_CLASSES = "rockchip-gpt-img" > -- > 2.20.1 > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-rockchip] [PATCH 0/5] add new SoCs support
Hi Randy, On Sun 2019-04-21 @ 11:53:34 PM, Randy 'ayaka' Li wrote: > After the FOSDEM, my patches for ARMv8 cortex tuning > are finally merged. So I think it is complete the > lose piece at meta-rockchip. > > Since the big-litte is not supported by OE now, > I make all the chips' configure to use the big core > tuning. > > Randy 'ayaka' Li (5): > conf/machine: rk3288: Add some machine files > conf/machine: add rk3399 support > conf/machine: add support for rk3328 > conf/machine: add support for rk3036 > conf/machine: add support for rv1108 I don't get the impression any of these patches were created for git.yoctoproject.org/meta-rockchip. Although they apply, none of them actually work. Or if they were intended for git.yoctoproject.org/meta-rockchip, then it doesn't look like they were intended for the master branch (which is the assumption when no branch tags are mentioned). For example, many of these new MACHINEs indicate the Linux kernel to use is "linux-rockchip" or "linux". Neither of these exist in git.yoctoproject.org/meta-rockchip (or openembedded-core), so building any of the MACHINEs introduced in these patches that specify either of these kernels will fail. git.yoctoproject.org/meta-rockchip is a community layer focused on providing builds composed of upstream and open-source components (i.e. U-Boot from git.denx.de/u-boot.git and the Linux kernel from kernel.org). Some BSP layers (e.g. meta-freescale) are able to provide users with a switch so that builds can be built either from vendor sources or upstream sources by setting one parameter, but so far git.yoctoproject.org/meta-rockchip doesn't have this functionality and my attempts to get this functionality integrated at a higher level (i.e. instead of having every BSP layer implement this logic independently) haven't met with success. Best regards, Trevor -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
