**** BEGIN LOGGING AT Thu May 30 03:00:00 2013
May 30 08:11:01 <ant_work> hi bluelightning
May 30 08:11:09 <bluelightning> hi ant_work
May 30 08:13:50 <ant_work> I'm trying to fix the kernel modules mgmt for Zaurus and up to now I've played with snd-soc modules
May 30 08:15:14 <ant_work> I was under the assumption linux-yocto adds automatically the "configured" modules to a _RRECOMMENDS but..
May 30 08:19:55 <ant_work> it appears that I have to add a specific MACHINE_EXTRA_RRECOMMENDS_append_spitz =  " kernel-module-snd-soc-spitz" and module_autoload_snd-soc-spitz_spitz = "snd-soc-spitz"
May 30 08:21:22 <ant_work> I have to find out which modules are automatically put in the image and why
May 30 08:21:56 <ant_work> (note this is not core-image-minimal, it's -base)
May 30 08:52:02 <bluelightning> right, this does need to be done manually
May 30 08:52:15 <bluelightning> however in the machine conf you shouldn't need _append_spitz
May 30 08:52:22 <bluelightning> just set it with =
May 30 08:52:43 <bluelightning> it's a machine-specific variable being set in the definitively machine specific place in the configuration :)
May 30 09:05:12 <ant_work> right
May 30 09:55:09 <ant_work> it's just I've started with a common MACHINE_EXTRA_RRECOMMENDS
May 30 09:56:30 <ant_work> now and then I doubt about the usefulness of zaurus.inc...most vars are overriden per-machine
May 30 10:02:01 <ant_work> it was needed long ago to standardize  when we had separate maintainers
May 30 10:04:44 <bluelightning> well, I think we're pretty much free to make cleanups where they make sense
May 30 10:12:47 <ant_work> I'm thinking we should add a machine feature for MTD
May 30 10:13:14 <ant_work> atm the drivers are compiled-in but still
May 30 10:18:26 <bluelightning> what would that control?
May 30 10:51:28 <ant_work> smthg like MACHINE_EXTRA_RDEPENDS = "mtd-utils mtd-utils-jffs2 mtd-utils-ubifs"
**** ENDING LOGGING AT Fri May 31 02:59:58 2013