Stefan Schmidt wrote:
> Which means the firmware side would be already usable even if not
> finished? Seems I need to compile the newest firmware. :)
You can see it being used by the user-space tools. E.g.,
ben-wpan/tools/atrf-txrx/atrf-txrx.c:rtt_slave_hmac
and
ben-wpan/tools/lib/atusb-common.c atusb_{rx_mode,rx,tx}
> Sounds good. Feature like auto ACK and auto retransmit will then be
> handled in the firmware as well I think.
Yes, it has to know at least which set of states to go to.
> E.g. the hw address filter callback in the atusb driver
> will need to transfer the changes, best in one go, to the firmware so
> it can set the registers for the filter accordingly
Does this have to be fast ? From reading the WPAN standard, I
got the impression that these settings were fairly static.
> Makes you feel like the old ATM networking days or was that before
> DaveM was in charge? ;)
If I remember correctly, he took networking under his wings
in the course of this (rather long-running) project.
> Hmm. Is anything else using the uSD slot for plain SPI or is the
> spi_atben the only customer?
There could be other users even if there are no in-kernel users
right now. Note that the SPI pin assignment is device-specific
does not have to follow any convention (such as MMC SPI mode.)
- Werner
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
