Wouldn't it adapt these two platforms to the new API? It seems to be mostly function renaming.

It's definitely more work than I was willing to put into this for now.
But of course, the goal is to transition to the new interfaces and purge the deprecated ones.

By the way - there currently is not a single implementation of the periph/rtc.h interface in master.

It's definitely more work than I was willing to put into this for now.
But of course, the goal is to transition to the new interfaces and purge
the deprecated ones.

From a brief look it appeared not much more effort than the current PR, since the interfaces look quite similar, but of course I have not checked in detail (where the devil might wait for you).

I have - the interfaces themselves are not even the hairy part.
There is no tests/periph_rtc, no sys/shell/commands/periph_rtc.c, ...

@OlegHahm this RTC implementation on msba2 was the only thing in RIOT which was working from the beginning of my thesis:)

but +1 to deprecate it now and remove it with the release after the next one.

There's a sc_rtc.c.

I'm not going to add anything to this PR in the immediate future.

@OlegHahm if you think it's a bad idea to deprecate it just say so, otherwise I suggest merging this now and taking care of the rewrite in a different PR.

@OlegHahm ping - if you don't want this let's close it - if you want it changed say so.

(or you could just decide you don't care..)

As I said: I would prefer adapting to the new API over deprecating the old one, but I'm not against it - and haven't looked how difficult the actual task is, so far.

Superseded by #2060