On 6/18/11, Stefan Schmidt <ste...@datenfreihafen.org> wrote:
> Hello.
>
> On Fri, 2011-06-17 at 20:30, Dmitry Eremin-Solenikov wrote:
>>
>> On 17.06.2011 19:55, Stefan Schmidt wrote:
>> >Hello.
>> >
>> >On Fri, 2011-06-17 at 19:31, Dmitry Eremin-Solenikov wrote:
>> >>
>> >>Sorry for ignoring this patch for sooo loooong. A bit better (IMHO)
>> >>patch was commited recently by Alexander/updated by me, which just
>> >>handles this few commands in a special
>> >>way.
>> >
>> >Can you sched some light one your plans regarding this project?
>> >
>> >It seems you just updated the git tree to 2.6.36 while completely
>> >ingnoring the 2.6.38 patches Jon posted long ago. I also never have
>> >seen the patches from Alexander on the list so you seem to have
>> >reviewed and approved them in private.
>> >
>> >Don't get me wrong here, I'm happy if you have time again to work on
>> >ieee802154/mac802154 and Alex works on the 6lowpan parts. I just would
>> >be interested in knowing if you plan to merge Jon's patches or move
>> >the git tree yourself to a more recent kernel and what kind of plans
>> >you have regarding mainline (or maybe staging).
>>
>> Please don't get me wrong :) I nearly don't have time to work on
>> IEEE/MAC 802.15.4. I might have some time, but not in near future.
>> For some time I was paid by my employee to work on this code. For
>> some time I was assigned to other projects. Currently (last few
>> months) Alexander (my colleague) is trying to dig into this project
>> and to contribute code. I'm supervising him on this (not so easy)
>> task. I really had no time to look for messages on this ML (and most
>> of other hobby projects were also stopped/delayed. Private life,
>> third kid).
>
> Thanks for taking the time to write this up. Private life and
> especially kids should always have higher priority no doubt. :)
>
> But with a plan laid out as below we at least know where to work on
> and what we can and can not expect from you. Thats always better then
> poking in the dark. ;)

Yeah, sorry for that.

>> * New drivers/hardware to support (at86rf230, rf212, cc25xx chips, etc.)
>
> Depends on people havceing access to the hardware as usual.

Yes. On the other hand there are still plenty of tasks/features to be
implemented
for current hardware. I myself have cards with rf231 and rf230 and I
have unsoldered
rf212 chip. Maybe I'll solder it on one of the rf231 (no real radio
output, but it will
help driver porting).

>> * Implement generic messaging code which can work across rs-232, USB,
>>   etc, like HCI interface for bluetooth. It should be extensible and
>>   simple enough (don't look at current serial protocol, it's a mess).
>> * Did I miss something?
>
> o CSMA-CA in combination with some MAC acceleration features (Werner
> did mention this as well)

Well, as I wrote earlier, the only CSMA-CA that should be supported is the
one completely handled by radio/firmware. There is really no point
in implementing CCA support in our stack.

> o Re-transmit in case of missing ACK? As far as I understand the spec
> the ACK must arrive in a given timeframe and thats why most of the
> chips implement hardware ACKing. While the at86rf231 can handle
> retransmissions as well the cc2420 is not able to do this. Sounds like
> a mac8021544 feature to me.

Yes, definitely. I'd generalise this a bit. mac802154 should handle
return codes from transmit. It can be either OK, timeout, etc.

> I will keep working on the cc2420 driver to get it reliable. Some
> patches should land here today. But its needs a lot more debugging and
> rewrite to work better (at all).

:)

> I also got myself some of the ATUSB devices Werner designed (at86rf231
> behind and ATmega32 and connected as USB stick to a linux host) and
> will help out there with the driver as well if needed. All this work
> is done for my diploma thesis and is only the groundwork for my actual
> work. Time has to show if I have some more spare cycles to tackle
> other tasks in the stack.

I'll look on that devices. ATUSB seems interesting for me, but I have no
previous experience with AVR, so it really depends on the amount
of my spare time.

-- 
With best wishes
Dmitry

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to