I don't want to spam the list, but as there are likely some people who
might want to attend for the benefit of the Linaro effort, I'd like to
announce that there is a Xen Hackathon coming on May 16-17 in Dublin
Ireland.
Details can be found here:
http://blog.xen.org/index.php/2013/03/07/google-hosted-xen-hackathon-may-16…
Thanks,
Russell Pavlicek
Xen Evangelist
Hello to everybody. I'm trying to virtualize Linaro-Android 4 with
qemu-linaro on two different kind of machines :
1) Pandaboard ES running Ubuntu with this kernel :
Linux arm 3.7.2-x6 #1 SMP Sat Jan 12 07:16:37 UTC 2013 armv7l armv7l armv7l
GNU/Linux
2) Samsung XE303C12-A01US Chromebook running CHR Ubuntu with this kernel :
Linux localhost.localdomain 3.4.0-5-chromebook #5-Ubuntu SMP Fri Feb 8
14:54:53 UTC 2013 armv7l armv7l armv7l GNU/Linux
To accomplish the goal I made the experiments with two versions of
qemu-linaro :
1) qemu-linaro-1.3.0-2012.12
2) qemu-linaro 1.4 from the GIT rep
In both cases I configured qemu-linaro with these parameters :
--disable-kvm --disable-tcg-interpreter --enable-curses --enable-sdl
--enable-vnc --disable-debug-tcg --enable-vhost-net
I tried to follow two different kind of tutorials :
1)
http://www.linuxforu.com/2011/06/qemu-for-embedded-systems-development-part…
2)
https://wiki.linaro.org/KenWerner/Sandbox/AndroidQEMU?highlight=%28QEMU%29|…
On the TUTORIAL n. 1:
1) Created a small test program, test.c, with the basic “Hello world”:
#include<stdio.h>
int main(){
printf("Welcome to Open World\n");
}
# gcc test.c -o test
2) Built the Linux kernel for ARM
# tar -jxvf linux-2.6.37.tar.bz2 (but I tried with a lot of other kernel
versions)
# cd linux-2.6.37
# make menuconfig ARCH=arm
# make ARCH=arm uImage -s
# qemu-system-arm -M versatilepb -m 128M -kernel
/home/user/Desktop/linux-2.6.37/arch/arm/boot/uImage
RESULT = black screen inside the qemu-linaro window without error messages
3) Developed a dummy filesystem (hello.c) for testing
#include<stdio.h>
int main(){
while(1){
printf("Hello Open World\n");
getchar();
}
}
# gcc hello.c -static -o hello
4) Created a root filesystem
# echo hello | cpio -o --format=newc > rootfs
5) Testing :
qemu-system-arm -M versatilepb -m 128M -kernel /home/user/Desktop/
linux-2.6.37/arch/arm/boot/uImage -initrd rootfs -append "root=/dev/ram
rdinit=/hello"
RESULT = black screen inside the qemu-linaro window without error messages
On the TUTORIAL n. 2 :
1) Patched :
qemu-linaro-1.3.0-2012.12
with :
sed -i "s/#define INITRD_LOAD_ADDR 0x00d00000/#define INITRD_LOAD_ADDR
0x01d00000/" qemu-linaro-1.3.0-2012.12/hw/arm_boot.c
and also qemu-linaro 1.4 from the GIT rep
with the same patch:
sed -i "s/#define INITRD_LOAD_ADDR 0x00d00000/#define INITRD_LOAD_ADDR
0x01d00000/" qemu-linaro/hw/arm_boot.c
2) wget
http://releases.linaro.org/12.05/android/images/vexpress-ics-gcc47-armlt-tr…
gunzip vexpress-ics-gcc47-armlt-tracking-open.img.gz
sudo kpartx -a vexpress-ics-gcc47-armlt-tracking-open.img
sudo mount /dev/mapper/loop0p1 /mnt -o loop,ro
cp /mnt/uImage /mnt/uInitrd .
sudo umount /mnt
sudo kpartx -d /dev/mapper/loop0p*
dd if=uImage of=vmlinuz skip=64 bs=1
dd if=uInitrd of=initrd.gz skip=64 bs=1
3) Tried to boot Linaro Android 12.05 using qemu-linaro-1.3.0-2012.12 and
also qemu-linaro 1.4 from the GIT rep
on the Pandaboard ES with this :
qemu-system-arm -M vexpress-a9 -m 1024 -smp 1 -snapshot -serial stdio
-no-reboot -kernel vmlinuz -initrd initrd.gz -drive
file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback
--append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init
androidboot.console=ttyAMA0"
and on the Samsung XE303C12-A01US Chromebook with this :
qemu-system-arm -M vexpress-a15 -cpu-cortex-a15 -m 1024 -smp 1 -snapshot
-serial stdio -no-reboot -kernel vmlinuz -initrd initrd.gz -drive
file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback
--append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init
androidboot.console=ttyAMA0"
I've also tried wth :
qemu-system-arm -M vexpress-a15 -cpu cortex-a15 -m 1024 -smp 1 -snapshot
-serial stdio -no-reboot -kernel uImage -initrd uInitrd -drive
file=vexpress-ics-gcc47-armlt-tracking-open.img,if=sd,cache=writeback
--append "console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init
androidboot.console=ttyAMA0"
Also tried with different kind of combinations,like :
-M versatilepb ; -M vexpress-a9 ; -cpu cortex-a9 ; -m 512 ;
but the RESULT is still the smae = black screen inside the qemu-linaro
window without error messages. Any help ?
Instead,debian_lenny_armel_desktop is virtualized very well with
qemu-linaro following this procedure :
a) wget vmlinuz-2.6.32-5-versatile,initrd.img-2.6.32-5-versatile and
debian_lenny_armel_desktop from here :
http://people.debian.org/~aurel32/qemu/armel/
b) tried to virtualize debian_lenny_armel_desktop with :
qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.32-5-versatile -initrd
initrd.img-2.6.32-5-versatile -hda debian_lenny_armel_desktop.qcow2 -append
"root=/dev/sda1"
and it works....
--
Mario.
Greetings,
The current 13.03 schedule has been published on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
llct rebuild is planned later today.
The 13.03 release would be v3.9-rc3 based (tentative).
Please make sure that requests to add new topics (with the git branch to
pull from) have been sent to me, or will be sent as soon as the topic is
ready. I would appreciate a "heads up" like information on the new
topics which are more complex than a couple patches on top of mainline.
For the moment I am aware of the kvm topic only. Anything else?
Thanks,
Andrey
Hi All,
I am not sure whether this is the right forum to ask about my issue. Let me
know. However this is really blocking for me and I do not have anyone at my
work to help me out. Hence asking help -
I am encountering a problem on my target board. Any help is hightly
appreciated.
On my target board which is SOM based on Marvel PXA series, ubiattach
fails.
The rootfs is ubi and comes up. I am trying to mount another partition to
put all my configuration data. Here is the log -
[root]#ubiformat /dev/mtd6 -s 2048 -f ./config.img
ubiformat: mtd6 (nand), size 152305664 bytes (145.2 MiB), 1162 eraseblocks
of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 1161 -- 100 % complete
ubiformat: 1162 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 47 -- 100 % complete
ubiformat: formatting eraseblock 1161 -- 100 % complete
[root]#ubiattach /dev/ubi_ctrl -m 6
UBI: attaching mtd6 to ubi1
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI error: vtbl_check: volume table check failed: record 0, error 9
ubiattach: error!: cannot attach mtd6
error 22 (Invalid argument)
[root]#
Let me know if you need any other information.
Thanks
Mchavva
Add display-timing node parsing to drm fimd and depends on
the display helper patchset at
http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html
It also adds pinctrl support for drm fimd.
changes since v8:
- replaced IS_ERR() with IS_ERR_OR_NULL(),
because devm_pinctrl_get_select_default can return NULL,
If CONFIG_PINCTRL is disabled.
- modified the error log, such that it shall NOT cross 80 column.
- added Acked-by.
changes since v7:
- addressed comments from Joonyoung Shim <jy0922.shim(a)samsung.com>
to remove a unnecessary variable.
changes since v6:
addressed comments from Inki Dae <inki.dae(a)samsung.com> to
separated out the pinctrl functionality and made a separate patch.
changes since v5:
- addressed comments from Inki Dae <inki.dae(a)samsung.com>,
to remove the allocation of 'fbmode' and replaced
'-1'in "of_get_fb_videomode(dev->of_node, fbmode, -1)" with
OF_USE_NATIVE_MODE.
changes since v4:
- addressed comments from Paul Menzel
<paulepanter(a)users.sourceforge.net>, to modify the commit message
changes since v3:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>, to modify
the return values and print messages.
changes since v2:
- moved 'devm_pinctrl_get_select_default' function call under
'if (pdev->dev.of_node)', this makes NON-DT code unchanged.
(reported by: Rahul Sharma <r.sh.open(a)gmail.com>)
changes since v1:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>
Vikas Sajjan (2):
video: drm: exynos: Add display-timing node parsing using video
helper function
video: drm: exynos: Add pinctrl support to fimd
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 33 ++++++++++++++++++++++++++----
1 file changed, 29 insertions(+), 4 deletions(-)
--
1.7.9.5
Hi Guys,
There was mail chain earlier which has discussed this earlier but not sure if
everybody got the final conclusion or not (that's why we are still
posting on linaro-dev).
Please embed linaro-kernel instead of linaro-dev in all your scripts
that you use for
sending patches.
Thanks in Advance.
--
viresh
On Tue, 2013-02-26 at 11:27 -0800, D D wrote:
> Yes, I have tried both the config in the release notes as well as
> configurations to boot A7.
> The configurations to boot A7 hang while executing the BOOTSCRIPT.
> The release note configurations get past that state, boot up the
> kernel and hang as shown in this thread.
> As a first step, I am just trying to get the release note
> configuration working without the hang.
I've just tested out the 13.01 release notes again by following them to
recreate and replacing my TC2's firmware and configure UEFI; and that
works for me to boot a fresh 13.01 Android image from an SD card.
If you aren't having any success with that configuration, then further
things I can suggest are:
1) To make sure any firmware changes have really taken hold, try erasing
all the NOR flash. You can do this from the bootloader Cmd> prompt by
entering "flash" to get a Flash> prompt, then enter 'eraseall'. After
the flash has finished erasing, reboot the board and the firmware will
be reprogrammed again.
2) In case there is an error in the UEFI config (I know it's a bit
fiddly to enter) then you could try the Linaro firmware zip we have for
the forthcoming 13.02 release [1]. This has a UEFI version which ignores
the SD card UUID and so doesn't need reconfiguring every time you create
a new disk image. It also has the benefit that the default boot config
will work without you needing to manually set anything. If you try this
latest UEFI, I suggest you also erase the flash as above, to make extra
sure there is no old config left over from a previous version.
[1] https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&targe…
--
Tixy