Re: [yocto] Is there a recipe for evtest package?
On Wed, Jan 25, 2012 at 7:36 AM, Brian Hutchinson wrote: > On Wed, Jan 25, 2012 at 9:48 AM, Jack Mitchell > wrote: >> Hi Brian, >> >> Your best bet is to adapt the one from meta-oe here: >> >> http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/evtest > > Hi Jack, > > I'm still trying to get up-to-speed on how to work with Yocto > would adding this layer be just like adding say poky extras? Yes, although other issues can present itself. If you start using meta-oe you need to make sure you pick one that is compatible with your oe-core layer. -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] understanding recipes
On Fri, Jan 27, 2012 at 10:43 AM, Joshua Lock wrote: > On 26/01/12 14:11, Scott Garman wrote: >> >> In this case, the LIC_FILES_CHKSUM is storing the md5sum of the COPYING >> file, which is stored in the top-level directory of the extracted sources. >> >> So manually download the hello version you are trying to use, extract >> the tarball locally, and run md5sum against the COPYING file. Then >> update the LIC_FILES_CHKSUM field with that new md5 checksum. > > > Or if you're lazy, like me, you can just run the build and let it fail then > run md5sum on the extracted source in the work directory. > > i.e. for qemux86 hello world I could bitbake helloworld then: > > md5sum tmp/work/i586-poky-linux/hello-world-2.7-r0/hello-world-2.7/COPYING I think it even tells you what it should be, so you don't even need to do this step. Just set the right file and the correct lines within the file and run until failure. -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1][KERNEL] meta/crownbay: use new yocto/emgd-1.10 feature branch
On 12-01-02 02:31 PM, tom.zanu...@intel.com wrote: From: Tom Zanussi This patchset makes crownbay use the new yocto/emgd-1.10 feature branch. Bruce, please don't merge this yet though - it depends on the new emgd-1.10 recipe, which in turn depends on some new LICENSE_FLAGS functionality being merged. Will let you know when all that's taken care of and it's safe to pull this in. merged with the emgd changes. Build testing now. Bruce Thanks, Tom The following changes since commit c979f1365b1eb74e882b2cbbc8407ec536ab6eb8: Bruce Ashfield (1): meta/routstationpro: refresh for 3.0 + rt support are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/linux-yocto-3.0-meta/emgd-1.10.v0 http://git.yoctoproject.org/cgit.cgi//log/?h=tzanussi/linux-yocto-3.0-meta/emgd-1.10.v0 Tom Zanussi (1): crownbay: use emgd-1.10 meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] +Bill Mar - you should be able to register...
Jeff Osier-Mixon shared a post with you on Google+. Google+ makes sharing on the web more like sharing in real life. Learn more: http://www.google.com/+/learnmore/ You received this message because Jeff Osier-Mixon shared it with yocto@yoctoproject.org. "+Bill Mar - you should be able to register for the +Yocto Project Developer Day at ELC here, even if you are already registered for ABS: http://www.regonline.com/yoctoprojectdeveloperday"; Accept the invitation to view the full post: https://plus.google.com/_/notifications/ngemlink?&emid=CKCP_db-8K0CFcyE3godmVUAAA&path=%2F115685581526580635799%2Fposts%2FgSDsDvFQiKe%3Fgpinv%3DAMIXal_jlTJo0kwDbvjM22hIpW1KJFKpNngbj0IzlLf0by6R7CZGkm0fDuG7qmSm0z7AFEalfGnunRQF6aMcK3j77TC1Ziltj9YsiRXGckxiFXxsBjXMWwk%26hl%3Den&dt=1327694295815 You received this message because Jeff Osier-Mixon shared it with yocto@yoctoproject.org. Click here to unsubscribe from these emails: https://plus.google.com/_/notifications/ngemlink?&emid=CKCP_db-8K0CFcyE3godmVUAAA&path=%2F_%2Fnonplus%2Femailsettings%3Fgpinv%3DAMIXal_jlTJo0kwDbvjM22hIpW1KJFKpNngbj0IzlLf0by6R7CZGkm0fDuG7qmSm0z7AFEalfGnunRQF6aMcK3j77TC1Ziltj9YsiRXGckxiFXxsBjXMWwk%26est%3DADH5u8Vg7pQVDfbAEtYDVBccKHt7J9pUO288CcFMoc5X06KDDS-5yPDI1vyMLeIsdcJy9ybwAtDHDNW7aIAAmFEqOiaWQ211sazgx-cjqKIhUeXzhB0L-p55BRogCgL1CKGj2q5jBDyB3MyWV8V1oMZKv63tAOe98g%26hl%3Den&dt=1327694295815 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/2][KERNEL] new yocto/emgd-1.10 feature branch
On 12-01-02 02:31 PM, tom.zanu...@intel.com wrote: From: Tom Zanussi This patchset adds a new yocto/emgd-1.10 feature branch to linux-yocto-3.0, alongside the existing yocto/emgd branch containing emgd-1.8. Bruce, please don't merge this yet though - it depends on the new emgd-1.10 recipe, which in turn depends on some new LICENSE_FLAGS functionality being merged. Will let you know when all that's taken care of and it's safe to pull this in. These are merged in with my 3.0.18 update to the kernel. I'm doing build tests, and this will be available shortly. Bruce Thanks, Tom The following changes since commit 6b4bf6173b0bd2d1619a8218bac66ebc4681dd35: Maurice Ma (1): x86, efi: Convert efi_phys_get_time() args to physical addresses are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/linux-yocto-3.0-yocto/emgd-1.10.v0 http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/linux-yocto-3.0-yocto/emgd-1.10.v0 Tom Zanussi (2): yocto/emgd: emgd 1.10 driver yocto/emgd: initial build fixups drivers/gpu/drm/Kconfig|9 + drivers/gpu/drm/Makefile |1 + drivers/gpu/drm/emgd/Makefile | 294 + drivers/gpu/drm/emgd/emgd/cfg/config.h | 113 + drivers/gpu/drm/emgd/emgd/cfg/config_default.h | 198 + drivers/gpu/drm/emgd/emgd/cfg/config_helper.c | 244 + .../gpu/drm/emgd/emgd/core/init/cmn/igd_global.c | 34 + drivers/gpu/drm/emgd/emgd/core/init/cmn/igd_init.c | 918 +++ .../drm/emgd/emgd/core/init/cmn/init_dispatch.h| 65 + drivers/gpu/drm/emgd/emgd/core/init/plb/init_plb.c | 458 ++ .../drm/emgd/emgd/core/init/plb/micro_init_plb.c | 631 ++ drivers/gpu/drm/emgd/emgd/core/init/tnc/init_tnc.c | 621 ++ .../drm/emgd/emgd/core/init/tnc/micro_init_tnc.c | 992 +++ drivers/gpu/drm/emgd/emgd/display/dsp/cmn/dsp.c| 2368 +++ .../drm/emgd/emgd/display/dsp/cmn/dsp_dispatch.h | 64 + .../gpu/drm/emgd/emgd/display/dsp/plb/dsp_plb.c| 709 ++ .../gpu/drm/emgd/emgd/display/dsp/tnc/dsp_tnc.c| 542 ++ .../gpu/drm/emgd/emgd/display/mode/cmn/igd_mode.c | 2219 +++ drivers/gpu/drm/emgd/emgd/display/mode/cmn/match.c | 1347 drivers/gpu/drm/emgd/emgd/display/mode/cmn/match.h | 59 + .../drm/emgd/emgd/display/mode/cmn/micro_mode.c| 1744 + .../drm/emgd/emgd/display/mode/cmn/mode_dispatch.h | 383 ++ .../gpu/drm/emgd/emgd/display/mode/cmn/vga_mode.c | 1467 + .../drm/emgd/emgd/display/mode/plb/clocks_plb.c| 701 ++ .../drm/emgd/emgd/display/mode/plb/kms_mode_plb.c | 1102 .../emgd/emgd/display/mode/plb/micro_mode_plb.c| 1372 .../gpu/drm/emgd/emgd/display/mode/plb/mode_plb.c | 1932 ++ .../gpu/drm/emgd/emgd/display/mode/plb/mode_plb.h | 47 + .../drm/emgd/emgd/display/mode/tnc/clocks_tnc.c| 1180 .../drm/emgd/emgd/display/mode/tnc/kms_mode_tnc.c | 1721 + .../emgd/emgd/display/mode/tnc/micro_mode_tnc.c| 2643 .../gpu/drm/emgd/emgd/display/mode/tnc/mode_tnc.c | 1997 ++ .../gpu/drm/emgd/emgd/display/mode/tnc/mode_tnc.h | 52 + drivers/gpu/drm/emgd/emgd/display/pd/cmn/pd.c | 516 ++ .../gpu/drm/emgd/emgd/display/pi/cmn/displayid.c | 1058 +++ drivers/gpu/drm/emgd/emgd/display/pi/cmn/edid.c| 1187 .../drm/emgd/emgd/display/pi/cmn/i2c_dispatch.h| 78 + drivers/gpu/drm/emgd/emgd/display/pi/cmn/igd_pi.c | 260 + .../gpu/drm/emgd/emgd/display/pi/cmn/mode_table.c | 2545 .../gpu/drm/emgd/emgd/display/pi/cmn/pd_init_all.c | 215 + drivers/gpu/drm/emgd/emgd/display/pi/cmn/pi.c | 1883 ++ drivers/gpu/drm/emgd/emgd/display/pi/plb/i2c_plb.c | 940 +++ .../drm/emgd/emgd/display/pi/tnc/i2c_bitbash_tnc.c | 599 ++ .../drm/emgd/emgd/display/pi/tnc/i2c_gmbus_tnc.c | 929 +++ drivers/gpu/drm/emgd/emgd/drm/drm_emgd_private.h | 167 + drivers/gpu/drm/emgd/emgd/drm/emgd_connector.c | 512 ++ drivers/gpu/drm/emgd/emgd/drm/emgd_crtc.c | 1004 +++ drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c | 2399 +++ drivers/gpu/drm/emgd/emgd/drm/emgd_drv.h | 199 + drivers/gpu/drm/emgd/emgd/drm/emgd_encoder.c | 474 ++ drivers/gpu/drm/emgd/emgd/drm/emgd_fb.c| 1403 drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c | 801 +++ drivers/gpu/drm/emgd/emgd/drm/emgd_interface.c | 2583 drivers/gpu/drm/emgd/emgd/drm/emgd_mmap.c | 186 + drivers/gpu/drm/emgd/emgd/drm/emgd_test_pvrsrv.c | 1365 drivers/gpu/drm/emgd/emgd/drm/image_data.h | 33 + drivers/gpu/drm/emgd/emgd/drm/splash_screen.c | 2221 +++ drivers/gpu/drm/emgd/emgd/drm/splash_screen.h | 280 + drivers/gpu/drm/emgd/emgd/drm/user_config.c| 252 + drivers/gpu/drm/emgd/emgd/drm/user_config.h| 113 + drivers/gpu/drm/emgd/emgd/gmm/gmm.c
Re: [yocto] understanding recipes
On 26/01/12 14:11, Scott Garman wrote: In this case, the LIC_FILES_CHKSUM is storing the md5sum of the COPYING file, which is stored in the top-level directory of the extracted sources. So manually download the hello version you are trying to use, extract the tarball locally, and run md5sum against the COPYING file. Then update the LIC_FILES_CHKSUM field with that new md5 checksum. Or if you're lazy, like me, you can just run the build and let it fail then run md5sum on the extracted source in the work directory. i.e. for qemux86 hello world I could bitbake helloworld then: md5sum tmp/work/i586-poky-linux/hello-world-2.7-r0/hello-world-2.7/COPYING Cheers, Joshua -- Joshua Lock Yocto Project "Johannes factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] serial consoles
I have the meta-cedartrail image running on hardware (Marshalltown board). To make the serial console work, I have in the machine/cedartrail.conf file: SERIAL_CONSOLE = "115200 ttyS0" this works fine, but only after Linux is up and the login prompts are sent out. I'm trying to also get the Kernel boot console log out, and possibly syslinux or grub console. If I look at the release notes for the meta-n450, it has suggestions to do this for that BSP as below: # Serial Port Setup for Intel Embedded Development Board 1-N40 SYSLINUX_OPTS_atom-pc = "serial 0 115200" SERIAL_CONSOLE_atom-pc = "115200 ttyS0" APPEND_atom-pc = "console=ttyS0,115200 console=tty0" However, those notes talk about added these statements to the local.conf file. I have not been able to translate what works on the n450 to cedartrail. Any ideas? Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] mpc8315: build u-boot by default.
On 12-01-27 12:11 PM, Darren Hart wrote: > > > On 01/27/2012 08:22 AM, Paul Gortmaker wrote: >> Valdiated on v2011.12 with hardware: >> >> U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX >> >> Reset Status: Software Hard, External/Internal Soft, External/Internal >> Hard >> >> CPU: e300c3, MPC8315E, Rev: 1.2 at 400 MHz, CSB: 133.333 MHz >> Board: Freescale MPC8315ERDB Rev 1.0 >> I2C: ready >> DRAM: 128 MiB (DDR2, 32-bit, ECC off, 266.667 MHz) >> Flash: 8 MiB >> NAND: 32 MiB >> PCIE0: No link >> PCIE1: No link >> In:serial >> Out: serial >> Err: serial >> Net: eTSEC0, eTSEC1 >> Hit any key to stop autoboot: 0 >> => ver >> >> U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX >> powerpc-poky-linux-gcc (GCC) 4.6.3 2017 (prerelease) >> GNU ld (GNU Binutils) 2.22 >> => >> >> Signed-off-by: Paul Gortmaker > > Hi Paul, > > Have you verified that the u-boot image this creates functions properly > when flashed to the mpc8315? Last time I tried I bricked the board - and Was there a specific functional test that you had in mind? I ask that, since for a basic overall "does it work" type question, I think I covered that in the commit log above. Thanks, Paul. > still haven't got around to unbricking it. > > -- > Darren > >> >> diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf >> b/meta-yocto/conf/machine/mpc8315e-rdb.conf >> index d3a5b1c..74ef611 100644 >> --- a/meta-yocto/conf/machine/mpc8315e-rdb.conf >> +++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf >> @@ -7,6 +7,9 @@ require conf/machine/include/tune-ppc603e.inc >> >> KERNEL_IMAGETYPE = "uImage" >> >> +EXTRA_IMAGEDEPENDS += "u-boot" >> +UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" >> + >> SERIAL_CONSOLE = "115200 ttyS0" >> >> MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial" > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New recipes not installing in core-image-minimal
On 01/27/2012 02:30 AM, Martin Jansa wrote:
> On Fri, Jan 27, 2012 at 03:52:58PM +0530, Joshua Immanuel wrote:
>> Hello Martin,
>>
>> On Fri, 2012-01-27 at 09:08 +0100, Martin Jansa wrote:
Perhaps, but it didn't fix this particular problem. Neither
/usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs.
However, each still appears in their respective workdir/image:
>>>
>>> Are they in workdir/packages-split/genmac/etc/init.d/genmac
>>> workdir/packages-split/ranpwd/etc/init.d/ranpwd
>>
>> I too have a similar issue when I try to include a manually constructed
>> fstab file into the rootfs image. The file is available in the following
>> locations
>> 1. core2-poky-linux/${PN}-${PV}-${PR}/etc/fstab
>> 2. core2-poky-linux/${PN}-${PV}-${PR}/packages-split/${PN}/etc/fstab
>>
>> but not in the final rootfs image. May be I am missing something
>> trivial.
>
> Maybe it depends on used package-manager bud I guess that at least
> opkg will refuse to overwrite /etc/fstab provided by base-files by
> /etc/fstab from your fancy PN and even if it allows it in do_rootfs,
> then it's not good idea for image with online package management,
> because your custom fstab will be overwritten as soon as base-files are
> changed.
>
> Why not .bbappend base-files and customize fstab there?
This is how I am modifying /etc/network/interfaces and this is working
fine for me. Joshua, I'd second Martin's suggestion.
--
Darren
>
>> Eager to know the solution on this thread.
>>
>> Regards
>> Joshua
>> --
>> Joshua Immanuel
>> HiPro IT Solutions Private Limited
>> http://hipro.co.in
>
>
>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] mpc8315: build u-boot by default.
On 01/27/2012 08:22 AM, Paul Gortmaker wrote: > Valdiated on v2011.12 with hardware: > > U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX > > Reset Status: Software Hard, External/Internal Soft, External/Internal > Hard > > CPU: e300c3, MPC8315E, Rev: 1.2 at 400 MHz, CSB: 133.333 MHz > Board: Freescale MPC8315ERDB Rev 1.0 > I2C: ready > DRAM: 128 MiB (DDR2, 32-bit, ECC off, 266.667 MHz) > Flash: 8 MiB > NAND: 32 MiB > PCIE0: No link > PCIE1: No link > In:serial > Out: serial > Err: serial > Net: eTSEC0, eTSEC1 > Hit any key to stop autoboot: 0 > => ver > > U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX > powerpc-poky-linux-gcc (GCC) 4.6.3 2017 (prerelease) > GNU ld (GNU Binutils) 2.22 > => > > Signed-off-by: Paul Gortmaker Hi Paul, Have you verified that the u-boot image this creates functions properly when flashed to the mpc8315? Last time I tried I bricked the board - and still haven't got around to unbricking it. -- Darren > > diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf > b/meta-yocto/conf/machine/mpc8315e-rdb.conf > index d3a5b1c..74ef611 100644 > --- a/meta-yocto/conf/machine/mpc8315e-rdb.conf > +++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf > @@ -7,6 +7,9 @@ require conf/machine/include/tune-ppc603e.inc > > KERNEL_IMAGETYPE = "uImage" > > +EXTRA_IMAGEDEPENDS += "u-boot" > +UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" > + > SERIAL_CONSOLE = "115200 ttyS0" > > MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial" -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] mpc8315: build u-boot by default.
Valdiated on v2011.12 with hardware: U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX Reset Status: Software Hard, External/Internal Soft, External/Internal Hard CPU: e300c3, MPC8315E, Rev: 1.2 at 400 MHz, CSB: 133.333 MHz Board: Freescale MPC8315ERDB Rev 1.0 I2C: ready DRAM: 128 MiB (DDR2, 32-bit, ECC off, 266.667 MHz) Flash: 8 MiB NAND: 32 MiB PCIE0: No link PCIE1: No link In:serial Out: serial Err: serial Net: eTSEC0, eTSEC1 Hit any key to stop autoboot: 0 => ver U-Boot 2011.12 (Jan 26 2012 - 16:55:23)MPC83XX powerpc-poky-linux-gcc (GCC) 4.6.3 2017 (prerelease) GNU ld (GNU Binutils) 2.22 => Signed-off-by: Paul Gortmaker diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf index d3a5b1c..74ef611 100644 --- a/meta-yocto/conf/machine/mpc8315e-rdb.conf +++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf @@ -7,6 +7,9 @@ require conf/machine/include/tune-ppc603e.inc KERNEL_IMAGETYPE = "uImage" +EXTRA_IMAGEDEPENDS += "u-boot" +UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" + SERIAL_CONSOLE = "115200 ttyS0" MACHINE_FEATURES = "kernel26 keyboard pci ext2 ext3 serial" -- 1.7.7 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] new How Do I posted
Thanks Jim... I will check this out. Scott -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of jfabernathy Sent: Friday, January 27, 2012 4:46 AM To: yocto@yoctoproject.org Subject: [yocto] new How Do I posted I created a "How DO I" for adding recipes, and added it to the wiki. Please review for correctness if you like. Jim A ___ 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] new How Do I posted
I created a "How DO I" for adding recipes, and added it to the wiki. Please review for correctness if you like. Jim A ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New recipes not installing in core-image-minimal
On Fri, Jan 27, 2012 at 03:52:58PM +0530, Joshua Immanuel wrote:
> Hello Martin,
>
> On Fri, 2012-01-27 at 09:08 +0100, Martin Jansa wrote:
> > > Perhaps, but it didn't fix this particular problem. Neither
> > > /usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs.
> > > However, each still appears in their respective workdir/image:
> >
> > Are they in workdir/packages-split/genmac/etc/init.d/genmac
> > workdir/packages-split/ranpwd/etc/init.d/ranpwd
>
> I too have a similar issue when I try to include a manually constructed
> fstab file into the rootfs image. The file is available in the following
> locations
> 1. core2-poky-linux/${PN}-${PV}-${PR}/etc/fstab
> 2. core2-poky-linux/${PN}-${PV}-${PR}/packages-split/${PN}/etc/fstab
>
> but not in the final rootfs image. May be I am missing something
> trivial.
Maybe it depends on used package-manager bud I guess that at least
opkg will refuse to overwrite /etc/fstab provided by base-files by
/etc/fstab from your fancy PN and even if it allows it in do_rootfs,
then it's not good idea for image with online package management,
because your custom fstab will be overwritten as soon as base-files are
changed.
Why not .bbappend base-files and customize fstab there?
> Eager to know the solution on this thread.
>
> Regards
> Joshua
> --
> Joshua Immanuel
> HiPro IT Solutions Private Limited
> http://hipro.co.in
> ___
> 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] New recipes not installing in core-image-minimal
Hello Martin,
On Fri, 2012-01-27 at 09:08 +0100, Martin Jansa wrote:
> > Perhaps, but it didn't fix this particular problem. Neither
> > /usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs.
> > However, each still appears in their respective workdir/image:
>
> Are they in workdir/packages-split/genmac/etc/init.d/genmac
> workdir/packages-split/ranpwd/etc/init.d/ranpwd
I too have a similar issue when I try to include a manually constructed
fstab file into the rootfs image. The file is available in the following
locations
1. core2-poky-linux/${PN}-${PV}-${PR}/etc/fstab
2. core2-poky-linux/${PN}-${PV}-${PR}/packages-split/${PN}/etc/fstab
but not in the final rootfs image. May be I am missing something
trivial.
Eager to know the solution on this thread.
Regards
Joshua
--
Joshua Immanuel
HiPro IT Solutions Private Limited
http://hipro.co.in
signature.asc
Description: This is a digitally signed message part
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New recipes not installing in core-image-minimal
On Thu, Jan 26, 2012 at 05:57:11PM -0800, Darren Hart wrote:
>
>
> On 01/26/2012 05:42 PM, Saul Wold wrote:
> > On 01/26/2012 05:29 PM, Darren Hart wrote:
> >> In support of a new BSP I've written two new recipes and appended to
> >> another to depend on them. The new recipes files are not appearing in
> >> the resulting images. I'm sure I'm overlooking something trivial, but
> >> I'm not sure what it would be. The layer is available here:
> >>
> >> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=dvhart/sys940x
> >>
> >> I've added ranpwd, genmac, and appended to netbase.
> >>
> >> netbase RDEPENDS on genmac and genmac RDEPENDS on ranpwd. Building
> >> core-image-minimal triggers the build of genmac and ranpwd, and the
> >> modified /etc/network/interfaces appears in the rootfs. genmac and
> >> ranpwd place the appropriate files in their workdir/image directory, but
> >> those files don't make it into the rootfs.
> >>
> > RDEPENDS_${PN} would work much better !
>
> Perhaps, but it didn't fix this particular problem. Neither
> /usr/bin/ranpwd nor /etc/init.d/genmac appear in the rootfs. However,
> each still appears in their respective workdir/image:
Are they in workdir/packages-split/genmac/etc/init.d/genmac
workdir/packages-split/ranpwd/etc/init.d/ranpwd
Maybe log.do_package even reports them as unpackaged files..
I don't think that update-rc.d adds /etc/init.d to FILES_${PN} for you.
Cheers,
>
> $ find
> tmp/work/sys940x_noemgd-poky-linux/core-image-minimal-1.0-r0/rootfs
> -name "ranpwd"
>
>
> $ find
> tmp/work/sys940x_noemgd-poky-linux/core-image-minimal-1.0-r0/rootfs
> -name "genmac"
>
>
> $ ls tmp/work/core2-poky-linux/genmac-1.0-r0/image/etc/init.d/
> genmac
>
> $ ls tmp/work/core2-poky-linux/ranpwd-git-r0/image/usr/bin/
> ranpwd
>
> genmac doesn't have a log.do_install in the workdir/temp directory. Is
> that significant?
>
> ranpwd does, but it isn't instructive:
>
> $ cat tmp/work/core2-poky-linux/ranpwd-git-r0/temp/log.do_install
> DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common',
> 'common-linux', 'common-glibc', 'i586-linux', 'common']
>
> Any other thoughts?
>
>
> >
> > Sau!
> >
> >> Can anyone offer an explanation as to why that might be? The top 4
> >> commits of the repository linked to above will list the new recipes and
> >> the bbappend for reference.
> >>
> >> Thanks,
> >>
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
> ___
> 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] New recipes not installing in core-image-minimal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/2012 12:02 AM, Martin Jansa wrote:
> On Thu, Jan 26, 2012 at 05:29:19PM -0800, Darren Hart wrote:
>> In support of a new BSP I've written two new recipes and appended
>> to another to depend on them. The new recipes files are not
>> appearing in the resulting images. I'm sure I'm overlooking
>> something trivial, but I'm not sure what it would be. The layer
>> is available here:
>>
>> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=dvhart/sys940x
>>
>>
>>
I've added ranpwd, genmac, and appended to netbase.
>>
>> netbase RDEPENDS on genmac and genmac RDEPENDS on ranpwd.
>> Building core-image-minimal triggers the build of genmac and
>> ranpwd, and the modified /etc/network/interfaces appears in the
>> rootfs. genmac and ranpwd place the appropriate files in their
>> workdir/image directory, but those files don't make it into the
>> rootfs.
>>
>> Can anyone offer an explanation as to why that might be? The top
>> 4 commits of the repository linked to above will list the new
>> recipes and the bbappend for reference.
>
> Have you tried correct version of RDEPENDS? RDEPENDS_${PN} ?
I have, yes, this is what Saul suggested in his response. Same end result.
- --
Darren
>
> Cheers,
>>
>> Thanks,
>>
>> -- Darren Hart Intel Open Source Technology Center Yocto Project
>> - Linux Kernel ___
>> yocto mailing list yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
- --
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPIlrzAAoJEKbMaAwKp364JC4IAJWQOfoNUlbXUSMfe3OQda5V
NOSBcFSEfkkk7c/cvxWHq9B298BRvqMDXzTY2kqZOOjx5a8zocg/+wRLdkvPjx7F
x9ZpSVjp+UDoHeQDDh9Qx3My7r2w1h2RK6YTM1sc+y3Ubc1USxdvedOLAVCzoE7O
Imr2aDKFWgyaK2C5dmxC4kTVwwIVStlciX1KaomcJv2kfvVpV1Cg2jDdEkwwPAu7
m09JcasPnukS+T7yF6XBMelYrWLbkJnH4O19pvaHXbZIDBLBon72zpXC+dahpCmm
41KNwrRKTIzW/iSk562ZF+KwD+tVLnpxGKYqxpmsJ7HyU0dOylSDfcsj8Yf9nsc=
=JAHD
-END PGP SIGNATURE-
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] New recipes not installing in core-image-minimal
On Thu, Jan 26, 2012 at 05:29:19PM -0800, Darren Hart wrote:
> In support of a new BSP I've written two new recipes and appended to
> another to depend on them. The new recipes files are not appearing in
> the resulting images. I'm sure I'm overlooking something trivial, but
> I'm not sure what it would be. The layer is available here:
>
> http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=dvhart/sys940x
>
> I've added ranpwd, genmac, and appended to netbase.
>
> netbase RDEPENDS on genmac and genmac RDEPENDS on ranpwd. Building
> core-image-minimal triggers the build of genmac and ranpwd, and the
> modified /etc/network/interfaces appears in the rootfs. genmac and
> ranpwd place the appropriate files in their workdir/image directory, but
> those files don't make it into the rootfs.
>
> Can anyone offer an explanation as to why that might be? The top 4
> commits of the repository linked to above will list the new recipes and
> the bbappend for reference.
Have you tried correct version of RDEPENDS? RDEPENDS_${PN} ?
Cheers,
>
> Thanks,
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
> ___
> 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
