Hi, Re-CCing the list so everyone else can see.
A quick comparison of the beagle and panda lists using "diff" shows exactly what I was expecting. Slightly different X configuration (omap+evdev vs keyboard+mouse+evdev+fbdev) and a massively different kernel configuration: the beaglebone image has 39 kernel module packages whereas the pandaboard has 2141. The Panda image appears to be pulling in every kernel module, instead of the just the ones you want. This is probably meta-ti's fault. Ross On 16 April 2013 15:52, Edward Vidal <vidal.devel...@gmail.com> wrote: > Ross, > I attaching the pkgslist if it will help. Are there anything else that I > can provide? > Thanks > Should these be sent to the mailing list? > > > beagleboard_pkglist041513<https://docs.google.com/file/d/0B11sthVgwfufY0l1Q05TaUJCblE/edit?usp=drive_web> > > > > On Tue, Apr 16, 2013 at 8:41 AM, Burton, Ross <ross.bur...@intel.com>wrote: > >> On 16 April 2013 15:35, Edward Vidal <vidal.devel...@gmail.com> wrote: >> > They all use EXTRA_IMAGE_FEATURES = "debug-tweaks tools-sdk".in >> local.conf >> > Something within the build is deciding which pkgs get installed between >> > different builds. I would expect several different RPMs but not >> hundreds as >> > was the case. >> >> Different BSPs can cause different packages to get pulled in, but >> without seeing full package lists from each of the images nobody can >> really comment on what is causing the differences. >> >> Maybe the meta-ti kernels are building more options as modules in >> their own packages? Maybe you've found a bug in the locale package >> selection? It's impossible to say without actually seeing the package >> lists. >> >> Ross >> > >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
