linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by Deepti Kalakeri

Hello All, As part of greater Continuous Integration (CI) efforts at Linaro, the Infrastructure Team is tasked to develop and maintain a jenkins based, versatile service run in the cloud that will drive the build part of the continuous integration loop for engineering components. After an intense 11.09 cycle focused on developing a solution for doing large scale kernel CI building and testing, we are pleased to announce that the Linaro CI build service is now available for wider beta testing for L inaro engineering teams. If you are interested in trying out this service or if you have a kernel tree/defconfig that you would like to be continuously built on Linaro CI and tested in Linaro's LAVA lab, please get in touch with me and the infrastructure team, to discuss your steps to get started. Expect more updates and information from the Linaro CI front as we proceed. In the meantime visit the links below: 1. The Linaro CI Build service + https://ci.linaro.org 2. Details and background on the CI build service and how to request a new job + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI 3. The list of the existing Kernel CI builds that are currently built and tested on daily basis can be found at + https://ci.linaro.org/jenkins/view/All%20CI/ 4. Daily tracking your Kernel CI build results is explained here + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI#Monitoring_Build_F… 5. Daily tracking your Kernel CI runtime results is explained there + https://wiki.linaro.org/Platform/Infrastructure/LinaroCI#Finding_Test_Resul… 6. Future development ideas for the service + https://launchpad.net/linaro-ci/+milestone/backlog The 11.09 release is just a first step and more exciting and advanced continuous integration features are on their way. Linaro CI has already started showing results by finding bugs during our development/setup phase of Linaro CI build service. Visit our backlog milestone [6] in launchpad to get an up to date overview of ideas and deliverables in our planning pipeline. Here some samples of topics we discussed: 1. Extend the kernel CI effort by adopting further defconfigs and tracked trees and verification of the kernel builds on different kinds of boards in the LAVA lab. 2. Develop and host a one stop place for kernel CI tracking on LAVA dashboard, where engineers can continuously monitor their components for build and runtime failures. 3. Add support for adhoc kernel builds. This will allow kernel tree maintainers to try out pull requests and local developments in LAVA using a simple one time submit feature. 4. Improve CI support for downstream kernel maintainers (e.g. ubuntu, android). The goal is to make continuous downstream merging and integration of highly active upstream repositories very easy and efficient. The beginning of many milestones has just begin with a small step and your feedback will be of immense value in achieving the future milestones. Thanks and Regards, Deepti Infrastructure Team Member, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

14 years, 10 months

Multimedia Glossary and Tutorials

by Kurt Taylor

Hello all, Here is a link that you might find useful if you get stuck on a multimedia term or acronym. There is also a tutorials section which I will continue adding to. Feel free to add to this page as you see fit: https://wiki.linaro.org/WorkingGroups/Middleware/Multimedia/Glossary -- Kurt Taylor (irc krtaylor) Linaro Multimedia Team Lead Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM SoCs Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> | Twitter<http://twitter.com/#%21/linaroorg>| Blog <http://www.linaro.org/linaro-blog/>

14 years, 10 months

[ACTIVITY] Android Platform Team 2011-09-19 to 2011-09-25

by Tony Mansson

Key Points for wider discussion =============================== * 2nd 11.09 Android Release Candidate is out: https://android-build.linaro.org/builds/~linaro-android/staging-snowball-11… Team Highlights =============================== * 4460 bringup with Linaro TI LT kernel done. * Ethernet Configuration Manager is in all builds, which means Ethernet now works on Panda, Staging Panda, Beagle, Beagle xM, Staging Snowball. * More test cases added to lava-android-test. * "Booting the Igloo Android A Release with Linaro Tools" document is finished: https://wiki.linaro.org/Platform/Android/Builds/Wip/igloo-snowball * 11.09 Toolchain is integrated. * iMX53 booting and Origen Wi-Fi issue ongoing. * 11.10 planning ongoing. Miscellaneous =============================== * Frans will be on vacation 2011-09-26 to 2011-10-07. * Tony will be away on training all of next week. 2011-10-03 to 2011-10-07. * Chao is off on Friday (2011-09-30) and next Tuesday ( 2011-10-04). Bugs fixed =============================== * #825327, #819723, #850099, #845793 Blueprints: =============================== https://launchpad.net/linaro-android/+milestone/11.09 https://launchpad.net/linaro-android/+milestone/11.10

14 years, 10 months

l-a-m-c issue reported on ask.linaro.org

by Michael Opdenacker

Hi Mattias, FYI, a user is reporting an issue with l-a-m-c on http://ask.linaro.org/questions/191/linaro-image-tools I can't reproduce the problem, and I didn't find any bug in LP matching the error message, but I guess your team should be able to help this guy. Thanks, Michael. -- Michael Opdenacker - Community Manager Linaro, http://linaro.org Cell: +33 621 604 642 IRC: 'opm' in #linaro on irc.freenode.net

14 years, 10 months

[Patch v4 08/11] Touch: DA9052 touchscreen driver

by ashishj3

This driver add support for DA9052 4-wire resistive ADC interfaced touchscreen controller. DA9052 is a MFD therefore this driver depends on DA9052 core driver for core functionalities. Signed-off-by: David Dajun Chen <dchen(a)diasemi.com> Signed-off-by: Ashish Jangam <ashish.jangam(a)kpitcummins.com> --- Changes since v4: - Add string "compile this driver as module" in kconfig - Replace struct da9052_tsi_reg with temp variable - Call schedule_delayed_work() from pen down irq handler - Mask data ready irq in pen up work - Disable IRQs in device close and enable it in device open - Remove set_bit() for ABS X,Y,Pressure as input_set_abs_params() does it Changes since v3: - Remove unrequire type cast - Prefix init code with _devinit - Remove check for workqueue reschedule - tsi_close() to wait for datardy intr completion - Remove seperate workqueue - Move cancel_work_sync to tsi_close() - Check for drv data before tsi priv data allocation Changes since v2: - Replace kthreads with workqueue - Remove kfifos - Taken care for bus type - Replace da9052_set/clear function with da9052_reg_update - Add open and close functionality --- drivers/input/touchscreen/Kconfig | 10 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/da9052_tsi.c | 374 ++++++++++++++++++++++++++++++++ 3 files changed, 385 insertions(+), 0 deletions(-) create mode 100755 drivers/input/touchscreen/da9052_tsi.c diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig index cabd9e5..e4e3341 100644 --- a/drivers/input/touchscreen/Kconfig +++ b/drivers/input/touchscreen/Kconfig @@ -144,6 +144,16 @@ config TOUCHSCREEN_DA9034 Say Y here to enable the support for the touchscreen found on Dialog Semiconductor DA9034 PMIC. +config TOUCHSCREEN_DA9052 + tristate "Dialog DA9052 TSI" + depends on PMIC_DA9052 + help + Say y here to support the touchscreen found on + Dialog Semiconductor DA9052 PMIC + + To compile this driver as a module, choose M here: the + module will be called da9052-tsi. + config TOUCHSCREEN_DYNAPRO tristate "Dynapro serial touchscreen" select SERIO diff --git a/drivers/input/touchscreen/Makefile b/drivers/input/touchscreen/Makefile index 282d6f7..a4aeb25 100644 --- a/drivers/input/touchscreen/Makefile +++ b/drivers/input/touchscreen/Makefile @@ -18,6 +18,7 @@ obj-$(CONFIG_TOUCHSCREEN_BITSY) += h3600_ts_input.o obj-$(CONFIG_TOUCHSCREEN_BU21013) += bu21013_ts.o obj-$(CONFIG_TOUCHSCREEN_CY8CTMG110) += cy8ctmg110_ts.o obj-$(CONFIG_TOUCHSCREEN_DA9034) += da9034-ts.o +obj-$(CONFIG_TOUCHSCREEN_DA9052) += da9052_tsi.o obj-$(CONFIG_TOUCHSCREEN_DYNAPRO) += dynapro.o obj-$(CONFIG_TOUCHSCREEN_HAMPSHIRE) += hampshire.o obj-$(CONFIG_TOUCHSCREEN_GUNZE) += gunze.o diff --git a/drivers/input/touchscreen/da9052_tsi.c b/drivers/input/touchscreen/da9052_tsi.c new file mode 100755 index 0000000..e7418b3 --- /dev/null +++ b/drivers/input/touchscreen/da9052_tsi.c @@ -0,0 +1,374 @@ +/* + * TSI driver for Dialog DA9052 + * + * Copyright(c) 2011 Dialog Semiconductor Ltd. + * + * Author: David Dajun Chen <dchen(a)diasemi.com> + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License as published by the + * Free Software Foundation; either version 2 of the License, or (at your + * option) any later version. + * + */ +#include <linux/module.h> +#include <linux/input.h> +#include <linux/delay.h> +#include <linux/platform_device.h> + +#include <linux/mfd/da9052/reg.h> +#include <linux/mfd/da9052/da9052.h> + +#define TSI_PEN_DOWN_STATUS 0x40 + +struct da9052_tsi { + struct da9052 *da9052; + struct input_dev *dev; + struct delayed_work ts_pen_work; + int irq_pendwn; + int irq_datardy; +}; + +static int da9052_ts_start(struct da9052_tsi *tsi) +{ + return da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, + 1 << 0, 1 << 0); +} + +static int da9052_ts_stop(struct da9052_tsi *tsi) +{ + return da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, 1 << 0, 0); +} + +static irqreturn_t da9052_ts_pendwn_irq(int irq, void *data) +{ + struct da9052_tsi *tsi = data; + struct da9052 *da9052 = tsi->da9052; + int ret; + + /* Mask PEN_DOWN event and unmask TSI_READY event */ + da9052->events_mask |= DA9052_E_PEN_DOWN; + da9052->events_mask &= ~DA9052_E_TSI_READY; + ret = da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0x80, 0x40); + if (ret < 0) + return IRQ_NONE; + + da9052_ts_start(tsi); + + input_report_key(tsi->dev, BTN_TOUCH, 1); + input_sync(tsi->dev); + + schedule_delayed_work(&tsi->ts_pen_work, HZ/50); + + return IRQ_HANDLED; +} + +static int da9052_ts_read(struct da9052_tsi *tsi) +{ + int ret = 0; + u16 x, y, z; + u8 v; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_X_MSB_REG); + if (ret < 0) + goto exit; + + x = (u16) ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_Y_MSB_REG); + if (ret < 0) + goto exit; + + y = (u16) ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_Z_MSB_REG); + if (ret < 0) + goto exit; + + z = (u16) ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_LSB_REG); + if (ret < 0) + goto exit; + + v = (u8) ret; + + x = ((x << 2) & 0x3fc) | (v & 0x3); + y = ((y << 2) & 0x3fc) | ((v & 0xc) >> 2); + z = ((z << 2) & 0x3fc) | ((v & 0x30) >> 4); + + input_report_abs(tsi->dev, ABS_X, x); + input_report_abs(tsi->dev, ABS_Y, y); + input_report_abs(tsi->dev, ABS_PRESSURE, z); + input_report_key(tsi->dev, BTN_TOUCH, 1); + input_sync(tsi->dev); + +exit: + return ret; +} + +static irqreturn_t da9052_ts_datardy_irq(int irq, void *data) +{ + struct da9052_tsi *tsi = data; + + da9052_ts_read(tsi); + return IRQ_HANDLED; +} + +static void da9052_ts_pen_work(struct work_struct *work) +{ + struct da9052_tsi *tsi = container_of(work, struct da9052_tsi, + ts_pen_work.work); + struct input_dev *ip_dev = tsi->dev; + struct da9052 *da9052 = tsi->da9052; + int ret; + + ret = da9052_reg_read(tsi->da9052, DA9052_TSI_LSB_REG); + if (ret < 0) + return; + + if (ret & TSI_PEN_DOWN_STATUS) /* Pen Down */ + schedule_delayed_work(&tsi->ts_pen_work, HZ/50); + else { + /* Pen UP */ + da9052_ts_stop(tsi); + + /* Mask TSI_READY event and unmask PEN_DOWN event */ + da9052->events_mask |= DA9052_E_TSI_READY; + da9052->events_mask &= ~DA9052_E_PEN_DOWN; + da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0x40, 0x80); + + /* Report Pen UP */ + input_report_abs(ip_dev, ABS_PRESSURE, 0); + input_report_key(ip_dev, BTN_TOUCH, 0); + input_sync(ip_dev); + } +} + +static int __devinit da9052_ts_configure_gpio(struct da9052 *da9052) +{ + int ret; + + ret = da9052_reg_update(da9052, DA9052_GPIO_2_3_REG, 0x30, 0); + if (ret < 0) + return ret; + + ret = da9052_reg_update(da9052, DA9052_GPIO_4_5_REG, 0x33, 0); + if (ret < 0) + return ret; + + ret = da9052_reg_update(da9052, DA9052_GPIO_6_7_REG, 0x33, 0); + + return ret; +} + +static int __devinit da9052_configure_tsi(struct da9052_tsi *tsi) +{ + ssize_t ret; + struct da9052 *da9052 = tsi->da9052; + + ret = da9052_ts_configure_gpio(tsi->da9052); + if (ret < 0) + return ret; + + /* Measure TSI sample every 1ms */ + ret = da9052_reg_update(tsi->da9052, DA9052_ADC_CONT_REG, + 1 << 6, 1 << 6); + if (ret < 0) + return ret; + + /* TSI_DELAY: 3 slots, TSI_SKIP: 0 slots, TSI_MODE: XYZP */ + ret = da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, 0xFC, 0xC0); + if (ret < 0) + return ret; + + /* Mask PEN_DOWN and TSI_READY events */ + da9052->events_mask |= DA9052_E_PEN_DOWN | DA9052_E_TSI_READY; + ret = da9052_reg_update(da9052, DA9052_IRQ_MASK_B_REG, 0, 0xc0); + if (ret < 0) + return ret; + + /*Supply TSIRef through LD09 */ + ret = da9052_reg_write(tsi->da9052, DA9052_LDO9_REG, 0x59); + + return ret; +} + +static int da9052_ts_input_open(struct input_dev *input_dev) +{ + struct da9052_tsi *tsi = input_get_drvdata(input_dev); + int ret; + + /* Unmask PEN_DOWN and TSI_READY events */ + tsi->da9052->events_mask &= ~(DA9052_E_PEN_DOWN | DA9052_E_TSI_READY); + ret = da9052_reg_update(tsi->da9052, DA9052_IRQ_MASK_B_REG, 0xc0, 0); + if (ret < 0) + return ret; + + /* Enable Pen Detect Circuit */ + return da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, + 1 << 1, 1 << 1); +} + +static void da9052_ts_input_close(struct input_dev *input_dev) +{ + struct da9052_tsi *tsi = input_get_drvdata(input_dev); + + /* Mask PEN_DOWN and TSI_READY events */ + tsi->da9052->events_mask |= DA9052_E_PEN_DOWN | DA9052_E_TSI_READY; + da9052_reg_update(tsi->da9052, DA9052_IRQ_MASK_B_REG, 0, 0xc0); + + cancel_delayed_work_sync(&tsi->ts_pen_work); + + da9052_ts_stop(tsi); + + /* Disable Pen Detect Circuit */ + da9052_reg_update(tsi->da9052, DA9052_TSI_CONT_A_REG, 1 << 1, 0); +} + +static int __devinit da9052_ts_probe(struct platform_device *pdev) +{ + struct da9052_tsi *tsi; + struct input_dev *input_dev; + struct da9052 *da9052; + int ret; + + da9052 = dev_get_drvdata(pdev->dev.parent); + if (da9052 == NULL) + return -EINVAL; + + tsi = kzalloc(sizeof(struct da9052_tsi), GFP_KERNEL); + if (!tsi) + return -ENOMEM; + + input_dev = input_allocate_device(); + if (!input_dev) { + dev_err(tsi->da9052->dev, "Failed to allocate input device\n"); + ret = -ENOMEM; + goto err_mem; + } + + INIT_DELAYED_WORK(&tsi->ts_pen_work, da9052_ts_pen_work); + + tsi->da9052 = da9052; + + input_dev->id.version = 0x0101; + input_dev->id.vendor = 0x15B6; + input_dev->id.product = 0x9052; + input_dev->id.bustype = tsi->da9052->bustype; + input_dev->name = "Dialog DA9052 TouchScreen Driver"; + input_dev->dev.parent = &pdev->dev; + input_dev->open = da9052_ts_input_open; + input_dev->close = da9052_ts_input_close; + __set_bit(EV_ABS, input_dev->evbit); + __set_bit(EV_KEY, input_dev->evbit); + __set_bit(BTN_TOUCH, input_dev->keybit); + + input_set_abs_params(input_dev, ABS_X, 0, 1023, 0, 0); + input_set_abs_params(input_dev, ABS_Y, 0, 1023, 0, 0); + input_set_abs_params(input_dev, ABS_PRESSURE, 0, 1023, 0, 0); + + tsi->dev = input_dev; + input_set_drvdata(input_dev, tsi); + + tsi->irq_pendwn = platform_get_irq_byname(pdev, "PENDWN"); + if (tsi->irq_pendwn < 0) { + ret = tsi->irq_pendwn; + goto err_input; + } + + ret = request_threaded_irq(tsi->da9052->irq_base + tsi->irq_pendwn, + NULL, da9052_ts_pendwn_irq, + IRQF_TRIGGER_LOW | IRQF_ONESHOT, + "PENDWN", tsi); + if (ret < 0) { + dev_err(tsi->da9052->dev, + "Failed to register %s IRQ %d, error = %d\n", "PENDWN", + tsi->da9052->irq_base + tsi->irq_pendwn, ret); + goto err_input; + } + + tsi->irq_datardy = platform_get_irq_byname(pdev, "TSIRDY"); + if (tsi->irq_datardy < 0) { + ret = tsi->irq_datardy; + goto err_pendwn_irq; + } + + ret = request_threaded_irq(tsi->da9052->irq_base + tsi->irq_datardy, + NULL, da9052_ts_datardy_irq, + IRQF_TRIGGER_LOW | IRQF_ONESHOT, + "TSIRDY", tsi); + if (ret < 0) { + dev_err(tsi->da9052->dev, + "Failed to register %s IRQ %d, error = %d\n", "TSIRDY", + tsi->da9052->irq_base + tsi->irq_datardy, ret); + goto err_pendwn_irq; + } + + ret = da9052_configure_tsi(tsi); + if (ret < 0) + goto err_datardy_irq; + + ret = input_register_device(tsi->dev); + if (ret < 0) + goto err_datardy_irq; + + platform_set_drvdata(pdev, tsi); + + return 0; + +err_datardy_irq: + free_irq(tsi->da9052->irq_base + tsi->irq_datardy, tsi); +err_pendwn_irq: + free_irq(tsi->da9052->irq_base + tsi->irq_pendwn, tsi); +err_input: + input_free_device(input_dev); +err_mem: + kfree(tsi); + return ret; +} + +static int __devexit da9052_ts_remove(struct platform_device *pdev) +{ + struct da9052_tsi *tsi = platform_get_drvdata(pdev); + + da9052_reg_write(tsi->da9052, DA9052_LDO9_REG, 0x19); + + free_irq(tsi->da9052->irq_base + tsi->irq_pendwn, tsi); + free_irq(tsi->da9052->irq_base + tsi->irq_datardy, tsi); + + input_unregister_device(tsi->dev); + + platform_set_drvdata(pdev, NULL); + + kfree(tsi); + + return 0; +} + +static struct platform_driver da9052_tsi_driver = { + + .probe = da9052_ts_probe, + .remove = __devexit_p(da9052_ts_remove), + .driver = { + .name = "da9052-tsi", + .owner = THIS_MODULE, + }, +}; + +static int __init da9052_ts_init(void) +{ + return platform_driver_register(&da9052_tsi_driver); +} +module_init(da9052_ts_init); + +static void __exit da9052_ts_exit(void) +{ + platform_driver_unregister(&da9052_tsi_driver); +} +module_exit(da9052_ts_exit); + +MODULE_DESCRIPTION("Touchscreen driver for Dialog Semiconductor DA9052"); +MODULE_AUTHOR("David Dajun Chen <dchen(a)diasemi.com>"); +MODULE_LICENSE("GPL"); +MODULE_ALIAS("platform:da9052-tsi");

14 years, 10 months

The Future of Meego

by Joey Stanford

In case you missed the news... MeeGo to be folded into Linux-based Tizen OS, slated to arrive in 2012 http://www.engadget.com/2011/09/28/meego-to-be-folded-into-linux-based-tize… and someone's created an interesting picture-based commentary on that announcement http://img41.imageshack.us/img41/3070/tizen.jpg Joey

14 years, 10 months

wiki feedback on new front page

by Andy Doan

Michael and I were tasked with making the front page of the Linaro wiki a little more developer focused and offloading some of the other information to the main website, linaro.org. We've put together a prototype page and would like to get some feedback before making the real switch: https://wiki.linaro.org/AndyDoan/Sandbox/FrontPage thanks, -andy

14 years, 10 months

Porter boxes offline 26/27 September

by James Westby

Hi, IS would like to upgrade the porter boxes from maverick to natty, which should make them more stable. This will require a reboot, and the upgrade may cause issues for some tasks, so please be aware and plan accordingly. The plan is to start with jenipapo at 1900UTC on Sept 26. The others (guinep, habitat) will be done in the hours following that, or starting at the same time on Sept 27 if they can't all be done in the first block. Thanks, James

14 years, 10 months

Making it easier for Linaro users to help themselves

by Dave Martin

Hi all, Over recent months I've had a steady stream of comments from external people trying to use the Linaro deliverables about the difficulty of getting started, understanding what Linaro produces and how to use it. My experience with supporting users is that using and making sense of the linaro output is often not nearly as easy as we would like to believe. Part of the problem seems to be that we may not do a good job of passing on the knowledge and understanding necessary to allow users to help themselves. Is it worth a session at Linaro Connect to discuss how we could improve the situation? This probably falls in the "community" area. Key things to discuss might be: * identifying and understanding our audience * providing the "missing manual" (what knowledge do we tend to assume in linaro that our audience may lack) * wiki ownership and maintenance (how do we _manage_ the information we produce to maximise its relevance and usefulness) (This includes identifying stale/obsolete information, removing duplicates and providing useful indices, contents lists and introductory material.) Ideally, we should get some users external to linaro to attend and/or provide input. Cheers ---Dave

14 years, 10 months

Reboot not working with the newly built upstream custom kernel

by Deepti Kalakeri

Hello, I am trying to build the upstream kernel like linux-linaro-3.0, linux(linus), linux-next, linux-arm-soc for next builds with omap2plus defconfig, Create a kernel debian package and use this debian package to verify the build. The builds are enabled with ext3 file system. The scripts that is used to build the kernel for example is http://bazaar.launchpad.net/~linaro-infrastructure/linaro-ci/lci-build-tool… . The builddeb used contains modifications submitted to work for cross compilation and the changes are available at http://permalink.gmane.org/gmane.linux.linaro.devel/7443. Other than that there is no hand made changes to any files. An example hwpack that I created using the linaro-hwpack-replace can be downloaded from http://ci.linaro.org/kernel_hwpack/panda/hwpack_linaro-panda_20110927-0741_… . This consists of the kernel debian package built from linux-linaro-3.0 with omap2 defconfig to work on a panda board. [PS: linaro-hwpack-replace which is part of the linaro-image-tools is a tool that replaces the old kernel debian package in a given hwpack with the supplied kernel debian package ] I see that the kernel builds successfully, and the hwpack containing this newly built kernel debian package boots fine on the boards, but it fails to execute the reboot command and it hangs with the following message: ################################################################# The system is going down for reboot NOW! root@linaro-nano:~# init: tty4 main process (3205) killed by TERM signal init: tty5 main process (3211) killed by TERM signal init: auto-serial-console main process (3213) killed by TERM signal init: tty2 main process (3215) killed by TERM signal init: tty3 main process (3218) killed by TERM signal init: tty6 main process (3224) killed by TERM signal init: openvt main process (3276) killed by TERM signal init: plymouth-upstart-bridge main process (3341) terminated with status 1 [ OK ]ing all remaining processes to terminate... [ OK ] processes ended within 1 seconds.... [ OK ]onfiguring network interfaces... [ OK ]ctivating swap... [ OK ]ounting weak filesystems... * Will now restart [ 2216.347167] Restarting system. ################################################################# The board needs to be hard reset to boot back to the system. Has anyone seen this issue before, or do you suspect some problem with the kernel I built ?? I would be very thankful if someone can help me triage the problem. Thanks and Regards, Deepti.

14 years, 10 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev