[Angstrom-devel] OE Changelog since 2013-10-13 until 2013-10-20
Changelog since 2013-10-13 until 2013-10-20. Projects included in this report: bitbake: git://git.openembedded.org/bitbake openembedded-core: git://git.openembedded.org/openembedded-core meta-openembedded: git://git.openembedded.org/meta-openembedded meta-angstrom: git://github.com/Angstrom-distribution/meta-angstrom.git meta-arago: git://arago-project.org/git/meta-arago.git meta-beagleboard: git://github.com/beagleboard/meta-beagleboard.git meta-browser: git://github.com/OSSystems/meta-browser.git meta-bug: git://github.com/buglabs/meta-bug.git meta-chicken: git://github.com/OSSystems/meta-chicken meta-efikamx: git://github.com/kraj/meta-efikamx.git meta-ettus: http://github.com/koenkooi/meta-ettus.git meta-fsl-arm: git://git.yoctoproject.org/meta-fsl-arm meta-fsl-arm-extra: git://github.com/Freescale/meta-fsl-arm-extra.git meta-fsl-ppc: git://git.yoctoproject.org/meta-fsl-ppc meta-guacamayo: git://github.com/Guacamayo/meta-guacamayo.git meta-gumstix: git://github.com/gumstix/meta-gumstix.git meta-gumstix-community: git://gitorious.org/schnitzeltony-oe-meta/meta-gumstix-community.git meta-handheld: git://git.openembedded.org/meta-handheld meta-igep: http://github.com/ebutera/meta-igep.git meta-intel: git://git.yoctoproject.org/meta-intel meta-ivi: git://git.yoctoproject.org/meta-ivi meta-java: git://github.com/woglinde/meta-java meta-kde: git://gitorious.org/openembedded-core-layers/meta-kde.git meta-micro: git://git.openembedded.org/meta-micro meta-mono: git://git.yoctoproject.org/meta-mono.git meta-netbookpro: git://github.com/tworaz/meta-netbookpro meta-nslu2: git://github.com/kraj/meta-nslu2 meta-opie: git://git.openembedded.org/meta-opie meta-qt3: git://git.yoctoproject.org/meta-qt3 meta-qt5: git://github.com/meta-qt5/meta-qt5.git meta-slugos: git://github.com/kraj/meta-slugos meta-systemd: git://git.yoctoproject.org/meta-systemd meta-raspberrypi: git://github.com/djwillis/meta-raspberrypi.git meta-smartphone: http://git.shr-project.org/repo/meta-smartphone.git meta-ti: git://git.yoctoproject.org/meta-ti meta-webos: git://github.com/openwebos/meta-webos.git meta-xilinx: git://git.yoctoproject.org/meta-xilinx meta-yocto: git://git.yoctoproject.org/meta-yocto openembedded: git://git.openembedded.org/openembedded Changelog for bitbake: Alexandru DAMIAN (3): toaster: add toaster code to bitbake toaster: adding frameworks for the Simple UI toaster: add Toaster UI interface Cristiana Voicu (1): hob: Hob should ask for ports only when Manual proxy is selected Olof Johansson (1): monitordisk: lower inode check warning to note Paul Eggleton (1): siggen: handle recipe path changes in siginfo files Richard Purdie (4): bitbake: Update post 1.20 to development version cooker/command: Add error state for the server and use for pre_serve errors bitbake: bitbake: bb: Drop deprecated functions utils: Don't show stack traces for BBHandledException Changelog for openembedded-core: Anders Roxell (1): ltp: update to new release 20130904 Bruce Ashfield (1): kernel: restore scripts in the sysroot Chase Maupin (1): udev: update local rules for new touchscreen device Chen Qi (1): device_table-minimal.txt: change group of /dev/hda back to disk Cristiana Voicu (1): separatebuilddir: remove entries for imake and xorg-cf-files Darren Hart (2): wic: Force lba off for FAT16 partitions wic: Check for external modules David Nyström (9): beecrypt: Add nativesdk in BBCLASSEXTEND popt: Add nativesdk in BBCLASSEXTEND icu: Add nativesdk in BBCLASSEXTEND attr: Add nativesdk in BBCLASSEXTEND acl: Add nativesdk in BBCLASSEXTEND rpmresolve: Add nativesdk in BBCLASSEXTEND smartpm: Add nativesdk in BBCLASSEXTEND ossp-uuid: Add nativesdk in BBCLASSEXTEND file: Add nativesdk in BBCLASSEXTEND Diego Rondini (1): libav: Add libswscale to PACKAGES_DYNAMIC Felipe F. Tonello (1): update-rc: Stop and remove service if updating package Jack Mitchell (2): grub: add patch to support 256 byte inodes crond: remove UID check in init script Jeffrey C Honig (1): initscripts: insure checkroot.sh runs before anything writing to the file Jonathan Liu (1): qt4: add upstream QTBUG-31579 patch for QPainter regression Laurentiu Palcu (10): byacc: upgrade to 20130925 xkeyboard-config: upgrade to 2.10.1 xauth: upgrade to 1.0.8 xf86-input-evdev: upgrade to 2.8.2 libdrm: upgrade to 2.4.47 xset: upgrade to 1.2.3 xf86-video-intel: upgrade to 2.21.15 xinput: upgrade to 1.6.1 xprop: upgrade to 1.2.2 xf86-video-fbdev: upgrade to 0.4.4 Marko Lindqvist (2): automake: unhardcode version number automake: update to upstream version 1.13.4 Martin Jansa (3): matchbox-wm: Add dependency on libxfixes and libxcursor telepathy-mission-control: Add PACKAGECONFIG for upower and connectivity bitbake.conf: Remove double slash from PATH_prepend and PKG_CONFIG_DIR Maxin
[Angstrom-devel] what file kernel configuration really uses?
Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file. I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled. I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION= 1.17.0 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.12 TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon oe_sitecno oe_emergence = unknown:unknown meta-angstrom = angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee These setting give kernel 3.8.11. Is there something I have missed? Thanks in advance, Matti ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
The defconfig file is present in the meta-layers and copied to the kernel build directory. It is used to create the .config file in the kernel source directory. If you modify the .config file, you will see changes in the kernel file. if you modify the defconfig file in the build directory, nothing happens. I typically change the .config and copy the result to the defconfig in the meta-layer. Then I rebuild from scratch. bitbake -c cleansstate virtual/kernel bitbake virtual/kernel Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com: Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file. I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled. I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION= 1.17.0 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.12 TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon oe_sitecno oe_emergence = unknown:unknown meta-angstrom = angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee These setting give kernel 3.8.11. Is there something I have missed? Thanks in advance, Matti ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
Thanks Ulf, It seems to work in that way. However, I'm a bit surprised that it works so as as I mentioned above all the procedures - patching defconfig in the kernel build directory, providing defconfig in metadata and providing configuration fragments as described in the Yocto Kernel development manual - give the same outcome in the defconfig at the kernel build directory. What command do you use when you are using .config directly? My experience is that when I for instance run: bitbake -f -c configure virtual/kernel after bitbake -f -c patch virtual/kernel bitbake executes again do_patch, that at least rides over defconfig if I edited that. In fact it seems that bitbake -c config runs always do_patch even if previous command was patch and no modifications were in between. BR, Matti 2013/10/22 Ulf Samuelsson angstrom-...@emagii.com The defconfig file is present in the meta-layers and copied to the kernel build directory. It is used to create the .config file in the kernel source directory. If you modify the .config file, you will see changes in the kernel file. if you modify the defconfig file in the build directory, nothing happens. I typically change the .config and copy the result to the defconfig in the meta-layer. Then I rebuild from scratch. bitbake -c cleansstate virtual/kernel bitbake virtual/kernel Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com: Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file. I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled. I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION= 1.17.0 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.12 TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon oe_sitecno oe_emergence = unknown:unknown meta-angstrom = angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee These setting give kernel 3.8.11. Is there something I have missed? Thanks in advance, Matti ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
On 2013-10-22 17:20, matti kaasinen wrote:
Thanks Ulf,
It seems to work in that way. However, I'm a bit surprised that it works so
as as I mentioned above all the procedures -
patching defconfig in the kernel build directory, providing defconfig in
metadata and providing configuration fragments as described in the Yocto
Kernel development manual - give the same outcome in the defconfig at the
kernel build directory.
What is happening is dependent on the kernel recipe.
Typically, you find that linux.inc does the job,
and in do_configure, which is run when you do:
bitbake -c configure virtual/kernel
${WORKDIR}/defconfig is altered to ensure it makes sense.
A lot of options are simply deleted.
${S}/.config is created as an empty file and then the deleted options
are added with a proper value.
At the end, defconfig is appended to the ${S}/.config
so when you run
bitbake -c configure virtual/kernel
both ${WORKDIR}/defconfig and ${S}/.config are changed.
/Ulf
What command do you use when you are using .config directly? My experience
is that when I for instance run:
bitbake -f -c configure virtual/kernel
after
bitbake -f -c patch virtual/kernel
bitbake executes again do_patch, that at least rides over defconfig if I
edited that.
In fact it seems that bitbake -c config runs always do_patch even if
previous command was patch and no modifications were in between.
BR,
Matti
2013/10/22 Ulf Samuelsson angstrom-...@emagii.com
The defconfig file is present in the meta-layers and copied to the
kernel build directory.
It is used to create the .config file in the kernel source directory.
If you modify the .config file, you will see changes in the kernel file.
if you modify the defconfig file in the build directory, nothing happens.
I typically change the .config and copy the result to the defconfig in
the
meta-layer. Then I rebuild from scratch.
bitbake -c cleansstate virtual/kernel
bitbake virtual/kernel
Best Regards
Ulf Samuelsson
u...@emagii.com
+46 (722) 427 437
22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com:
Hi!
What configuration kernel build really uses - .config or defconfig?
It seems, that menuconfig (bitbake -c menuconfig ) use always .config
file.
I have problem that changes in defconfig are not seen in kernel features.
Instead they seem the same that are in .config file
I have tried configuration fragments, patches and providing defconfig
directly.
They all seem to give proper defconfig. However, menuconfig never provide
the changed configurations. Also, for instance when I try to configure HW
EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH.
omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled.
I've been workin on beaglebone variant - layer over beaglebone.
Build Configuration:
BB_VERSION= 1.17.0
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = beaglebone
DISTRO= angstrom
DISTRO_VERSION= v2012.12
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
oe_sitecno
oe_emergence = unknown:unknown
meta-angstrom =
angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee
These setting give kernel 3.8.11.
Is there something I have missed?
Thanks in advance,
Matti
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] USB hotplugging on Beaglebone Black non-functional in master branch
On 2013-10-18 10:36, Koen Kooi wrote:
Op 18 okt. 2013, om 09:27 heeft Ulf Samuelsson angstrom-...@emagii.com het
volgende geschreven:
I have built the cloud9-gnome-image configured for beaglebone
using the master branch of Angstrom and loaded it on a Beaglebone Black.
The Beaglebone Black has a 5V/2A power supply.
The USB hotplugging seems to not work.
Know bug, pester TI to fix it.
When I remove something from the beaglebone USB host connector I get:
musb_stage0_irq 790: unhandled DISCONNECT transition (a_idle)
What I can see from the code, is that there is only one way to enter
OTG_STATE_A_IDLE-
- if you get an interrupt and the MUSB_INTR_SESSREQ flag is set
Then this mode is set:
musb-xceiv-state = OTG_STATE_A_IDLE;
AFAIK, I.E, it is now an idle OTG peripheral (not a host)
Havent looked through everything yet, but I am yet to find a place where
you exit this state.
If the driver is in this state, then basically every event gets ignored.
In musb_core.c there is no place where
switch(musb-xceiv-state)
has a
case OTG_STATE_A_IDLE: ...
There is a CONFIG_USB_GADGET_MUSB_HDRC which is clear,
If this means that the HDRC can work in OTG mode switching between host
and device,
and the CONFIG item is unchecked, then you should never be in a
peripheral state, right?
The symptom occur when the driver handles a disconnect interrupt.
It falls through to the default, and you get the error
if ((int_usb MUSB_INTR_DISCONNECT) !musb-ignore_disconnect) {
DEV_DBG(musb-controller, DISCONNECT (%s) as %s, devctl %02x\n,
otg_state_string(musb-xceiv-state),
MUSB_MODE(musb), devctl);
handled = IRQ_HANDLED;
switch (musb-xceiv-state) {
case OTG_STATE_A_HOST:
case OTG_STATE_A_SUSPEND:
usb_hcd_resume_root_hub(musb_to_hcd(musb));
musb_root_disconnect(musb);
if (musb-a_wait_bcon != 0)
musb_platform_try_idle(musb, jiffies
+ msecs_to_jiffies(musb-a_wait_bcon));
break;
case OTG_STATE_B_HOST:
/* REVISIT this behaves for real disconnect
* cases; make sure the other transitions from
* from B_HOST act right too. The B_HOST code
* in hnp_stop() is currently not used...
*/
musb_root_disconnect(musb);
musb_to_hcd(musb)-self.is_b_host = 0;
musb-xceiv-state = OTG_STATE_B_PERIPHERAL;
MUSB_DEV_MODE(musb);
musb_g_disconnect(musb);
break;
case OTG_STATE_A_PERIPHERAL:
musb_hnp_stop(musb);
musb_root_disconnect(musb);
/* FALLTHROUGH */
case OTG_STATE_B_WAIT_ACON:
/* FALLTHROUGH */
case OTG_STATE_B_PERIPHERAL:
case OTG_STATE_B_IDLE:
musb_g_disconnect(musb);
break;
default:
WARNING((%s) unhandled DISCONNECT transition\n,
otg_state_string(musb-xceiv-state));
break;
}
}
If I boot without a USB-serial converter and plug it in afterwards, I do not
get a new tty.
If I boot with the USB-serial converter inserted, I get /dev/ttyUSB0.
If I then remove the USB-serial converter /dev/ttyUSB0 remains.
Using the default defconfig in meta-beagleboard which seems to enable
everything USB related.
Anyone seen this?
Is it correct to use the beaglebone, or is beagleboard better?
Which is the most stable branch for the Beaglebone Black?
Whatever the setup-scripts use as default is the most stable and feature rich
config. The machine for beaglebone white and black is 'beaglebone'.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
