Mariano Alvira scrisse: > The hard part about supporting new hardware platforms is dealing with > the hardware: the radio, the UART, or doing USB->serial in the case of > a chip that has USB builtin. Contiki doesn't help much with this.
I was recently pondering on this same issue, and while you're correct on your opinion (ie. doing it directly through libmc1322 is lighter) I believe Bastian's point was a bit different. Going the contiki way may help for a good bunches of widely available platform already supported by contiki but not yet by linux-zigbee (yay, damn telos/sky, I'm looking at you too), as well as other platforms which will be introduced in the future. In this case, it makes sense to pass through another contiki radio layer (core/dev/radio.h maybe? Is it the lowest abstraction?) together with a contiki firmware similar to the one you did for mc1322, in order to gain some more hardware options for interfacing, avoiding the task of a firmware completely written from scratch. Given all the above, I think Bastian proposal was good, and I'd like to see it pushed on... Ciao, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S. | lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
