Fixed small typo in README.
Split LDFLAGS,  -Wl,-s cannot be used when debugging
Rough Nokia Buzzer support

Completely rewritten buzzer.[ch]. The central function is now
buzzer_play, that accept an array of notes defined thusly:
- first 4 MSB are the pitch
- next 2 bits specifies octave
- last 10 bits define duration
There are also 2 "meta" notes:
0x___0 defines a rest (silence)
0x___F is a "stop" note, ending a melody sequence.

TI license was removed as the file was completely rewritten.

Keep in mind that the current implementation does not power save; the
watch is active and "locked" for the whole duration of a melody. This is
of course unacceptable, and will be solved soon by using the timer
module.
Aesthetic changes

Added a colon to separate notes and note numbers in comments.
Inlined the buzzer_init call

Since it is called only once in the firmware I'm sure GCC does this automatically during optimization. However, defining it explicitly is always better.
Corrected typo in documentation.
Small bug fix

Interrupt wasn't disabling but re-enabling, and that could lead to some unexpected problems.
timer1 not returning properly from sleep

This fixes a bug that could lead to an always sleeping watch, because it would never come out of LPM3.
Arbitrary LPM for timer0_delay

Added support user-supplied Low Power Mode for the timer0_delay function. It is the user now that decides in which power mode is the watch sitting whilst waiting for the delay. This patch is fundamental for buzzer, because it uses SMCLK which is disabled in LPM3.
Fixed critical initialization issue

Buzzer must be initialized after the timer subsystem is ready, because buzzer depends on it!
Updated buzzer to take advantage of new timer0_delay

Now the buzzer function consumes a lot less power, because it waits in low power mode while playing melodies.
Fixed potential bug in timer macro

Macro functions should always be wrapped in parentheses.
Small aesthetic fixes in buzzer docs.

A list was parsed incorrectly by Doxygen.
Fix breakage caused by API change on timer_delay()
Make the accelerometer work again

The accelerometer handling code was being executed *after* the code
that verifies if the interrupt was generated by a button. If the
interrupt was not generated by a button then the function would return
preventing the accelerometer code to ever execute.
Remove CONFIG_FREQUENCY

This was only used by simpliciTI which is now disabled.
Add button debouncing to the button interrupt handler

This patch makes the watch ignore all button presses that were quicker
than a specified time interval. Because this uses the 10Hz timer to
measure the time interval, a fail-safe mechanism was implemented
to allow the buttons to still work even when the timer is disabled.
In this case, the buttons won't be debounced and only short button
presses will be detected.
Increase Timer0 CCR0 frequency from 10Hz to 20Hz

This allows the "deboucing" delay implemented in
5a25c773c777db81baf7ffc86d7980e66df9e73b to detect shorter button
presses, improving input usability.

Since at the moment only the ports driver was using the 10Hz timer,
there is no harm in increasing its frequency to 20Hz, with the exception
of a somewhat negligible battery usage increase. Future modules might
also benefit from this frequency, specially for measurements of small
periods of time.
drivers/rtca: Implement days of week strings and RTC start/stop

Note: The RTC driver automatically calculates the correct day
of week based on the date that is stored. For this reason, the clock
module does not allow you to change the day of week string,
while in edit mode.
Implement item based menu_editmode

Looking at both alarm and clock modules, I was still not happy
with how the code had to be written to properly use menu_editmode.
In special, the looping through all edit items had to be done manually
by all modules. Moreover, all modules also needed to conditionally
chose the item to blink/set. All of this simple tasks are always repeated
between modules implementing menu_editmode. For this reason, I merged
them into the openchronos menu_editmode functionality so that the tasks
are performed automatically by the openchronos core.
For now, this functionality is taking a hundred bytes more than without
it, which I think is fine since it really improves code readability.

The clock and alarm modules were updated to use the new API.
The annotated doxygen documentation was also updated.