**** BEGIN LOGGING AT Sun Apr 25 02:59:56 2010 Apr 25 11:26:51 hi all Apr 25 11:27:58 can someone help me understand some things about bitbake and angstrom?... Apr 25 11:32:45 I built a uImage with the 2.6.31 kernel, and was wondering how to make sure this is actually included in the console-image when i bitbake that. Apr 25 11:34:22 I currently don't quite see how much the two are related. So: does the console-image just download its own linux kernel sources, compile, deploy and clean them without any chance of me choosing which kernel to use? Apr 25 11:34:39 or can I influence this somehow? Apr 25 11:34:54 anyone? Apr 25 11:35:53 or should i go to a different channel? Apr 25 12:06:03 tsaaps: that should be defined in the respective bitbake recipe Apr 25 12:06:48 ok... i had a look at console-image.bb and it's pretty empty... Apr 25 12:07:07 it probably includes some other bb Apr 25 12:07:31 ah, as to the kernel for me that is defined in the machine config IIRC Apr 25 12:08:39 err sorry Apr 25 12:09:08 it's in my local.conf - PREFERRED_VERSION_virtual/kernel = "2.6.27.10-omap1" Apr 25 12:09:37 ah! Apr 25 12:10:40 YMMV ofc Apr 25 12:11:11 * dm8tbr continues to kick fennec 1.1b1c2 into submission Apr 25 12:12:52 nothing in local.conf .. but i remember seeing this somewhere Apr 25 12:13:13 grep for it then :) Apr 25 12:13:21 ;) Apr 25 12:13:30 I guess you can set it even in the console-image.bb if you want to Apr 25 12:13:52 or provide it on the command line before you call bitbake Apr 25 12:33:03 hm PREFERRED_PROVIDER_virtual/kernel isn't found in the git tree, but PREFERRED_VERSION_virtual/kernel got me to the file conf/machine/include/omap3.inc, which seems to have something to do with which other images are included in....something. Don't know if this has anything to do with bitbaking the console-image... Apr 25 12:34:18 honestly, I have no idea :) Apr 25 12:36:15 do you know what it means if a line says PREFERRED_PROVIDER_virtual/kernel = "linux-omap" ? Is linux-omap some recipe then? Seems to be some kind of category for omap-based linuxes... Apr 25 12:36:36 hi tsaaps, is your kernel integrated into a recipe ? Apr 25 12:36:51 yes, i think so Apr 25 12:37:01 should be linux-omap-2.6.31.bb Apr 25 12:37:11 when you do bitbake linux : does it build the kernel you want ? Apr 25 12:38:02 hm I wrote "bitbake -c compile linux-omap-2.6.31" Apr 25 12:38:49 if you want this recipe to be used as a defautl for your machine, you need to tell it somewhere Apr 25 12:39:11 e.g. in your local.conf? :) Apr 25 12:39:23 yes, i think that is what i want. Ok so i guess i should edit some "linux.bb" file? Apr 25 12:39:50 my local.conf is pretty empty.. no reference to lnux versions Apr 25 12:40:07 in linux-omap-2.6.31.bb add : DEFAULT_PREFERENCE_your_machine_name = "1" Apr 25 12:40:31 I don't know if that's the best way to do it but it works Apr 25 12:41:12 hm and remove it from, say linux-omap-2.6.29 ? Apr 25 12:41:18 .bb Apr 25 12:41:31 or you change it to -1 on the other .bb Apr 25 12:42:16 and other way is to set somee variable in conf/machines/your_machine.conf Apr 25 12:42:23 PREFERRED_PROVIDER_virtual/kernel = "linux" Apr 25 12:42:23 PREFERRED_VERSION_linux = "2.6.33" Apr 25 12:42:26 for example Apr 25 12:45:19 aha, btw conf/machine/beagleboard.conf actually references the conf/machine/include/omap3.inc i was wondering about earlier.. things falling into place...... Apr 25 12:50:43 that omap3.inc file specifies PREFERRED_PROVIDER_virtual/kernel = "linux-omap". But I'm still looking for PREFERRED_VERSION_linux-omap... but the conf folder is very informative! Apr 25 12:54:08 yees but doesn't beagleboard.Conf bypass this with linux-omap-psp ? Apr 25 13:00:24 i see that omap3evm.conf does, which is of course very similar.. beagleboard.conf doesn't as far as i can tell. Apr 25 13:13:03 I'm trying to understand the parse order of the config files... What calls conf/machine/beagleboard.conf ? Is it directly related to the line MACHINE ?= "beagleboard" in my local.conf or is there some intermediate step? Apr 25 13:13:44 yes this is related tot your machine **** ENDING LOGGING AT Mon Apr 26 02:59:56 2010