[U-Boot-Users] [PATCH] Add support for the hammerhead (AVR32) board

Haavard Skinnemoen haavard.skinnemoen at atmel.com
Wed Jul 30 10:35:00 CEST 2008


Haavard Skinnemoen <haavard.skinnemoen at atmel.com> wrote:
> From: Julien May <mailinglist at miromico.ch>
> 
> The Hammerhead platform is built around a AVR32 32-bit microcontroller
> from Atmel.  It offers versatile peripherals, such as ethernet, usb
> device, usb host etc.

Since I didn't receive any explanation of why it's bad with two
maintainers, I've applied this as-is to my 'next' branch:

	git://git.denx.de/u-boot-avr32.git next

I intend this to be a fairly stable branch which will normally not be
rebased. Since the patches aren't applied there until they have been
fully reviewed, it's unlikely that anything needs fixing once it's been
applied.

Mistakes do of course happen, so I'm not saying that I will _never_
rebase the tree, I'm just saying that I will try my best not to.

I'm also going to try out a 'topic branch' strategy so that even if the
history does get mangled, the commit IDs of the unaffected topics will
be stable as I just re-pull the topic branches after fixing whatever it
is that needs fixing. Currently, my tree has two topic branches:
'eth-cleanup' and 'hammerhead', but I expect at least two more boards
to join in before the next merge window.

So if you need to pull something from 'next', please try pulling a
topic branch as it is more likely to stay stable than the 'next' branch
itself.

When the next merge window opens, I'll pull all the topic branches into
'master'. Or perhaps it's better to just pull the 'next' branch. I'm
not really sure about this.

I'd appreciate some feedback from other maintainers on whether or not
you think this sounds like a good plan.

Haavard




More information about the U-Boot mailing list