<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- name="generator" content="blosxom/2.0" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
  <channel>
    <title>Steve's blog   </title>
    <link>http://blog.einval.com</link>
    <description>The Words of the Sledge</description>
    <language>en</language>

  <item>
    <title>Scanning for assembly code in Free Software packages</title>
    <pubDate>Sat, 30 Mar 2013 03:08:00 +0100</pubDate>
    <link>http://blog.einval.com/2013/03/30#LEG-assembly-scanning</link>
    <description>
&lt;p&gt;In the Linaro Enterprise Group, my task for the last several weeks
was to work through a huge number of packages looking for assembly
code. Why? So that we could identify code that would need porting to
work well on AArch64, the new 64-bit execution state coming to the ARM
world Real Soon Now.&lt;/p&gt;

&lt;p&gt;Working with some Ubuntu and Fedora developers, we generated a list
of packages included in each distribution that seemed to contain
assembly code of some sort. Then I worked through that list, checking
to see:&lt;/p&gt;

&lt;ol type=&quot;a&quot;&gt;
&lt;li&gt;if there was actually any assembly there;&lt;/li&gt;
&lt;li&gt;if so, what it was for, and&lt;/li&gt;
&lt;li&gt;whether it was actually used&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I've written
a &lt;a href=&quot;https://wiki.linaro.org/LEG/Engineering/OPTIM/Assembly&quot;&gt;full
report&lt;/a&gt; about what I found in the scan, and I'll be writing some
more articles based on it shortly.&lt;/p&gt;</description>
  </item>
  <item>
    <title>Ladies. And Fire Engines. And all for Charity!</title>
    <pubDate>Tue, 19 Feb 2013 00:11:00 +0100</pubDate>
    <link>http://blog.einval.com/2013/02/19#jo_fire_engine</link>
    <description>
&lt;p&gt;My lovely wife Jo has signed up for a charity event in May this
year. To help support the
UK &lt;a href=&quot;http://www.firefighterscharity.org.uk/&quot;&gt;Fire Fighters
Charity&lt;/a&gt;, she has committed to a
sponsored &lt;a href=&quot;http://www.firefighterscharity.org.uk/what-you-can-do/fundraise/challenge-events/ldc-beds-cambs&quot;&gt;driving
challenge&lt;/a&gt;. If she can raise enough funds in sponsorship, she'll
get to drive a fire engine, a tractor and (it's rumoured) maybe even a
combine harvester too! I've chipped in some money towards the total
already; I'm sure Jo would love it if some other nice people pledged
on
her &lt;a href=&quot;http://www.justgiving.com/Joanne-McIntyre2&quot;&gt;JustGiving&lt;/a&gt;
page too.&lt;/p&gt;

&lt;p&gt;Go on, it's for a good cause! :-)&lt;/a&gt;</description>
  </item>
  <item>
    <title>Spoiling my vote</title>
    <pubDate>Tue, 13 Nov 2012 23:50:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/11/13#spoiling_my_vote</link>
    <description>
&lt;p&gt;Ever since I passed the age of 18, I've used my legal right in the
UK to vote in every poll I could: local council, British Parliament,
European Parliament and even the messed-up referendum on the
Alternative Vote that we had last year. In each of those cases, I made
a point of considering my available options and I voted accordingly. I
went along and marked my ballot paper in person where possible, or I
filled in a postal vote for the last Westminster election in 2010 as I
was on vacation in Florida when it was held.&lt;/p&gt;

&lt;p&gt;Unfortunately, it seems that my diligence in voting makes me
unusual amongst the UK population these days. The long-term trend for
voter turnout is downwards (as you
can &lt;a href=&quot;http://www.ukpolitical.info/Turnout45.htm&quot;&gt;see&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;However, the latest election that's happening in the UK (well,
England and Wales outside London) this week is for the newly-created
posts of &lt;a href=&quot;http://www.aboutmyvote.co.uk/pcc.aspx&quot;&gt;Police and
Crime Commissioners&lt;/a&gt;. It's a textbook example of
how &lt;strong&gt;not&lt;/strong&gt; to organise an election, as pointed out
eloquently by
the &lt;a href=&quot;http://www.electoral-reform.org.uk/police-and-crime-commissioners/&quot;&gt;Electoral
Reform Society&lt;/a&gt;. This election has been incredibly badly managed
and publicised by the Government, and lots of early polls are
suggesting a tiny turnout of less than 20%. Despite
the &lt;a href=&quot;http://www.bbc.co.uk/news/uk-politics-20257552&quot;&gt;political
crap about &quot;democracy&quot;&lt;/a&gt; being spouted by some Tory ministers, it's
clear that very few people want this change in how the police are run,
and it has simply been imposed from the top. Too few people care about
the results of these elections for them to be valid - most people
don't want the police politicised.&lt;/p&gt;

&lt;p&gt;After a lot of thought about the issue, I've decided how I'm going
to vote this time. For the first time ever, I'm explicitly going to
turn up and spoil my ballot paper as a protest - &lt;strong&gt;I do not want
this crap&lt;/strong&gt;. I urge other people in England and Wales to
consider doing the same.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Pepper!</title>
    <pubDate>Fri, 28 Sep 2012 17:14:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/09/28#Pepper</link>
    <description>
&lt;p&gt;We've been thinking about getting a dog for &lt;strong&gt;ages&lt;/strong&gt;,
but it's been difficult to work out the logistics when we've been
travelling so much. Well, today's the day!&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://photos.einval.com/gallery/Pepper/aaf&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/Pepper/aaf.sized.jpg&quot;
alt=&quot;Pepper, day one&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Pepper is
a &lt;a href=&quot;http://en.wikipedia.org/wiki/Parson_Russell_Terrier&quot;&gt;Parson
Russell Terrier&lt;/a&gt;, and she's 3 years old. We just collected her from
the lovely people at &lt;a href=&quot;http://www.woodgreen.org.uk/&quot;&gt;Wood Green
Animals Shelter&lt;/a&gt;. Her previous owner passed away recently, so she
was looking for a new home.&lt;/p&gt;

&lt;p&gt;We've just brought her home and things are going great - she's very
well behaved (so far!) and is loving a new place with lots of fuss and
cuddles.&lt;/p&gt;</description>
  </item>
  <item>
    <title>Anniversary trip to Scotland</title>
    <pubDate>Fri, 28 Sep 2012 16:59:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/09/28#Scotland</link>
    <description>
&lt;p&gt;Back at the beginning of September, Jo and I were invited up to
Aberdeen for a weekend for a party to celebrate the 50th wedding
anniversary of some friends. Then we decided to stay around for a few
days - it was our 1st anniversary just two days later. :-)&lt;/p&gt;

&lt;p&gt;We had a great time at the party, and had some awesome weather for
the weekend (especially considering the time of year!). We travelled
around a bit for the next few days, visiting Crathes Castle, John O'
Groats and Culloden amongst other places. We stayed in a hotel
overlooking Loch Ness for the evening of our own anniversary, but no
sign of Nessie! We headed back via Gretna Green and visited the famous
(if tacky!) Blacksmith's there, then headed home. Having done both
Land's End and John O' Groats in one year, we've covered the length of
Great Britain.&lt;/p&gt;

&lt;p&gt;We thoroughly enjoyed ourselves for a few days, especially the
lovely roads with very few people on them! Also we got to see some
very unusual road signs that made us chuckle...&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://photos.einval.com/gallery/2012_Scotland/aab&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/2012_Scotland/aab.sized.jpg&quot;
alt=&quot;Stanes!&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://photos.einval.com/gallery/2012_Scotland/aac&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/2012_Scotland/aac.sized.jpg&quot;
alt=&quot;Otters!&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We'll definitely go back again soon!&lt;/p&gt;</description>
  </item>
  <item>
    <title>EFI Debian CDs, step 4: i386 support</title>
    <pubDate>Mon, 03 Sep 2012 07:24:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/09/03#Debian_EFI_4</link>
    <description>
&lt;p&gt;Continuing on
from &lt;a href=&quot;http://blog.einval.com/2012/08/24#Debian_EFI_3&quot;&gt;my third
EFI progress report&lt;/a&gt;...&lt;/p&gt;

&lt;p&gt;I've added some i386 EFI support in debian-cd and built new
images. Alongside a new amd64 image, we now have an i386 image and a
mixed image which should &lt;em&gt;hopefully&lt;/em&gt; boot and work on both
32-bit and 64-bit machines. The i386 support is more experimental at
this point, and it's more difficult for me to test due to a lack of
physical hardware. If you've got an older 32-bit EFI machine, this
might work for you...&lt;/p&gt;

&lt;p&gt;Grab the images
from &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload4/&quot;&gt;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload4/&lt;/a&gt;
if you'd like to help test. Please do, and let me know via
debian-boot/debian-cd how you get on.&lt;/p&gt;

&lt;p&gt;As previously, the &quot;bits&quot; subdirectory contains all the tweaked d-i
packages I've played with, in both source and binary form. My
debian-cd changes are still in
my &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-cd/branches/EFI_support/&quot;&gt;branch&lt;/a&gt;
but are just about ready for merging I think. I've posted my full set
of d-i patches to the debian-boot list for review now, and hopefully
we'll be able to get those changes merged in after the Wheezy d-i beta
2 build is done. Full speed ahead for EFI in beta 3!&lt;/p&gt;</description>
  </item>
  <item>
    <title>Even more progress on EFI Debian CDs</title>
    <pubDate>Fri, 24 Aug 2012 03:16:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/08/24#Debian_EFI_3</link>
    <description>
&lt;p&gt;Continuing on
from &lt;a href=&quot;http://blog.einval.com/2012/08/22#Debian_EFI_2&quot;&gt;my
second EFI progress report&lt;/a&gt;...&lt;/p&gt;

&lt;p&gt;My
second &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload2/&quot;&gt;alpha
release&lt;/a&gt; of a Wheezy netinst CD for amd64 EFI seemed to work OK for
me and a few others, but it wasn't 100% good, with (at least) two
issues:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It didn't work as a hybrid (CD or USB) image, just working from CD
for EFI
&lt;li&gt;It didn't work for BIOS booting due to a silly bug
&lt;/ul&gt;

&lt;p&gt;In the couple of days since then, I've fixed both of these
issues. Yay! Hybrid boot was easier than I expected - I've just added
a tiny FAT partition to the image containing the grub EFI bootloader
and that seems to work fine. I also found that I made a mistake in the
ordering of the El Torito boot records in the last image. BIOS boot
seems to be limited to just the first image available on the machines
I've tested with, wherease EFI will happily work as a secondary
image. I've swapped them around in my code, and things look much
better now. So, time for another CD alpha release for testing.&lt;/p&gt;

&lt;p&gt;Grab the image
from &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload3/&quot;&gt;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload3/&lt;/a&gt;
if you'd like to help test it. Please do, and let me know via
debian-boot/debian-cd how you get on.&lt;/p&gt;

&lt;p&gt;As previously, the &quot;bits&quot; subdirectory contains all the tweaked d-i
packages I've played with, in both source and binary form. My
debian-cd changes are still in
my &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-cd/branches/EFI_support/&quot;&gt;branch&lt;/a&gt;
but are just about ready for merging I think. I've posted my full set
of d-i patches to the debian-boot list for review now, and hopefully
we'll be able to get those changes merged in after the Wheezy d-i beta
2 build is done. Full speed ahead for EFI in beta 3!&lt;/p&gt;</description>
  </item>
  <item>
    <title>More progress on EFI Debian CDs</title>
    <pubDate>Wed, 22 Aug 2012 13:57:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/08/22#Debian_EFI_2</link>
    <description>
&lt;p&gt;Continuing on
from &lt;a href=&quot;http://blog.einval.com/2012/08/12#Debian_EFI&quot;&gt;my first
EFI progress report&lt;/a&gt;...&lt;/p&gt;

&lt;p&gt;My
first &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload1/&quot;&gt;alpha
release&lt;/a&gt; of a Wheezy netinst CD for amd64 EFI worked OK for me and
a few others, with reasonable feedback. But it was far from complete,
with (at least) three outstanding issues:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It didn't work as a hybrid (CD or USB) image, just working from CD
for EFI
&lt;li&gt;The initial grub display was really ugly, with no graphics
&lt;li&gt;I hadn't been able to get grub-efi to work, so it only allowed use
of elilo.
&lt;/ul&gt;

&lt;p&gt;In the days since then, I've carried on hacking on things. I've not
yet sorted out hybrid boot, but I've fixed the other issues. To make
graphics work on the grub boot menu was a simple case of loading the
right module from grub.cfg (&quot;insmod png&quot;). Getting grub-efi to work
took quite a lot more effort, though. I've been looking through
Ubuntu's version of debian-installer code and merged a fair amount of
their code into my local builds, adding tweaks as necessary. Result?
I've got another CD alpha release ready for testing. Yay!&lt;/p&gt;

&lt;p&gt;Grab the image
from &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload2/&quot;&gt;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload2/&lt;/a&gt;
if you'd like to help test it. Please do, and let me know via
debian-boot/debian-cd how you get on.&lt;/p&gt;

&lt;p&gt;As previously, the &quot;bits&quot; subdirectory contains all the tweaked d-i
packages I've played with, in both source and binary form. My
debian-cd changes are still in
my &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-cd/branches/EFI_support/&quot;&gt;branch&lt;/a&gt;
but are just about ready for merging I think. I'll post more d-i
patches to the debian-boot list for review shortly.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>EFI installation progress</title>
    <pubDate>Sun, 12 Aug 2012 16:22:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/08/12#Debian_EFI</link>
    <description>
&lt;p&gt;As promised
&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/925.en.html&quot;&gt;last
month at DebConf&lt;/a&gt;, I've been working on adding EFI support to
debian-cd and debian-installer, hopefully to get it up and running. At
the moment, this is &lt;strong&gt;basic&lt;/strong&gt; support only for booting
and setting up the installed system via UEFI. I'm &lt;strong&gt;not&lt;/strong&gt;
worrying about &quot;Secure&quot; (better named &quot;Restricted&quot;?) Boot yet - that
comes later, and depends on the basic stuff working first.&lt;/p&gt;

&lt;p&gt;So, how is it going? Quite well, really. I've got a
&lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-cd/branches/EFI_support/&quot;&gt;debian-cd
branch&lt;/a&gt; that I'm working on locally, and with a relatively small
amount of work there I've got a locally-built CD that boots in EFI
mode, using grub-efi as a boot loader. I've borrowed a script
called &lt;code&gt;efi-image&lt;/code&gt; from Colin Watson which generates the
necessary EFI boot image from bits out of the grub-efi-amd64-bin
package. For some reason, this grub image isn't working with all the
normal graphics code so I've not got a pretty branded startup screen
yet. But, nonetheless, I do have a working EFI boot CD. Yay!&lt;/p&gt;

&lt;p&gt;Next step: the installer. At the moment, generic amd64 and i386
machines are assumed to use need dos-style partitioning, and then
either lilo or grub as a bootloader. I've patched and rebuilt some of
the d-i packages locally to add a new sub-architecture of &quot;efi&quot; for
both amd64 and i386, alongside the existing &quot;generic&quot; and &quot;mac&quot;
variants. Using that new sub-architecture, it's possible to add checks
for amd/efi and i386/efi in various places to make the necessary
changes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;choose the GPT partition type for blank disks
&lt;li&gt;tweak the auto-partitioner to add an EFI (fat32) boot partition
on the front of the first hard disk
&lt;li&gt;install the elilo bootloader
&lt;/ul&gt;

&lt;p&gt;Why elilo? It's the default for current ia64 systems, and for EFI
Macs. I tried to get grub-efi working with the grub-installer package,
but with little success so far. I'll try again with grub-efi, but for
now elilo is much simpler and (importantly!) it works for me.&lt;/p&gt;

&lt;p&gt;So, I have a netinst CD built that works for me in local testing in
a qemu VM
using &lt;a href=&quot;http://blog.hansenpartnership.com/uefi-secure-boot/&quot;&gt;James
Bottomley's OVMF build of Tianocore&lt;/a&gt;. It's not pretty, but it works
fine, covering all the normal Debian installation steps and giving me
a UEFI system at the end of the process. I'm about to start testing on
real hardware now, so I think it's worth sharing this netinst image
with others too. Grab it
from &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload1/&quot;&gt;http://cdimage.debian.org/cdimage/unofficial/efi-development/upload1/&lt;/a&gt;
. The &quot;bits&quot; subdirectory contains all the tweaked d-i packages I've
played with, in both source and binary form. If you have an EFI system
and would like to help us get it supported well in Debian, please
download this image and play with it! Feedback to the debian-cd and/or
debian-boot lists, please!&lt;/p&gt;</description>
  </item>
  <item>
    <title>CD work at DebCamp</title>
    <pubDate>Mon, 09 Jul 2012 18:20:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/07/09#cd-work</link>
    <description>
&lt;p&gt;Great productive couple of days hacking on debian-cd with Joey. I
don't do DebCamp often enough - it's great fun...&lt;/p&gt;</description>
  </item>
  <item>
    <title>DebCamp</title>
    <pubDate>Fri, 06 Jul 2012 00:00:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/07/06#debcamp1</link>
    <description>
&lt;p&gt;Yay, got to Nicaragua OK last night. It's the first time I've
managed to get to DebCamp in quite a while, and I'm making the most of
it. I've got slides ready for two of my BoF sessions next week (both
ARM-related), and I'm preparing for the other four now. Why did I sign
up to run six sessions? Maybe because I'm a bit silly, or maybe
because they needed doing and other people hadn't registered
them. Maybe both. :-)&lt;/p&gt;

&lt;p&gt;BTW: these are all BoF (Birds of a Feather) sessions, not
lectures. While I have an interest in each topic, I'm neither wanting
nor expecting to just talk &lt;strong&gt;at&lt;/strong&gt; a room full of people -
I'm wanting to provoke discussions in each case. If you're interested,
please join in those discussions, either physically in Managua or
virtually using
the &lt;a href=&quot;http://debconf12.debconf.org/watch.xhtml&quot;&gt;live video
streaming&lt;/a&gt; and IRC back-channels:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/870.en.html&quot;&gt;ARM port(s) update&lt;/a&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/882.en.html&quot;&gt;AArch64 planning&lt;/a&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/925.en.html&quot;&gt;EFI in Debian&lt;/a&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/871.en.html&quot;&gt;Debian-CD&lt;/a&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/926.en.html&quot;&gt;Hijacking packages for fun and profit&lt;/a&gt;
&lt;li&gt;&lt;a href=&quot;http://penta.debconf.org/dc12_schedule/events/872.en.html&quot;&gt;wiki.debian.org&lt;/a&gt;
&lt;/ul&gt;

&lt;p&gt;See you there...!&lt;/p&gt;</description>
  </item>
  <item>
    <title>Small children on long-haul flights...</title>
    <pubDate>Mon, 04 Jun 2012 22:20:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/06/04#kids_on_planes</link>
    <description>
&lt;p&gt;...should be banned. On the flight back from Hong Kong to London, a
collection of about half a dozen small children conspired to cry,
shout, wail and shriek nigh-on constantly. For twelve hours. :-(&lt;/p&gt;

&lt;p&gt;I think it's incredibly selfish to take kids on planes when they're
too young to understand what's going on, or to behave
reliably. Children make noise, that's natural and expected. Forcing
hundreds of other people around you to deal with that noise in an
enclosed space for extended periods with no way to escape is just
wrong, in my opinion.&lt;/p&gt;

&lt;p&gt;&amp;lt;/rant&amp;gt;&lt;/p&gt;</description>
  </item>
  <item>
    <title>Wandering around Hong Kong</title>
    <pubDate>Mon, 04 Jun 2012 22:12:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/06/04#hong_kong</link>
    <description>
&lt;p&gt;Jo and I flew in to HK a few days early for the Linaro conference,
so we got some time to ourselves for doing touristy stuff. That was a
good plan - we got to see quite a lot of Kowloon for a couple of days,
then we wandered over to Hong Kong island itself for a day. Jo also
had more time during the week while I was in the sessions at the
conference.&lt;/p&gt;

&lt;p&gt;Hong Kong is a &lt;em&gt;busy&lt;/em&gt; place, very densely packed at all
times of day and night that we could see. The first impression we got
on the taxi from the airport on day one was that it was a city full of
tower blocks - huge numbers of apartments stacked very closely
together for living space. That makes sense, I guess, with the large
population in such a small space. There are houses around with more
space for people to live, but they are understandably very
expensive.&lt;/p&gt;

&lt;p&gt;Later on in Kowloon, we got to meet lots of the local street
vendors, mostly offering us &quot;Copy Rolex&quot;, &quot;Fake handbag&quot; and the
like. Even &quot;Sharp trousers&quot; at one point. We decided not to try them
out... :-) We saw lots and lots of very expensive shops downtown,
crammed into huge shopping centres in the tourist area. As an antidote
for all of that, we headed up to the &quot;Golden Computer Arcade&quot; to go
browsing around the vast array of tiny technology stalls and shops
there. Picked up some nice cheap laptop memory and some SD cards
there. Yay!&lt;/p&gt;

&lt;p&gt;Across on Hong Kong island itself on Sunday,
we &lt;a href=&quot;http://blog.einval.com/2012/06/04#visiting_grandad&quot;&gt;found
my grandfather's grave&lt;/a&gt; then rode around on
the &lt;a href=&quot;http://photos.einval.com/gallery/HK_tram&quot;&gt;trams&lt;/a&gt; for a
while to get a good view of the city, including
a &lt;a href=&quot;http://photos.einval.com/gallery/HK_demo&quot;&gt;democracy
protest&lt;/a&gt; that happened to be on that day! We had a quick look
around &lt;a href=&quot;http://photos.einval.com/gallery/HK_temple&quot;&gt;Tin Hau
Temple&lt;/a&gt;, where we found a very specific set of rules for
visitors:&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://photos.einval.com/gallery/HK_temple/aaa&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/HK_temple/aaa.sized.jpg&quot;
alt=&quot;temple rules&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I can only guess that they must have been terrified by gangs of
kids racing their RC cars at one point!&lt;/p&gt;

&lt;p&gt;We finished the day by heading up to Victoria Peak for the sunset
view and some dinner, then back to the hotel. Killing time in a
shopping centre waiting for the bus to turn up, we found a truly
astonishing little item on sale, a Solar Queen!&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/HK_solarqueen.jpg&quot;
alt=&quot;solar queen&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Apparently this gift has a solar panel on the handbag to provide
power to a little motor in the Queen's hand to make her wave to her
subjects. We decided that we'd somehow have to live without such a
delight in our lives... :-)&lt;/p&gt;

&lt;p&gt;HK was a cool place to visit. It still feels very British in some
ways, as you'd expect from an ex-colony (power sockets are still the
same as ours, driving on the left, everybody spoke English, etc.) but
utterly alien in others (the climate, working public transport
*grin*). I look forwards to heading out there again!&lt;/p&gt;</description>
  </item>
  <item>
    <title>Linaro Connect in Hong Kong, 2012: Ruby bug squashed!</title>
    <pubDate>Mon, 04 Jun 2012 20:22:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/06/04#lc-q2-2012</link>
    <description>
&lt;p&gt;&lt;img src=&quot;http://www.linaro.org/remote/images/linaro-connect-logo.png&quot;
alt=&quot;Connect logo&quot; align=&quot;left&quot;&gt;Sometimes conferences can be dull and
boring, but sometimes they can be just awesome in terms of finding the
right people to collaborate with. Linaro Connect in Hong Kong last
week was definitely one of the great ones!
&lt;/p&gt;

&lt;p&gt;I chaired my my usual sessions
(&lt;a href=&quot;http://summit.linaro.org/lcq2-12/meeting/20695/linaro-general-q112-armhf-status/&quot;&gt;armhf
status&lt;/a&gt;
and &lt;a href=&quot;http://summit.linaro.org/lcq2-12/meeting/20696/linaro-general-q112-cross-distro-1/&quot;&gt;cross-distro
ARM&lt;/a&gt;) and we had some lively discussion in both. We're probably
just about done with the armhf sessions, as most distros have accepted
a hard-float ARMv7 port now and there's not so much specific work left
there now that future sessions will be necessary. The cross-distro
work for ARM ports is likely to continue into the future, but we're
going to be concentrating on bootstrapping work for ARMv8 soon.&lt;/p&gt;

&lt;p&gt;Talking v8, there were a lot of meetings discussing the various
work topics for this new 64-bit ARM architecture: kernel, toolchains,
bootstrapping etc. More to come on that soon!&lt;/p&gt;

&lt;p&gt;On top of all this useful discussion and planning, we also found
time during the week for some hacking. This was the highlight of the
week for me, as I found some expert help to solve my long-standing
Ruby on ARM bug
(&lt;a href=&quot;http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652674&quot;&gt;Debian
bug #652674&lt;/a&gt;, ruby1.9.1: FTBFS on armhf: test suite
segfaults). Ulrich Weigand (an IBM toolchain wizard seconded into the
Linaro team) sat with me for a couple of hours while we worked through
reproducing the problem, only to find that he could not reproduce it!
The crash had looked very much like a pthreads locking bug, which
was &lt;em&gt;scaring&lt;/em&gt; me. After some digging, we worked out where the
problem was, and how it was now fixed.&lt;/p&gt;

&lt;p&gt;For a long time on ARM, the Linux getcontext/setcontext system
calls have never been implemented; apparently nobody really missed
them, so they have never been a priority. In Ruby 1.9.x, the
implementation of the new &quot;fiber&quot; primitive wanted to use
getcontext/setcontext to control stack state etc. in different threads
of control. In cases where they are not available or known not to work
well, Ruby has fallback code to implement similar functionality. It
seems that fallback code is buggy. Maybe it was correct at some point
and has bit-rotted due to not being exercised, or maybe it was buggy
as written, but it clearly does not work correctly for us now. In the
last few months, getcontext/setcontext have finally
been &lt;a href=&quot;http://sourceware.org/git/?p=glibc-ports.git;a=commit;h=402a76b62dded0ee93cfec0471aaeccb989196d2&quot;&gt;implemented
for ARM in glibc trunk&lt;/a&gt; (by Michael Hope, also in the Linaro
toolchain team!) and backported into current Debian and Ubuntu eglibc
versions. Re-running configure and rebuilding Ruby against the most
recent code in both Sid and Precise fixed the test suite crash we were
seeing earlier. Yay! We could also provoke the bug again at will by
quickly hacking around the Ruby source to force it to switch back to
the fallback code, thereby verifying the fix.&lt;/p&gt;

&lt;p&gt;Why does this matter? As we're expecting ARM servers to enter the
market soon, web apps written in Ruby on Rails are going to be an
important part of the software stack that customers will want to
run. Broken fibers and threading would not help here!&lt;/p&gt;

&lt;p&gt;It's great to meet up and work with talented folks like this;
Linaro Connect is an excellent event for getting stuff done!&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Visiting my grandfather in Hong Kong</title>
    <pubDate>Mon, 04 Jun 2012 19:07:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/06/04#visiting_grandad</link>
    <description>
&lt;p&gt;I never met my father's father, as he died many years before I was
born. He was a soldier in the British Army and was killed in an
accident in Burma in the 1950s. I'm told that back then the Army did
not repatriate casualties as a matter of course like they do today, so
none of the family got to see his funeral or even visit the
grave. Like many of the military casualties in the Far East, he was
buried in the Colonial Cemetery in Hong Kong. A few photographs were
sent to my grandmother of the ceremony and the headstone, but that's
all we ever saw.&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/grandad-telegram.png&quot;
alt=&quot;telegram&quot;&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/funeral.png&quot;
alt=&quot;funeral&quot;&gt;&lt;/p&gt;

&lt;p&gt;Fast forward to 2012. I travelled to Hong Kong for a conference
(&lt;a href=&quot;http://summit.linaro.org/lcq2-12/&quot;&gt;Linaro Connect&lt;/a&gt;, more
about that later...). I looked up the details of where grandad was
laid to rest, and found a major coincidence. He was killed on 27th May
1952, almost exactly 60 years ago! I resolved to go to find him on
27th May 2012 to make the most of this lucky anniversary. Wikipedia
told me that in the intervening years the Colonial Cemetery had been
renamed to Happy Valley Cemetery, then
simply &lt;a href=&quot;http://en.wikipedia.org/wiki/Hong_Kong_Cemetery&quot;&gt;Hong
Kong Cemetery&lt;/a&gt;, and repurposed from military to civilian use.&lt;/p&gt;

&lt;p&gt;Jo and I bought some flowers and headed over to Happy Valley on
Hong Kong Island on Sunday afternoon. We found a very large cemetery
with a helpful map posted to show the different sections, but nothing
to tell us where we should be looking. One of the attendants at the
office on site looked at the details we had and shrugged to say
&quot;sorry, can't help&quot;. Ah well, nobody said this was going to be very
easy... What we found after a few minutes was that the graves weren't
laid out in any obviously logical fashion. In any given small area,
you'd find people buried from &lt;em&gt;roughly&lt;/em&gt; the same period, but
people for any given period could (and would) be scattered across
multiple sections at all corners of the site. Great, time for an
exhaustive search then. I started combing the site, checking all the
markers I could find that looked anything like the tiny grainy black
and white photo we had of grandad's headstone.&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/HK_cemetery/aao.sized.jpg&quot;
alt=&quot;cemetery&quot;&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/headstone.png&quot;
alt=&quot;headstone&quot;&gt;&lt;/p&gt;

&lt;p&gt;Almost two hours later, I eventually found him. Two hours of heavy
work: the cemetery is built on the side of quite a steep hill, and the
prevailing weather was very hot with 100% humidity. But, I forgot all
that as we eventually stumbled across the correct grave in (no
exaggeration!) the very last part of the last section of the site,
20a.&lt;/p&gt;

&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://photos.einval.com/albums/HK_cemetery/aag.sized.jpg&quot;
alt=&quot;grave&quot;&gt;&lt;/p&gt;

&lt;p&gt;I was relieved at this point: as things had taken so long, I had
started to worry that maybe the grave had been moved or the headstone
damaged and lost. But no, I found the man who had gone off to war
leaving my dad and aunt as small children. We took some photos and
took note of where we had found the final resting place of Sergeant
William Alexander McIntyre of the Royal Signals, a man I never met in
life but clearly a very important member of our family.&lt;/p&gt;</description>
  </item>
  <item>
    <title>Armhf buildds and status in Debian</title>
    <pubDate>Mon, 09 Jan 2012 17:11:00 +0100</pubDate>
    <link>http://blog.einval.com/2012/01/09#armhf_buildds2</link>
    <description>
&lt;h3&gt;Current status&lt;/h3&gt;

&lt;p&gt;Back in September,
  I &lt;a href=&quot;http://blog.einval.com/2011/09/05#armhf_buildds&quot;&gt;wrote&lt;/a&gt;
  about the machines that I set up to help bootstrap the new armhf
  port in Debian. Basing on Konstantinos' huge efforts in bringing up
  the new &quot;architecture&quot; in debian-ports, we started importing armhf
  into the main Debian archive on the 24th of November. Since then,
  those builders have been churning away night and day to build the
  huge collection of software that makes up the Debian archive. The
  current state can be seen on
  the &lt;a href=&quot;https://buildd.debian.org/status/architecture.php?a=armhf&amp;suite=sid&quot;&gt;armhf
  buildd status page&lt;/a&gt;, and there's a nice graph showing how quickly
  we've managed to run from 0 to over 90% of the archive here. (Click
  on the image for a larger version, or visit
  &lt;a href=&quot;https://buildd.debian.org/stats/&quot;&gt;https://buildd.debian.org/stats/&lt;/a&gt;
  for other versions. We overtook hurd-i386 quickly and are now ahead
  of the kfreebsd-* architectures.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.einval.com/~steve/images/armhf-bootstrap-big.png&quot;&gt;&lt;img src=&quot;http://www.einval.com/~steve/images/armhf-bootstrap.png&quot;
alt=&quot;armhf bootstrap graph&quot;&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We've recently brought 3 more similar build machines online
  (&lt;strong&gt;hildegard&lt;/strong&gt;, &lt;strong&gt;howells&lt;/strong&gt;
  and &lt;strong&gt;hummel&lt;/strong&gt;), again sponsored by the nice folks
  at &lt;a href=&quot;http://www.linaro.org&quot;&gt;Linaro&lt;/a&gt; but now hosted at
  the &lt;a href=&quot;http://www.ynic.york.ac.uk/&quot;&gt;York NeuroImaging Centre
  at the University of York&lt;/a&gt;. This gives us both more build
  horsepower to keep up with building more different bits of Debian
  (experimental, updates etc.) and more redundancy in case of
  problems.&lt;/p&gt;

&lt;p&gt;We now have the vast majority of the archive built, and now a
  number of us are concentrating on fixing the remaining issues:
  language bootstraps and bugs. Also, on the 7th of January we were
  just added into testing, the next step on our path for inclusion as
  a Debian release architecture.&lt;/p&gt;

&lt;h3&gt;Setting up the machines&lt;/h3&gt;

&lt;p&gt;A lot of people have been asking me about the physical setup I
  showed in my last blog about these machines, so here's more details
  for those who are interested.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;3U mini-rack&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;&lt;a href=&quot;http://www.schroff.co.uk&quot;&gt;Schroff&lt;/a&gt; model 24563-192
        subrack (3U, 235mm deep), ordered
        from &lt;a href=&quot;http://uk.farnell.com/jsp/search/productdetail.jsp?sku=1455796&quot;&gt;Farnell&lt;/a&gt;
        in the UK.
      &lt;li&gt;Added some 24560-353 220mm guide rails
        (&lt;a href=&quot;http://uk.farnell.com/jsp/search/productdetail.jsp?sku=1370430&quot;&gt;Farnell
          link&lt;/a&gt;).
    &lt;/ul&gt;
    &lt;p&gt;Lovely kit, which fits together easily for a rigid enclosure.&lt;/p&gt;
  &lt;li&gt;&lt;strong&gt;ATX PSU&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;Ideally with lots of old-style Molex power connectors. I
        bought the cheapest one I could find from my supplier, and
        dismantled it. I cannibalised another old PSU and soldered on
        some extra Molex connectors.
      &lt;li&gt;In theory, the 6 boards and disks I'm using here could use up
        to 15W each on the 5V rail (but in practice much less); any
        current PSU on the market should handle that easily.
      &lt;li&gt;While I had the case open, I drilled holes and put some bolts
        through so I could mount it to the mini-rack.
      &lt;li&gt;Finally, connect together pins 15 and 16 on the ATX power
        connector so that the PSU will come on without needing to be
        connected to a PC motherboard
        (&lt;a href=&quot;http://en.wikipedia.org/wiki/ATX&quot;&gt;details on
          wikipedia&lt;/a&gt;).
    &lt;/ul&gt;
  &lt;li&gt;&lt;strong&gt;Freescale iMX53 Quickstart boards&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;These are the little 3-inch square dev boards I'm using. I
        bought them
        from &lt;a href=&quot;http://nl.mouser.com/ProductDetail/Freescale-Semiconductor/MCIMX53-START/?qs=sGAEpiMZZMspbelMIdDJdKswmyqRD7aG&quot;&gt;Mouser&lt;/a&gt;
        here, but there are quite a few other companies selling them
        too. Apparently this exact part has just gone EOL, but there is
        a &lt;a href=&quot;http://nl.mouser.com/ProductDetail/Freescale-Semiconductor/MCIMX53-START-R/?qs=sGAEpiMZZMtE4ePzUE8d2K4fu%252bEPEHrz&quot;&gt;replacement&lt;/a&gt;
        that I would hope to work in its place.
    &lt;/ul&gt;
  &lt;li&gt;&lt;strong&gt;2.5 inch SATA hard drives&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;I just bought what looked reasonably priced from my local
        supplier, 320 GB on the first machines and 250 GB on the next
        three after the recent rise in disk prices.
    &lt;/ul&gt;
  &lt;li&gt;&lt;strong&gt;Cables and connectors&lt;/strong&gt;
    &lt;ul&gt;
      &lt;li&gt;45cm right-angle SATA cable with one right-angled end
        like &lt;a href=&quot;http://www.scan.co.uk/products/45cm-scan-right-angled-sata-i-ii-cable-with-locking-latches&quot;&gt;this&lt;/a&gt;
      &lt;li&gt;Molex to twin SATA-power cable
        like &lt;a href=&quot;http://www.scan.co.uk/products/30cm-akasa-4pin-molex-to-2x-sata-adapter-single-molex-to-two-15pin-sata-power-connectors&quot;&gt;this&lt;/a&gt;
      &lt;li&gt;2.1mm/5.0mm power plug
        like &lt;a href=&quot;http://www.maplin.co.uk/dc-power-plugs-43084&quot;&gt;here&lt;/a&gt;
        (L48AY at Maplin)
    &lt;/ul&gt;
    &lt;p&gt;The downside of the Quickstart board is that it doesn't include
    a SATA power connector on the board, just a SATA data
    connector. So, what I've done for my boards is modify Molex to
    SATA power splitters. This way I get a single power input for the
    board/drive combination as a whole.&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;The Molex socket will connect to the Molex plug from the PSU
      &lt;li&gt;The first SATA power connector goes to the laptop drive
      &lt;li&gt;Cut off the second SATA connector
      &lt;li&gt;Using the red and black (5V and ground) wires remaining,
        solder on a power plug to drive the board itself
    &lt;/ul&gt;
  &lt;li&gt;&lt;strong&gt;Perspex board&lt;/strong&gt;
    &lt;ul&gt;
    &lt;li&gt;I found a supplier near Cambridge for some perspex. Each
    machine has a base card measuring 220mm x 100mm, 2mm thick. I
    drilled holes and mounted each board with a drive and its cables
    as
    shown &lt;a href=&quot;http://www.einval.com/~steve/photos/hartmann.jpg&quot;&gt;here&lt;/a&gt;.
    &lt;/ul&gt;
&lt;/ul&gt;

&lt;p&gt;Mount the 6 boards into the mini-rack, connect up the Molex power
  connectors to each board, attach ethernet cables and turn it all on!
  Each board comes with a micro-SD card containing uboot and an Ubuntu
  installation. I've configured uboot to boot off the hard drive
  directly, but leaving configuration available to use the Ubuntu on
  the micro-SD as a simple rescue system should the need arise.&lt;/p&gt;

&lt;p&gt;The Quickstart boards are not &lt;strong&gt;ideal&lt;/strong&gt; physically for
  two reasons: the lack of SATA power, plus you need to push a power
  button on each board to boot it - they don't boot automatically the
  moment power is applied. However, they're quite inexpensive little
  machines and have done a great job of building the Debian archive so
  far! The ideal machines for us would also include more RAM at this
  point. CPU on these is adequate, but the larger C++ packages (yay
  webkit!) use a &lt;strong&gt;huge&lt;/strong&gt; amount of memory at link
  time. Linking in swap is not the best thing,
  performance-wise... :-(&lt;/p&gt;

&lt;p&gt;&lt;b&gt;UPDATE 2012-01-12:&lt;/b&gt; Ian tells me that the newer Quickstart-R
  boards apparently have a different power controller; these now boot
  up straight away without needing you to push a button. That sounds
  useful.&lt;/p&gt;</description>
  </item>
  <item>
    <title>Armhf buildds and porter box hosted at ARM</title>
    <pubDate>Mon, 05 Sep 2011 17:15:00 +0100</pubDate>
    <link>http://blog.einval.com/2011/09/05#armhf_buildds</link>
    <description>
&lt;p&gt;I'm in the middle of setting up new build machines for the armhf
port (see &lt;a href=&quot;http://wiki.debian.org/ArmHardFloatPort&quot;&gt;the
wiki&lt;/a&gt; for more details). We'll shortly have six machines set up in
the machine room here at ARM in Cambridge:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;b&gt;harris&lt;/b&gt; as a porter box
&lt;li&gt;&lt;b&gt;hartmann&lt;/b&gt;, &lt;b&gt;hasse&lt;/b&gt;, &lt;b&gt;hebden&lt;/b&gt; and &lt;b&gt;henze&lt;/b&gt; running buildd software
&lt;li&gt;&lt;b&gt;hoiby&lt;/b&gt; as a hot spare
&lt;/ul&gt;

&lt;p&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/hartmann.jpg&quot;
alt=&quot;hartmann&quot;&gt;&lt;/p&gt;

&lt;p&gt;All of these machines are Freescale i.MX53 Quickstart (aka &quot;loco&quot;)
development boards. They include a 1GHz i.MX53 CPU (based around the
ARM Cortex A8, one of the ARMv7-A family). They have 1GB of RAM and
native SATA. They're lovely little machines, measuring just 3 inches
square. To mount them usefully in a machine room, I've mounted each
board with a 320GB notebook hard drive and the necessary cabling onto
a small perspex card as you can see here. Then we can fit 6 such
machines and a normal PC-style ATX PSU into a 3U mini-rack. Well,
it &lt;b&gt;almost&lt;/b&gt; fits - the power supply pokes out a little so we'll
need 4U of space when we come to mount it.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;http://www.einval.com/~steve/photos/armhf-minirack.jpg&quot;
alt=&quot;armhf mini rack&quot;&gt;&lt;/p&gt;

&lt;p&gt;The Quickstart boards have been sponsored
by &lt;a href=&quot;http://www.linaro.org&quot;&gt;Linaro&lt;/a&gt;, and ditto my time
setting up these machines. Thanks!&lt;/p&gt;

&lt;p&gt;As is common with new development boards, these machines are
not &lt;em&gt;quite&lt;/em&gt; fully supported in Debian yet. The kernels we're
using are locally-built, using the sources supplied by Freescale. For
now, that means a heavily-patched &quot;2.6.35&quot; kernel but we're expecting
to be able to switch to mainline very soon. The .config I'm using
is &lt;a href=&quot;http://www.einval.com/~steve/debian/freescale/kernel.config/&quot;&gt;kernel.config&lt;/a&gt;,
and I've built it natively on harris using&lt;/p&gt;

&lt;p&gt;&lt;code&gt;fakeroot make -j2 deb-pkg DEBEMAIL=93sam@debian.org DEBFULLNAME=&quot;Steve McIntyre&quot; KDEB_PKGVERSION=1buildd1&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Similarly to the setup for
the &lt;a href=&quot;http://blog.einval.com/2010/09/27#marvell_buildds&quot;&gt;armel
machines&lt;/a&gt;, for now I've tweaked things when installing the
kernel:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;depmod:
  &lt;ul&gt;
    &lt;li&gt;Need to make sure that depmod is run so the new kernel can
        find and load modules at boot. Added trivial script
        in &lt;code&gt;/etc/kernel/postinst.d/depmod&lt;/code&gt; to do this.
  &lt;/ul&gt;
  &lt;li&gt;initramfs-tools:
  &lt;ul&gt;
    &lt;li&gt;Needed to copy the
        file &lt;code&gt;/etc/kernel/postinst.d/initramfs-tools&lt;/code&gt; into
        place from my amd64 machine; I'm guessing this would be there
        automatically on a new-enough version of initramfs-tools on
        the armel machines, but we're still using Lenny as a base
        system for now even if I'm using a Squeeze-based kernel.
  &lt;/ul&gt;
  &lt;li&gt;flash-kernel:
  &lt;ul&gt;
    &lt;li&gt;Add support for these boards
    &lt;li&gt;&lt;a href=&quot;http://bugs.debian.org/550584&quot;&gt;#550584&lt;/a&gt;: kernel
        postinst hook script
        (&lt;code&gt;/etc/kernel/postinst.d/zz-flash-kernel&lt;/code&gt;) to
        create uImage and uInitrd files from the kernel zImage and the
        initramfs.
  &lt;/ul&gt;
&lt;/ul&gt;

&lt;p&gt;Finally, I've tweaked the uboot config on the machines to use the
uImage and uInitrd files that are generated by flash-kernel:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;pre&gt;
MX53-LOCO U-Boot &gt; setenv loadaddr 0x70800000
MX53-LOCO U-Boot &gt; setenv initrdaddr 0x71000000
MX53-LOCO U-Boot &gt; setenv bootargs_sata set bootargs \$\{bootargs\} root=/dev/sda2 rw rootwait
MX53-LOCO U-Boot &gt; setenv load_sata_kernel ext2load sata 0:1 \$\{loadaddr\} /uImage
MX53-LOCO U-Boot &gt; setenv load_sata_initrd ext2load sata 0:1 \$\{initrdaddr\} /uInitrd
MX53-LOCO U-Boot &gt; setenv load_sata run load_sata_kernel load_sata_initrd
MX53-LOCO U-Boot &gt; setenv bootcmd_sata sata init\; run bootargs_base bootargs_sata load_sata\; bootm \$\{loadaddr\} \$\{initrdaddr\}
MX53-LOCO U-Boot &gt; setenv bootcmd run bootcmd_sata
&lt;/pre&gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;And I've added extra config into uboot to use the pre-installed
Ubuntu system on the micro SD card as a fall-back:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&lt;pre&gt;
MX53-LOCO U-Boot &gt; setenv bootcmd_rescue sata init\; run bootargs_base bootargs_sata\; mmc read 0 \$\{loadaddr\} 0x800 0x1800\; bootm
&lt;/pre&gt;&lt;/code&gt;&lt;/p&gt;
</description>
  </item>
  <item>
    <title>In one word: AWESOME</title>
    <pubDate>Mon, 15 Aug 2011 12:01:00 +0100</pubDate>
    <link>http://blog.einval.com/2011/08/15#dc11_summary</link>
    <description>
&lt;p&gt;Every year I worry that DebConf might not be as good as I hope, or
not as good as previous years. Well, I've yet to be let down!&lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;http://wiki.earth.li/DebconfTravel2011&quot;&gt;road trip&lt;/a&gt;
down to Banja Luka was good fun, even if it took a little longer than
planned. We ended up travelling down through Germany on the same
Friday as much of the country finished work/school for their summer
vacation, so there was a &lt;strong&gt;lot&lt;/strong&gt; of traffic. Meh, we got
there in the end.&lt;/p&gt;

&lt;p&gt;I made my usual mistake of planning some things to hack on during
the DebConf week; by now I should know better... :-) I made a start on
one small project, but then got so distracted by so many talks and
side meetings with people that it's still waiting. As always, my own
personal TODO list picked up huge amounts of extra stuff from those
discussions. Catching up with, and socialising with, Debian friends
from all over the world was also fun as always!&lt;/p&gt;

&lt;p&gt;Lots of highlights of the week for me, both for technical and
social reasons:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;Multi-arch is finally with us!
      Great &lt;a href=&quot;https://penta.debconf.org/penta/schedule/dc11/event/747.en.html&quot;&gt;talk
      from Steve Langasek&lt;/a&gt;, and a very
      useful &lt;a href=&quot;http://wiki.debian.org/Multiarch/Debconf11MultiarchRelatedMinutes&quot;&gt;meeting
      afterwards&lt;/a&gt; to unpick what work is still needed. Quite a bit,
      it seems... :-)
  &lt;li&gt;Useful meetings with Otavio to discuss future changes to how
      debian-installer is going to work, and how the debian-cd and
      debian-installer teams can work together better on that.
  &lt;li&gt;Catching up with Martin to work out what's needed to get
      &lt;a href=&quot;http://pancutan.alioth.debian.org/&quot;&gt;pancutan&lt;/a&gt;finally
      integrated with our regular CD builds.
  &lt;li&gt;Talking with Jimmy about where to go next for regular
      &lt;a href=&quot;http://live.debian.net&quot;&gt;debian-live&lt;/a&gt; builds on our
      core CD build machine.
  &lt;li&gt;The &lt;a href=&quot;https://penta.debconf.org/penta/schedule/dc11/event/795.en.html&quot;&gt;ARM
      BoF&lt;/a&gt;, where things have moved on from &quot;why should I care
      about ARM?&quot; to &quot;when will you have armhf ready for going in the
      archive?&quot;. W00t!
  &lt;li&gt;Doing our own day trip in the cars from the UK. We got to meet
      some very friendly and helpful local people, plus we found some
      incredible roads to drive on. Even if not all of them
      were &lt;strong&gt;technically&lt;/strong&gt; roads yet... :-)
  &lt;li&gt;Playing poker in a real casino for the first time, along with a
      bunch of friends. Nice atmosphere, and very good fun.
&lt;/ul&gt;

&lt;p&gt;Banja Luka was a lovely place to visit, and a great host city for
DebConf. Looking forwards to Managua now!&lt;/p&gt;</description>
  </item>
  <item>
    <title>Unofficial backport CDs now hosted on cdimage.debian.org</title>
    <pubDate>Mon, 25 Jul 2011 14:41:00 +0100</pubDate>
    <link>http://blog.einval.com/2011/07/25#kmuto_cd</link>
    <description>
&lt;p&gt;For several years, &lt;a href=&quot;http://kmuto.jp/b.cgi&quot;&gt;Kenshi Muto&lt;/a&gt;
has been doing some awesome work on updated/backported Debian CDs,
producing CDs with support for newer hardware and newer features. I've
used them myself in the past to help get awkward machines working, and
I know they are a great resource for lots of other Debian users.&lt;/p&gt;

&lt;p&gt;We've discussed things in the last few weeks, and agreed that it
would be useful to host his images on cdimage.debian.org. The best
place to look now
is &lt;a href=&quot;http://cdimage.debian.org/cdimage/unofficial/backports/&quot;&gt;http://cdimage.debian.org/cdimage/unofficial/backports/&lt;/a&gt;. These
are &lt;b&gt;unofficial&lt;/b&gt; images, so please don't report bugs in the
Debian BTS for them.&lt;/a&gt;
</description>
  </item>
  <item>
    <title>Project Harmony?</title>
    <pubDate>Wed, 13 Jul 2011 16:57:00 +0100</pubDate>
    <link>http://blog.einval.com/2011/07/13#disharmony</link>
    <description>
&lt;p&gt;So, the &quot;Harmony Project&quot; launched their set of contributor
agreements and tools last week. Colour me unimpressed...&lt;/p&gt;

&lt;p&gt;There's a claim on
their &lt;a href=&quot;http://harmonyagreements.org/&quot;&gt;website&lt;/a&gt; that they
are a &quot;community-centered group&quot;, but I don't see any list of people
and organisations who contributed to this work. That bothers
me. Regarding their aim to &quot;assist organisations which use
contribution agreements&quot;, I don't think that there is anything of
value here for the Free Software community at all. Free Software
developers &lt;b&gt;don't need contribution agreements&lt;/b&gt;, and in my
opinion encouraging their use like this is only going to cause further
splintering of the community. We've managed for a very long time
without them, why start now?&lt;/p&gt;

&lt;p&gt;As a developer, I personally don't believe in contribution
agreements at all. If I contribute code to a project, it will be under
the terms of a good Free Software license or not at all. That's all
that's needed. There's a fair body of opinion out there on this - see
pieces
from &lt;a href=&quot;http://ebb.org/bkuhn/blog/2011/07/07/harmony-harmful.html&quot;&gt;Bradley
Kuhn&lt;/a&gt;, &lt;a href=&quot;http://opensource.com/law/11/7/trouble-harmony-part-1&quot;&gt;Richard
Fontana&lt;/a&gt;
and &lt;a href=&quot;http://blogs.gnome.org/bolsh/2011/07/06/harmony-agreements-reach-1-0/&quot;&gt;Dave
Neary&lt;/a&gt; for more discussion.&lt;/p&gt;

&lt;p&gt;What do you think?&lt;/p&gt;</description>
  </item>
  </channel>
</rss>