Re: ?????: [PATCH 10/10] ieee802154: add at86rf230/rf231 spi driver



Maxim Osipov wrote:
Hi Marcel,

On Tue, Jun 2, 2009 at 12:36 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
For Bluetooth naming directories 'bluetooth' is logical, as 802.15.1
standard is a less known name, doesn't incorporate latest changes
from Bluetooth, etc.
and so is IEEE 802.15.4 hence we propose using "zigbee" here. Using the
mac80211 has historical reasons and 802.11 is a known name and even used
on product marketing material. IEEE 802.15.4 is not. We are also using
the term "wimax" and not its IEEE numbering.

Actually, ieee802154 is better in this case, because as Dmitry
mentioned, an entire family of standards is implemented on the top of
it, including:

- ZigBee
- 6LoWPAN
- ISA100.11a
- WirelessHART
- and probably something I don't know about
I'll tack on tosmac (the tinyos protocol).
The platforms I support have out of kernel support for a cc2420 (802.15.4) radio
using that protocol. In the embedded sensors field it seems to be
pretty common to use linux nodes as gateways to systems running various realtime
/ light weight OSes.

As Maxim stated there are a lot of protocols out there.

Thank you to Dmitry and co for your work on this project, I'll be following
your progress with interest (and when I have a sec adding support for the cc2420
if no one else does it first ;)

---
Jonathan Cameron


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: usb drive
    ... > been able to mount the other drive. ... Seems its not recognised - perhaps the manufacturer didnt use a standard ... protocol. ... and see if there is some comment for support for it. ...
    (alt.os.linux)
  • compile error on alpha - binutils problem?
    ... {standard input}:246: Error: macro requires $at register while noat in effect ... # PCCARD support ...
    (Linux-Kernel)
  • Re: How often do you have to work around implementations?
    ... Something that's bitten me a few times recently is cases in which implementations were buggy -- rarely, to be fair, in the core C language, but "standard" system extensions like POSIX conformance. ... modifying address lengths take pointers to "size_t" objects. ... If the system is FLOSS, I report a bug, at least when I know that the developers originally intended to support what I was doing. ... Replace "%N$*M$lu" with more "normal" format specifiers and repeat printf arguments explicitly that were initially re-used by the original format specifiers. ...
    (comp.lang.c)
  • Re: New Ethiopian Find - Oldest Biped At 3.8-4 mya
    ... >> This is not an example of a double standard. ... > criticise arguments you don't support for not ... *elimination of human hair as it relates to swimming. ... primarily--neither set out to address hair reduction) required a rather ...
    (sci.anthropology.paleo)
  • Re: Testing portability to non-2s-complement machines
    ... to all standard systems, including such hypothetical ones. ... so the representation of numbers is quite relevant. ... That an overflow occurs ... decide to only support standard programs (or "Forth ...
    (comp.lang.forth)