Am Sat, 14 Mar 2015 13:59:06 +0100
schrieb Jozef Maslik ma...@binarylemon.com:
Hi Jozef,
Some example with major differences:
SPI has min 3 variants: DSPI (K family), SPI (L, M family), SPI(L0x
family) UART has min 3 variants: 1. K, M family, 2. L family, 3. L0x
family low power UART is in L
For the kw01 you should look at the PR that the Phytec guys are working on
(Johann Fischer and Jonas Remmert et.al.) which can be found at
https://github.com/RIOT-OS/RIOT/pull/2328
Best regards, Joakim
On Mar 14, 2015 2:00 PM, Jozef Maslik ma...@binarylemon.com wrote:
Hi,
@Joakim, It is not
We have used some conditional compilation in drivers where the
differences have been somewhat manageable. See the UART driver for
example. If the entire module is different then I guess I would prefer
to have two separate C-files for the two solutions rather than forking
the entire kinetis_common
Hi,
On 03/13/15 19:59, Hauke Petersen wrote:
Of course this leads to some duplication of code, but in the end it
leaves the overall folder structure very clean and it is always clear,
where the code you are currently building is coming from.
No. Code duplication is evil.
It leads to
Hi,
@Joakim, It is not easy question :)
In short, we can say, there are differences between families based on core type
but it is not true for all options. MCUs with core Cortex M4 have different
modules compare to Cortex M0+ and here is difference compared to L0x family
which use some
Hi,
How we want deal with the difference between variants of peripherals in
Freescale Kinetis families (I mean, what is RIOT OS prefered way)? Here is
difference between families - for example between K family vs L family. And if
I remember correctly ;), there can be difference between
