Re: [yocto] how to set up PREMIRRORS_prepend to avoid constant git clones?
On 03/10/2012 04:51 PM, Gary Thomas wrote:
On 2012-03-10 08:46, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
On 2012-03-10 08:29, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
On 2012-03-10 06:39, Robert P. J. Day wrote:
... snip ...
$ bitbake -c fetchall core-image-minimal
and got something unexpected:
NOTE: package bash-4.2-r1: task do_fetch: Started
ERROR: Function failed: Network access disabled through
BB_NO_NETWORK
but access rquested with command /usr/bin/env wget -t 5 -nv
--passive-ftp --no-check-certificate -P
/home/rpjday/yocto/builds/beag2/downloads
'ftp://ftp.gnu.org/gnu/bash/bash-4.2-patches/bash42-001' (for url
None)
ERROR: Logfile of failure stored in:
/home/rpjday/yocto/builds/beag2/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/bash-4.2-r1/temp/log.do_fetch.32479
Log data follows:
| DEBUG: Trying PREMIRRORS
... snip ...
i can clearly see the problem -- while i have the bash tarball
itself in my own mirror, i don't have the patches to go with it, as
defined in the recipes file:
SRC_URI = ${GNU_MIRROR}/bash/${BPN}-${PV}.tar.gz;name=tarball \
${GNU_MIRROR}/bash/bash-4.2-patches/bash42-001;apply=yes;striplevel=0;name=patch001
\
${GNU_MIRROR}/bash/bash-4.2-patches/bash42-002;apply=yes;striplevel=0;name=patch002
\
${GNU_MIRROR}/bash/bash-4.2-patches/bash42-003;apply=yes;striplevel=0;name=patch003
\
... etc etc ...
when i went looking for actual downloads in step 1, i just
searched
for sizable tarballs or zip files, it never occurred to me to check
for patch files. so i guess i just have to be more observant and
check for patch files as well (or anything else a recipe might
want to
download).
so far, so good?
I didn't check but this is often the recipe's fault. It must specify
an exact git SRCREV, not a tag, for the NO_NETWORK to be successful.
i'm not sure what you're saying here. the patches are simple
files,
nothing to do with git. the bash source itself is properly being
fetched from my mirror -- it's the numerous patch files i was unaware
of that still require network access; that is, until i manually copied
them over to my mirror directory, and that solved the problem.
i just had to notice that the bash recipe downloaded a number of
patch files, then add them to my local mirror.
Sorry, I misread. Yes, you do need those patch files in your local
mirror.
In fact, if you look at ${BUILD}/downloads, every _file_ (not
symlink) that's
at the top level needs to be copied. I manage this by running a script
like this:
(cd downloads;find . -type f -maxdepth 1 | tar -cT - | tar -x -C
${DL_DIR})
but doesn't that pick up all the .done files as well? doesn't
hurt, but certainly unnecessary.
I said something like - add in | grep -v .done if you want to skip
those.
I actually use a more complex script as there are some things I simply
never
want to copy...
I added a small how-do-i on this subject, since I have not found it
documented elsewhere.
https://wiki.yoctoproject.org/wiki/How_do_I
Please remove/add if something is incorrect.
Br,
David
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Web Hob GUI design
Hi Belen, In the meantime of GTK Hob development, we are also moving forward on web hob development. One question is that, will the web hob GUI follow with GTK hob design? Or do we need a new design for web style? Thanks, Dongxiao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] is yocto based on oe-core *as-is*?
On 2012-03-11 16:38, Paul Eggleton wrote: On Sunday 11 March 2012 06:46:17 Gary Thomas wrote: On 2012-03-11 06:33, Paul Eggleton wrote: This is correct, and you can verify it by doing a diff of the OE-Core meta/ subdirectory against Poky's meta/ - the only difference is that Poky does not include the sample configs (it provides its own in meta-yocto). Have you actually done such a comparison? Yes, I did so before sending the above message. I just compared them like this: poky/yocto: commit 320558f494c618f53e0c773db3ea0109476e8359 Author: Paul Eggletonpaul.eggle...@linux.intel.com Date: Wed Feb 29 12:59:14 2012 + openembedded-core: commit 50dc8bfbac42b9a9b52a2f7d0568740c41790c13 Author: Richard Purdierichard.pur...@linuxfoundation.org Date: Fri Mar 9 14:14:04 2012 +0800 These are the up-to-date master branches, as of 2012-03-11 12:40 GMT I don't think you'll find they are. Your poky branch is behind OE-Core by quite a number of commits - in fact 320558f494c618f53e0c773db3ea0109476e8359 is where the 1.2_M3 branch HEAD is currently, are you sure you aren't on that branch instead of master? You're right, but I sure don't know how that happened! I never have anything but master checked out, but somehow this time I did. Sorry for the noise. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Poky-Build error
Hi Mark, Thanks a lot for your reply and i will take care for mailing list etiquette.. Check your logs for a makedevs-native. If that hasn't been built I checked for makedevs-native and found makedevs-native is not built. Can you please suggest me what could be the wrong in the configuration and where i should look at? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] 1.2_M2-Final build failures
On Monday 12 March 2012 14:14:48 Wolfgang Denk wrote: In message 3971839.nMHIKpoOXs@helios Paul Eggleton wrote: On Wednesday 01 February 2012 11:28:22 jfabernathy wrote: Using the tarballs for Poky and meta-intel for 1.2_M2-Final, I was getting a lot of build failures below is what worked and what didn't. Not sure if this is a bug or if I'm missing something. I extracted the meta-intel tarball for 1.2_M2-Final in the poky directory created by extracting the poky tarball for 1.2_M2.Final. ... 3. building n450 core-image-minimal fails with error: ERROR: Unable to parse /home/jim/poky/meta/recipes-core/tasks/task-base.bb:00:20 Traceback (most recent call last): File /home/jim/poky/bitbake/lib/bb/parse/ast.py, line 379, in multi_finalize(fn='/home/jim/poky/meta/recipes-core/tasks/task-base. bb http://task-base.bb', d=bb.data_smart.DataSmart object at 0x4a801d0): ... 4. building cedartrail core-image-minimal fails with error: ERROR: Unable to parse conf/bitbake.conf: Could not include required file conf/machine/include/ia32-base.inc I think I know what's going on here. In previous editions it was enough to have just the meta-intel sub-layer in your bblayers.conf (e.g. meta-crownbay) - now you also need to add meta-intel itself to get certain common files. If you do this then your errors will go away. Is it correct to assume that your note refers to the 4. problem above only? I don't recall now but I assume I meant both at the time. FWIW it seems that for Jim's case both issues were solved by the suggested fix. I see the very same error as described as 3. above, but I don't use sub-layers. I'm not sure what you mean here. Which entries for meta-intel do you have in your bblayers.conf? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] 1.2_M2-Final build failures
Dear Paul, In message 1619950.WDgEWRegMs@helios you wrote: I see the very same error as described as 3. above, but I don't use sub-layers. I'm not sure what you mean here. Which entries for meta-intel do you have in your bblayers.conf? None. I have this: - cat conf/bblayers.conf # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = 4 BBFILES ?= BBLAYERS ?= \ /home/wd/git/poky/eldk-5.2/meta \ /home/wd/git/poky/eldk-5.2/meta-yocto \ /home/wd/git/poky/eldk-5.2/meta-eldk \ This was working fine before, and we don't have any sub-layers in meta-eldk. So far I have no idea where to look ... Thanks! Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/3][KERNEL] yocto/emgd: emgd 1.10 driver
From: Tom Zanussi tom.zanu...@intel.com The starting-point code that subsequent patches will modify. This is a straight copy of the code in the emgd 1.10 emgd driver, specifically IEMGD_HEAD_Linux/common/drm/emgd_drm.tgz from LIN_EMGD_1_10_RC_2209.tgz, the 'Linux Tar Ball' release downloaded from http://edc.intel.com/Software/Downloads/EMGD/. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- drivers/gpu/drm/emgd/Makefile | 326 + 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| 1005 +++ drivers/gpu/drm/emgd/emgd/gmm/gtt.c| 436 ++ drivers/gpu/drm/emgd/emgd/include/cmd.h| 47 + drivers/gpu/drm/emgd/emgd/include/context.h| 254 + drivers/gpu/drm/emgd/emgd/include/debug.h | 169 + drivers/gpu/drm/emgd/emgd/include/decode.h | 76 + drivers/gpu/drm/emgd/emgd/include/dispatch.h | 59 + drivers/gpu/drm/emgd/emgd/include/dispatch_utils.h | 78 + drivers/gpu/drm/emgd/emgd/include/displayid.h | 644 ++ drivers/gpu/drm/emgd/emgd/include/dsp.h| 46 + drivers/gpu/drm/emgd/emgd/include/edid.h | 130 + drivers/gpu/drm/emgd/emgd/include/general.h| 84 + drivers/gpu/drm/emgd/emgd/include/instr_common.h | 54 + drivers/gpu/drm/emgd/emgd/include/intelpci.h | 98 + drivers/gpu/drm/emgd/emgd/include/math_fix.h | 59 +
[yocto] [PATCH 0/3][KERNEL] emgd 1.10 for linux-yocto 3.2
From: Tom Zanussi tom.zanu...@intel.com Hi Bruce, Please pull in the emgd-1.10 topic branch below into linux-yocto-3.2. Thanks, Tom The following changes since commit 417fc778a86e81303bab5883b919ee422ec51c04: Bruce Ashfield (1): perf: hard-code NO_LIBPERL/NO_LIBPYTHON are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/linux-yocto-3.2/emgd-1.10 http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/linux-yocto-3.2/emgd-1.10v1 Tom Zanussi (3): yocto/emgd: emgd 1.10 driver yocto/emgd: initial build fixups yocto/emgd: linux 3.2-related 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 | 2401 +++ 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 | 802 +++ 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| 1005 +++ drivers/gpu/drm/emgd/emgd/gmm/gtt.c| 436 ++ drivers/gpu/drm/emgd/emgd/include/cmd.h| 47 + drivers/gpu/drm/emgd/emgd/include/context.h| 254 + drivers/gpu/drm/emgd/emgd/include/debug.h | 169 + drivers/gpu/drm/emgd/emgd/include/decode.h | 76 + drivers/gpu/drm/emgd/emgd/include/dispatch.h | 59 + drivers/gpu/drm/emgd/emgd/include/dispatch_utils.h | 78 + drivers/gpu/drm/emgd/emgd/include/displayid.h | 644 ++
[yocto] [PATCH 2/3][KERNEL] yocto/emgd: initial build fixups
From: Tom Zanussi tom.zanu...@intel.com
Add emgd config option (DRM_EGD) and modify Makefiles for in-tree
builds.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
drivers/gpu/drm/Kconfig |9 +
drivers/gpu/drm/Makefile |1 +
drivers/gpu/drm/emgd/Makefile | 40
3 files changed, 14 insertions(+), 36 deletions(-)
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 1368826..2207d03 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -159,6 +159,15 @@ config DRM_SAVAGE
Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
chipset. If M is selected the module will be called savage.
+config DRM_EGD
+ tristate Intel EMGD
+ depends on DRM
+ select DRM_KMS_HELPER
+ help
+ Choose this option if you have an EMGD-supported chipset
+ (Intel E6xx or System Controller Hub US15W/US15WP/WPT).
+ If M is selected the module will be called emgd.
+
source drivers/gpu/drm/exynos/Kconfig
source drivers/gpu/drm/vmwgfx/Kconfig
diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile
index c0496f6..ca90165 100644
--- a/drivers/gpu/drm/Makefile
+++ b/drivers/gpu/drm/Makefile
@@ -36,4 +36,5 @@ obj-$(CONFIG_DRM_VMWGFX)+= vmwgfx/
obj-$(CONFIG_DRM_VIA) +=via/
obj-$(CONFIG_DRM_NOUVEAU) +=nouveau/
obj-$(CONFIG_DRM_EXYNOS) +=exynos/
+obj-$(CONFIG_DRM_EGD) +=emgd/
obj-y += i2c/
diff --git a/drivers/gpu/drm/emgd/Makefile b/drivers/gpu/drm/emgd/Makefile
index 13705f4..3971c7f 100644
--- a/drivers/gpu/drm/emgd/Makefile
+++ b/drivers/gpu/drm/emgd/Makefile
@@ -24,10 +24,6 @@
#
export EGD_TOPLEVEL = DRM Driver
-KERNELVER ?= $(shell uname -r)
-KERNELDIR ?= /lib/modules/$(KERNELVER)/build
-INSTALLDIR ?= /lib/modules/$(KERNELVER)/kernel/drivers/gpu/drm/emgd
-
BLUE = \033[34m
OFF = \033[0m
BUILD ?= release
@@ -35,7 +31,7 @@ CONFIG_PVR_RELEASE ?= $(BUILD)
CONFIG_DRM_EGD ?= m
# Get the include paths pointed to the right place.
-export EMGD_MOD_DIR ?= $(CURDIR)
+export EMGD_MOD_DIR ?= $(obj)
BUILDDATE ?= $(shell date +%Y%m%d)
@@ -51,6 +47,7 @@ PROJECT_INCLUDES = \
-I$(EMGD_MOD_DIR)/emgd/pal/ch7036 \
-I$(EMGD_MOD_DIR)/emgd/drm \
-I$(KERNELDIR)/include/drm \
+ -Iinclude/drm \
-I/usr/src/linux-headers-2.6.32-5-common/include/drm \
-I$(EMGD_MOD_DIR)/pvr/include4 \
-I$(EMGD_MOD_DIR)/pvr/services4/include \
@@ -120,6 +117,8 @@ ifeq ($(PDUMP),1)
EXTRA_CFLAGS += -DPDUMP=1
endif
+ccflags-y += $(EXTRA_CFLAGS)
+
EMGD_OBJS := \
emgd/drm/emgd_fb.o \
emgd/drm/emgd_fbcon.o \
@@ -293,34 +292,3 @@ ifeq ($(PDUMP),1)
endif
obj-$(CONFIG_DRM_EGD) += emgd.o
-
-all:: clean modules
-
-modules::
- @echo $(CURDIR) -- $(CONFIG_PVR_RELEASE)
- @echo $(MAKE) -C $(KERNELDIR) M=$(CURDIR) modules
- @$(MAKE) -C $(KERNELDIR) M=$(CURDIR) modules
-
-clean::
- @rm -f $(emgd-y)
- @rm -f emgd.o emgd.mod.* emgd.ko Module.* modules.order
- @find . -name *.cmd -exec rm '{}' \;
-
-install::
- install -o root -g root -m 755 -d $(INSTALLDIR)
- install -o root -g root -m 744 emgd.ko $(INSTALLDIR)
- /sbin/depmod -a
-
-uninstall::
- rmmod $(INSTALLDIR)/emgd.ko
- rm -rf $(INSTALLDIR)/emgd.ko
- /sbin/depmod -a
-
-debug::
- export CONFIG_PVR_RELEASE=debug; $(MAKE) modules
-
-package:: clean
- @echo -e $(BLUE)Packaging $(EGD_TOPLEVEL)$(OFF);
- mkdir -p $(EGD_PKG)
- tar -C $(EMGD_MOD_DIR) --exclude CVS -czf $(EGD_PKG)/emgd_drm.tgz *
-
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 3/3][KERNEL] yocto/emgd: linux 3.2-related build fixups
From: Tom Zanussi tom.zanu...@intel.com Fix build errors caused by changes to kernel interfaces introduced by linux 3.2 such as: error: 'THIS_MODULE' undeclared here (not in a function) due to a missing THIS_MODULE definition which can be found in linux/export.h. It also fixes a ream of errors like: error: expected ')' before string constant due to missing MODULE_PARM_DESC definition which can be found in linux/moduleparam.h, included by linux/module.h, needed also for MODULE_AUTHOR, etc. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c |2 ++ drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c |1 + 2 files changed, 3 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c b/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c index 5a8f2e6..9ed2363 100644 --- a/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c +++ b/drivers/gpu/drm/emgd/emgd/drm/emgd_drv.c @@ -38,6 +38,8 @@ #include drm/drm_crtc_helper.h #include linux/version.h #include linux/device.h +#include linux/export.h +#include linux/module.h #include drm/drm_pciids.h #include intelpci.h #include drm_emgd_private.h diff --git a/drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c b/drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c index 547caaa..edfe2c7 100644 --- a/drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c +++ b/drivers/gpu/drm/emgd/emgd/drm/emgd_fbcon.c @@ -36,6 +36,7 @@ #include drmP.h #include drm_crtc_helper.h #include linux/vga_switcheroo.h +#include linux/export.h #include user_config.h -- 1.7.0.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] issue building iputils with uclibc
On 09/03/2012 16:45, Khem Raj wrote: On Fri, Mar 9, 2012 at 7:45 AM, John Toomeyjohn.too...@linux.intel.com wrote: Anything else I can try? Do you have UCLIBC_HAS_RESOLVER_SUPPORT=y in uclibc .config ? I dont think so, is there an easy way to check? How would I set it to try this? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto and LTSI
On 03/09/2012 06:43 AM, Bruce Ashfield wrote: On 12-03-09 09:36 AM, Bob Cochran wrote: On 03/09/2012 08:43 AM, Bruce Ashfield wrote: On 12-03-09 07:20 AM, David Nyström wrote: Hi All, Whats yoctos take on LTSI ? http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=summary http://lwn.net/Articles/484337/ I've noticed that LTT-ng and other kernel patches are independently ported and maintained by the yocto project. Are there any plans for yocto to have ltsi-kernel patches as upstream ? We'll be syncing up with the ltsi kernel parts over the summer. But yes, LTSI will be one of the sources used for yocto kernel trees. Cheers, Bruce I just finished reviewing the slides for LTSI given at ELC: (https://events.linuxfoundation.org/images/stories/pdf/lf_elc12_shibata.pdf). Why does the Linux Foundation need to get behind yet another effort to maintain a kernel repository for embedded? It seems that many of the objectives are the same for the two projects regarding the kernel. Why not just branch a yearly Yocto kernel as long-term stable and add the support methodology outlined in the LTSI slides to this branch? Perhaps this could also be done with the Poky repo? LTSI is still relatively new, a bit of patience is required for us to effectively collaborate between the two areas. But yocto will always have a newer kernel than LTSI as we work throughout any given period. Quite simply put, there is no way to have one kernel version that meets everyone's needs. That's always been the case, and will likely continue to be the case for the forseeable future. How is a developer supposed to view Yocto and LTSI? The former is cutting edge, developer friendly with all the bells whistles, and experimental but use the latter for production??? Or maybe use the tools and rootfs from Yocto but the kernel from LTSI? These sorts of things are still being worked out, when we actually have a LSTI based yocto option, some sort of messaging will be created. It seems Greg K-H of LTSI should join forces with Yocto and keep things simple unified for us embedded developers (or Yocto should dump maintaining its own kernel repos and just draw from LTSI). I already have initial conact with Greg on sync'ing up my efforts with LSTI. Perhaps someday there will be a more complete overlap in the two, but today there isn't a complete overlap, so there will be additions to LTSI that some boards/features/etc that yocto requires. Those additions may degrade to zero over time. In fact, if everything would just go mainline .. that would be even better. Another point to make is that Yocto Project recipes (applications, system libraries, and Linux kernels) will always be based on some upstream, and should not be considered an upstream themselves. In future releases, the linux-yocto recipes will use LTSI as a base, and continue to work to push any changes we have to make by way of integration and stablization to mainline as well as LTSI. -- 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 0/3][KERNEL] emgd 1.10 for linux-yocto 3.2
On 12-03-12 11:09 AM, tom.zanu...@intel.com wrote: From: Tom Zanussitom.zanu...@intel.com Hi Bruce, Please pull in the emgd-1.10 topic branch below into linux-yocto-3.2. Thanks, Tom The following changes since commit 417fc778a86e81303bab5883b919ee422ec51c04: Bruce Ashfield (1): perf: hard-code NO_LIBPERL/NO_LIBPYTHON are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/linux-yocto-3.2/emgd-1.10 http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/linux-yocto-3.2/emgd-1.10v1 Looks good. Merged and pushed. Cheers, Bruce Tom Zanussi (3): yocto/emgd: emgd 1.10 driver yocto/emgd: initial build fixups yocto/emgd: linux 3.2-related 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 | 2401 +++ 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 | 802 +++ 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| 1005 +++ drivers/gpu/drm/emgd/emgd/gmm/gtt.c| 436 ++ drivers/gpu/drm/emgd/emgd/include/cmd.h| 47 + drivers/gpu/drm/emgd/emgd/include/context.h| 254 + drivers/gpu/drm/emgd/emgd/include/debug.h | 169 + drivers/gpu/drm/emgd/emgd/include/decode.h | 76 +
Re: [yocto] custom image recipes
On Sunday 11 March 2012 13:14:12 João Henrique Freitas wrote:
One of my custom recipes (via-image-st.bb) is to make a custom image
(adding some files). Example:
SRC_URI = \
file://interfaces \
file://snmpd.conf \
file://snmp.conf \
file://syslog.conf \
file://ntpd \
file://syslog.lr \
inherit core-image
ROOTFS_POSTPROCESS_COMMAND_append = remove_packaging_data_files ;
ROOTFS_POSTPROCESS_COMMAND_append = setup_target_image ;
setup_target_image() {
mkdir -p ${IMAGE_ROOTFS}/opt/sistema/conf
install -m 0644 ${WORKDIR}/interfaces
${IMAGE_ROOTFS}/etc/network/interfaces
...
}
When I run: bitbake via-image-st:
install: cannot stat
`/mnt/yocto/build/mst_1.2/tmp/work/qemux86-tp-linux/via-image-st-1.0-r1/inte
rfaces': No such file or directory
NOTE: package via-image-st-1.0-r1: task do_rootfs: Failed
ERROR: Task 8
(/home/joaohf/jhf/tropico/projetos/yocto-1.1tropico/meta-tropico/meta-viast/
images/ via-image-st.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3192 tasks of which 3190 didn't need to be
rerun and 1 failed.
Summary: 1 task failed:
/home/joaohf/jhf/tropico/projetos/yocto-1.1tropico/meta-tropico/meta-viast/i
mages/ via-image-st.bb, do_rootfs
I think this commit
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbc
lass?id=6706c7bdd2de6e0e447d90062e74a718a8d31778the others task doesn't
perform.
Indeed, this seems to no longer be supported. I think this is probably a good
idea because then there is less confusion as to where files come from.
The main question is: How I can create a recipe to customize some files
inside of the image?
I need to have a recipe like base-files? (recipes-core/base-files/
base-files_3.0.14.bb)
Yes, the preferred method to achieve this is to use bbappends for the recipes
where these files appear if they are already provided by a recipe, e.g. netbase
for /etc/network/interfaces - see here for a machine-specific example:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/recipes-core/netbase
For new files you can either include them via the same bbappend mechanism if
that makes sense for the particular files, or a separate recipe.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project 1.2 M3 1.1.1 release readiness
Attendees: Dave. Nitin, Beth, Jessica, Mark, Darren, Terrance, Richard, Saul, ScottR, Denys, Josh, Matthew M3 readiness - release criteria review (https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status#Milestone_3 ): 1. Functional completion: All P1s but 1145 and 1890 are completed. 1145 and 1890 have been pushed to M4 due to resource conflict with conferences and their preparation. 1145 is about improve bitbake output messaging. 1890 is about the web interface for build history analysis. They are both pushed to early M4. There are no features depending on them. The team agrees that they can be left for M4. a significant part of P2/P3's are completed in M3 or close to complete. We also moved some of the P2/P3's to post 1.2. We are still reviewing the list, there will be more to be moved to post 1.2. 2. No high bugs against M3. All high bugs are analyzed and they are not blockers for M3 release. 2066 is a high bug without any fix now. But it does not affect P1 features of M3 release. We have a plan and Saul will follow up to root cause it and have the fix in master. 3. The full pass QA report looks good. We have some issues with the core build system but most of them have patches in master already. 2048: patches soon, marked for M4 2050: Bruce/Nitin has a patch already, needs to be in master. Marked for M4 2054: Patch in master 1229: Patch in master 2051: Patch in master 2052: Patch in master 4. Distro tested with latest version and they all passed. 5. There is no significant performance degradation. 2048: patches soon, marked for M4 2050: Bruce/Nitin has a patch already, needs to be in master. Marked for M4 2054: Patch in master 1229: Patch in master 2051: Patch in master 2052: Patch in master Decision: the team unanimously agreed to release M3 RC1 for M3. Beth will pack up the release and release note, it should be released sometime today. 1.1.1 point release: We had a build and QA has given a full pass testing for it. Some issues are found, we have fixed significant ones and pulled the patches into the build. QA has tested and verified those fixes. We still have some issues left but the team agrees that they should not block the point release. Decision: the team agrees to release the current build for the 1.1.1 point release. Next step: 1. Beth will pack up the release. 2. Josh will gather the known issues list and send to Beth. 3. Scott Rifenbark will work with Beth to point the 1.1.1 web link to the right place. 4. Beth will then push and announce the release in the public mailing list. -Original Appointment- From: Liu, Song Sent: Friday, March 09, 2012 2:44 PM To: yocto@yoctoproject.org Cc: Mueller, Robert; 'Ravi Vompolu'; 'Anders Darander'; Barros Pena, Belen; Bodke, Kishore K; 'Bruce Ashfield'; 'Daniel Cauchy'; 'deVries, Alex'; 'Dixon, Brad'; Dmytriyenko, Denys; Erway, Tracey M; Flanagan, Elizabeth; Hart, Darren; 'Hatle, Mark'; 'Jeremy Puhlman'; Kooi, Koen; Kridner, Jason; Li, Susie; 'lieu...@windriver.com'; Lock, Joshua; 'McCombe, Kevin'; Moeller, Thorsten; 'mor...@mvista.com'; Osier-mixon, Jeffrey; 'paul.ander...@windriver.com'; 'Polk, Jeffrey'; Purdie, Richard; 'Ranslam, Rob'; Rifenbark, Scott M; Saxena, Rahul; Stewart, David C; Wang, Shane; Wold, Saul; Yu, Ke; Zanussi, Tom; Zhang, Jessica; 'Hudson, Sean'; Arce Moreno, Abraham; mor...@mvista.com; Elizabeth Flanagan; Moses, Fred Subject: Yocto Project 1.2 M3 1.1.1 release readiness When: Monday, March 12, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada). Where: Bridge Info Enclosed Monday, March 12, 2012, 08:00 AM US Pacific Time 916-356-2663, 8-356-2663, Bridge: 4, Passcode: 1137217 Speed dialer: inteldialer://4,1137217 | Learn more ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] custom image recipes
Thanks. I will try this. Yes, the preferred method to achieve this is to use bbappends for the recipes where these files appear if they are already provided by a recipe For new files you can either include them via the same bbappend mechanism if that makes sense for the particular files, or a separate recipe. -- --- João Henrique Freitas - joaohf_at_gmail.com Campinas-SP-Brasil BSD051283 LPI 1 http://www.joaohfreitas.eti.br ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, March 13, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada).
Agenda * Opens collection - 5 min (Song) * Yocto 1.2 M3/M4 status - 20 min (Song/Team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.2_Status * SWAT team rotation: Beth-Paul * Opens - 10 min * Team Sharing - 20 min -Original Appointment- Conference details Conference name:Yocto Technical Team Conference date/start time: Tue Jun 28, 2011 at 10:00 AM Central Daylight Time Participants: 30 Duration: 60 minutes Participant passcode: 49611427 Dial-in number: 1.972.995. US Toll Free number:1.877.561.6828 BlackBerry users, click this link to join your conference as a chairperson: 1.972.995.x67184230# BlackBerry users, click this link to join your conference as a participant: 1.972.995.x49611427# Depending on where you are dialing from, either your BlackBerry will pause and enter the passcode automatically or you will be prompted to click again to dial the passcode. Local and Global Access Numbers Country Dial-in number Australia: 1800 636 843 Czech Republic: 242 430 350 China (Beijing): From office dial 8-995 or 8784277 Beijing Out of Office dial 5878 4277 China (Shanghai): From office dial 8-995 or 3073322 Shanghai Out of Office dial 2307 3322 China (Shenzen): From office dial 8-995 or 6007877 Shenzen Out of Office dial 2600 7877 China (Other Cities): From IP phone dial 8-995 Other cities - Non IP phone dial 021-23073322 Denmark: 8060 1400 Finland: 09 41333477 France: 0497 275888 Germany: 08161 803232 Holland: 030 2417490 India: BSNL subscribers use 1800 425 9996 (Toll Free) Airtel subscribers use 0008 009 861 212 (Toll Free) From TI Campus use 8995 Others use 2509 9555 (Landline within Bangalore) or 80 2509 9555 (Outside Bangalore) Israel: 09 790 6715 Italy: 039 69061234 (039 is local city code not country code) Japan: From TI Campus use 8 995 Outside TI use 03 4331 3777 Malaysia: From IP phone dial 2643799 From Kuala Lumpur dial 4264 3799 Outside Kuala Lumpur dial (03)4264 3799 Norway: 2 295 8744 Philippines: From Baguio City use 4471177 From Metro Manila area use 8702477 Singapore: From IP phone dial 3894777 Outside TI use 6389 4777 South Korea: From IP phone dial 5606998 From Seoul dial 5606998 Outside Seoul dial (02)5606998 Sweden: 08 58755577 Taiwan: From IP phone dial 1363 From Taipei dial 2241 1363 Outside Taipei dial (02)2241 1363 Turkey: Landline Only dial 0811 288 0001 then enter 877 633 1123 UK: 01604 663003 US: 972 995 or 1877 561 6828 Recurring conferences First scheduled conference: Tue Jun 28, 2011 Recurrence frequency: Weekly - Every 1 week(s) on Tuesday Recurrence ends:End on Fri Jun 22, 2012, 10:40 AM CDT ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/2] meta-intel: crownbay 3.2 update
From: Tom Zanussi tom.zanu...@intel.com This updates crownbay and crownbay-noemgd to the 3.2 kernel. It also fixes a problem seen with a missing emgd dependency when testing. The following changes since commit d9132cc66316be45f44beeea6eba734bb3ab337d: Tom Zanussi (1): ia32-base: remove libc-headers PREFERRED_PROVIDER are available in the git repository at: git://git.yoctoproject.org/meta-intel.git tzanussi/crownbay-kernel-3.2-switch http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/crownbay-kernel-3.2-switch Tom Zanussi (2): meta-crownbay: switch to linux-yocto-3.2 kernel ia32-base: add libva display dependencies to emgd xserver conf/machine/include/ia32-base.inc |3 +++ meta-crownbay/conf/machine/crownbay-noemgd.conf|2 ++ meta-crownbay/conf/machine/crownbay.conf |2 ++ .../linux/linux-yocto-rt_3.2.bbappend | 20 .../recipes-kernel/linux/linux-yocto_3.2.bbappend | 17 + 5 files changed, 44 insertions(+), 0 deletions(-) create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/2] meta-crownbay: switch to linux-yocto-3.2 kernel
From: Tom Zanussi tom.zanu...@intel.com
Switch crownbay and crownbay-noemgd to the 3.2 kernel.
Signed-off-by: Tom Zanussi tom.zanu...@intel.com
---
meta-crownbay/conf/machine/crownbay-noemgd.conf|2 ++
meta-crownbay/conf/machine/crownbay.conf |2 ++
.../linux/linux-yocto-rt_3.2.bbappend | 20
.../recipes-kernel/linux/linux-yocto_3.2.bbappend | 17 +
4 files changed, 41 insertions(+), 0 deletions(-)
create mode 100644
meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf
b/meta-crownbay/conf/machine/crownbay-noemgd.conf
index 2c80bd8..af85b00 100644
--- a/meta-crownbay/conf/machine/crownbay-noemgd.conf
+++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf
@@ -4,6 +4,8 @@
#@DESCRIPTION: Machine configuration for Crown Bay systems, without
Intel-proprietary graphics bits
# i.e. E660 + EG20T
+PREFERRED_VERSION_linux-yocto ?= 3.2%
+
require conf/machine/include/tune-atom.inc
require conf/machine/include/ia32-base.inc
diff --git a/meta-crownbay/conf/machine/crownbay.conf
b/meta-crownbay/conf/machine/crownbay.conf
index 2c1ef3d..1458bff 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -4,6 +4,8 @@
#@DESCRIPTION: Machine configuration for Crown Bay systems
# i.e. E660 + EG20T
+PREFERRED_VERSION_linux-yocto ?= 3.2%
+
require conf/machine/include/tune-atom.inc
require conf/machine/include/ia32-base.inc
diff --git a/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
b/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
new file mode 100644
index 000..dee9bce
--- /dev/null
+++ b/meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
@@ -0,0 +1,20 @@
+FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
+
+COMPATIBLE_MACHINE_crownbay-noemgd = crownbay-noemgd
+KMACHINE_crownbay-noemgd = crownbay
+
+KERNEL_FEATURES_append_crownbay-noemgd += cfg/smp.scc
+
+COMPATIBLE_MACHINE_crownbay = crownbay
+KMACHINE_crownbay = crownbay
+
+KERNEL_FEATURES_append_crownbay += cfg/smp.scc
+
+# Update the following to use a different BSP branch or meta SRCREV
+#KBRANCH_crownbay-noemgd = yocto/standard/preempt-rt/base
+#SRCREV_machine_pn-linux-yocto-rt_crownbay-noemgd ?=
+#SRCREV_meta_pn-linux-yocto-rt_crownbay-noemgd ?=
+
+#KBRANCH_crownbay = yocto/standard/preempt-rt/base
+#SRCREV_machine_pn-linux-yocto-rt_crownbay ?=
+#SRCREV_meta_pn-linux-yocto-rt_crownbay ?=
diff --git a/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
b/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
new file mode 100644
index 000..3b02076
--- /dev/null
+++ b/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
@@ -0,0 +1,17 @@
+FILESEXTRAPATHS_prepend := ${THISDIR}/${PN}:
+
+COMPATIBLE_MACHINE_crownbay = crownbay
+KMACHINE_crownbay = crownbay
+KBRANCH_crownbay = standard/default/crownbay
+KERNEL_FEATURES_append_crownbay += cfg/smp.scc
+
+COMPATIBLE_MACHINE_crownbay-noemgd = crownbay-noemgd
+KMACHINE_crownbay-noemgd = crownbay
+KBRANCH_crownbay-noemgd = standard/default/crownbay
+KERNEL_FEATURES_append_crownbay-noemgd += cfg/smp.scc
+
+SRCREV_machine_pn-linux-yocto_crownbay ?=
4471c11c7755727219b673cb887d8a13b8715aba
+SRCREV_meta_pn-linux-yocto_crownbay ?=
64840f55ee144e9814278eaa8e3f33dd60da892c
+
+SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?=
4471c11c7755727219b673cb887d8a13b8715aba
+SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?=
64840f55ee144e9814278eaa8e3f33dd60da892c
--
1.7.0.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
