looks like this isn't working:
revno: 485committer: Mattias Backman
<mattias.backman(a)linaro.org>branch nick: linaro-image-toolstimestamp:
Thu 2012-01-19 14:44:02 +0100message: Post-release version bump to
2012.01.1
$./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc --dev
origen --system system.tar.bz2 --userdata userdata.tar.bz2 --boot
boot.tar.bz2
I see...
Device Mount point Size
/dev/sda none 114473MB
/dev/sda1 / 109778MB
/dev/sda2 none 4693MB
/dev/sda5 none 4693MB
/dev/sdb none 0MB
/dev/sdc none 7695MB
/dev/sdc1 none 131MB
/dev/sdc2 none 512MB
/dev/sdc3 none 256MB
/dev/sdc4 none 6795MB
/dev/sdc5 none 511MB
/dev/sdc6 none 6282MB
/dev/sdd none 0MB
/dev/sde none 0MB
Are you 100% sure, on selecting [/dev/sdc] (y/n)? y
Checking that no-one is using this disk right now ...
OK
Warning: bad partition start (earliest 1327105)
partition ends on cylinder 1023, beyond the end of the disk
partition ends on cylinder 1023, beyond the end of the disk
Warning: partition 2 does not start at a cylinder boundary
BLKRRPART: Device or resource busy
The command to re-read the partition table failed.
Run partprobe(8), kpartx(8) or reboot your system now,
before using mkfs
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
end: (c,h,s) expected (0,132,8) found (1,127,32)
start: (c,h,s) expected (0,133,8) found (2,1,30)
end: (c,h,s) expected (18,10,23) found (67,127,31)
start: (c,h,s) expected (18,10,25) found (68,0,1)
end: (c,h,s) expected (85,239,56) found (323,127,32)
start: (c,h,s) expected (85,239,57) found (324,0,1)
end: (c,h,s) expected (1020,203,14) found (1023,127,32)
partition ends on cylinder 1023, beyond the end of the disk
start: (c,h,s) expected (85,240,27) found (324,1,1)
end: (c,h,s) expected (119,230,10) found (451,127,32)
start: (c,h,s) expected (119,230,43) found (452,1,1)
end: (c,h,s) expected (187,210,42) found (707,127,32)
start: (c,h,s) expected (187,211,13) found (708,1,1)
end: (c,h,s) expected (1020,203,14) found (1023,127,32)
partition ends on cylinder 1023, beyond the end of the disk
Traceback (most recent call last):
File "./linaro-image-tools/linaro-android-media-create", line 140, in <module>
args.should_create_partitions, args.should_align_boot_part)
File "/workspace/tmp/linaro-image-tools/linaro_image_tools/media_create/partitions.py",
line 69, in setup_android_partitions
get_android_partitions_for_media(media, board_config)
File "/workspace/tmp/linaro-image-tools/linaro_image_tools/media_create/partitions.py",
line 392, in get_android_partitions_for_media
"Could not find boot partition for %s" % media.path)
AssertionError: Could not find boot partition for /dev/sdc
this works:
revno: 484
tags: 2012.01
committer: Mattias Backman <mattias.backman(a)linaro.org>
branch nick: linaro-image-tools
timestamp: Thu 2012-01-19 14:43:59 +0100
message:
Release 2012.01
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
looks like I caught either a bad cold or a light flu - not feeling too well.
I'll be around, but probably sleeping half the day, so don't worry
about me lagging a lot today.
Chances are I'll be back to normal tomorrow, those things never last
too long with me. Linux is a very effective cure for all ailments. ;)
ttyl
bero
Sorry for the wide distribution, but I wasn't sure who all would be
interested.
I spent time over the last month updating the Android monthly toolchain
benchmark process[1] to pull its benchmark data from LAVA tests that are
stored in validation.linaro.org. Here's an example test run[2].
This month's results will be published to the wiki as I normally do.
However, I spent some time last weekend looking at how to handle this on
the validation server as well. I first toyed with trying to do a simple
report plugin. However, it really didn't quite have everything I thought
was needed.
I wound up using the "LAVA kernel CI views" project as a skeleton to
create something for Android. I've got a local prototype that's starting
to do just about everything I want (I'm fighting some issues the the
javascript FLOT library for my charts). I'm attaching a screenshot so
you can get a rough idea.
Before I really invest time, I wanted to get people's thoughts. Some big
questions for me:
1) Is anyone against doing this?
2) The project is currently called "Android Benchmarks". However, I'm
wondering if we should make more of a generic view for "Android".
"Toolchain Benchmarks" could then be one part of this, but we'd have a
spot to add other things if needed/wanted. Due to how projects are shown
across the top of validation.l.o, I think we need pretty concise entries.
3) If the general thought is "this looks okay", then are you guys okay
with targeting it for next month?
[1]
<https://wiki.linaro.org/Platform/Android/AndroidToolchainBenchmarking/2011-…>
[2]
<http://validation.linaro.org/lava-server/dashboard/streams/anonymous/doanac…
>
I had my "Binary Blobs Attack!!!" BoF session accepted at ELC this year:
Most SoC vendors distribute binary blobs with Linux kernel shims.
These binary blobs enable graphics engines, DSPs and other cores on
ARM and other architecture SoCs. These binary blobs tend to be tied to
specific kernel versions which limits unreadability and hackability
and complicates device manufactures, which slows down innovation and
the introduction of new and unique computing devices. This BoF is
aimed at trying to improve this situation with pragmatic steps.
Anyone interested in discussing their experience with binary blob
integration, ideas for making this easier to deal with across
architectures, ways to encourage openness while allowing vendor
differentiation and others interested in a constructive dialog should
attend.
I was wanted to get some feedback from people about their own binary
blob experiences. I think this will be a good place to have a good
productive conversation about this critical issue.
This is ELC so We'll want to cover issues that affect all Linux distros.
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
I've been trying to get accelerated graphics up on imx53 -
unfortunately, causing lots of crashes and little else.
I think the problem is that so far, the only version of the graphics
driver that has been released is for Gingerbread, and it simply
doesn't work with ICS.
However, some of you have much more experience than me with making
sense of binary blobs, so if someone has some spare time, feel free to
look. ;)
I've attached the script I'm using to push the binary driver into
system.tar.bz2.
I've looked at their kernel sources and gralloc tree, and it looks
like we have everything we need there - but of course I could be
wrong.
ttyl
bero
Hi guys.
Please report your status at
https://wiki.linaro.org/Platform/Android/Meetings/2012-01-18 today or early
tomorrow.
The release is coming up, and normally we arrange a 24/3 release duty
schedule around this date. So please check your availability and reply
which times you can sign up for.
||Date || 00:00 - 08:06 UTC || 08:00 - 16:06 UTC || 16:00 - 00:06 UTC ||
|| W Jan 25 || || ||
||
|| T Jan 26 || || ||
||
|| F Jan 27 || || ||
||
I will call for a Post-Mortem meeting at 1300 UTC on Friday the 27:th,
please send me input, good or bad experiences from January 2012 for this
meeting.
Best regards,
/Tony
