Hello.
On Mon, 2013-03-25 at 03:50, Werner Almesberger wrote:
> 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}
ok, cool.
> > 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.
Its mostly state machine changes from basic to extended mode anyway.
I think I will just wait and see with what you come up for the new
driver. :)
> > 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.
They are. I just think it would be nice to save rountrip in
configuration as well as in data. The callback form the stack
indicates all changes so we could go and update them in one go, one
usb urb so to speak, and let the firmware write the registers.
regards
Stefan Schmidt
------------------------------------------------------------------------------
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
