sixlowpan: rename to sixlowpan_legacy

[miri64]

Since #1680 turns out to become quite a nightmare review-wise, I decided to split and clean it up a little. First point on the agenda is to make it more or less independent from the old 6LoWPAN module. For this I renamed the old module to sixlowpan_legacy and I will remove the move commit from #1680. Though I recycled lot of the original code in #1680, it is not what it used to be, so the changes wouldn't be that visible anyways.

[miri64]

Travis fails due to cppcheck and externc.sh. Must I really do this for this?

[OlegHahm]

Travis fails due to cppcheck and externc.sh. Must I really do this for this?

I'd say no.

For this PR in general: I'm a bit reluctant to rename sixlowpan to sixlowpan_legacy without including a proper sixlowpan into RIOT master.

[miri64]

That's what #1680 is for ;-)

[OlegHahm]

So, this PR is mainly split for review and intended to be merged along with #1680? Is there a need for sixlowpan_legacy after #1680 is merged?

[miri64]

For older boards maybe.

[miri64]

Rebased

[miri64]

Rebased

[miri64]

Rebased

[miri64]

Rebased to master

[miri64]

Rebased

[miri64]

Had do redo the whole thing due to heavy changes in #1404 and #1767.

[LudwigKnuepfer]

needs rebase

[miri64]

sigh not today… this is just to complex again -.-

[miri64]

Rebased to master

[miri64]

Will rebase next either after review of #1680 or when heavy changes to rpl stop.

[OlegHahm]

I think we should not rename this before the new network stack is ready anyways. In the best case we don't need this PR and can just remove the old implementation completely.

[miri64]

Yes of course: the goal of this PR is more to get the old implementation out of the way to give me breathing room for the new implementation, than a thing I actually want to do ;-)

[miri64]

Abandoned. New implementation will get a ng_ prefix (see #2278)