Hi Stefan, >Nice, that you used the same schematics and build your boards! >Do you by any chance have the infrastructure to handle a bigger run of these? We often get asked about such a device >for easy hacking with ieee802154 from a laptop or desktop without any SPI connections available. This is exactly the reason I am interested in the device. I want to set up a simple 6LoWPAN network, but do not have any SPI connections. >The run Werner did was around 100 - 120 pieces for atusb IIRC. My best guess would be that there could be interest for >another 50-100 depending on the promotions. So-far, we have only built two atusb modules. We are in the process of loading the firmware and testing, so I am not sure if the boards are functional yet. At this time, we are not set up to produce numbers in the 50-100 range. This may change once we successfully test the boards. >Werner did a great job on documenting the whole design to deliver process so most pitfalls should be known and the risk >reduced. If you stay with the same chips the firmware and factory testing things are also ready. Yes, Werner's web-site has lots of useful info. I will report our status once we complete testing :) >>Hmm, you really only want to transmit some data between two linux hosts here, right? Correct. >In that case you can simply use the now mainline atusb driver and its 0.2 frimware and tranbsmit your data over the >ipv6 sockets we offer with 6lowpan. >Unless I misunderstood you and you wanted to to something more low level with ieee802165 there would be no need for >you to hack on the firmware. You are welcome to if you want, but I see no need for you right now. :) Ok that is great info Stephan. I am not intimately familiar with the Linux networking stack, so I am not sure exactly how to communicate with the device. As you indicated, I assumed I would communicate with the device via a socket interface. Since I don't really know what kind of interface is presented by the device, I was thinking that I would have to dig into the firmware to discover the underlying protocol needed to control the device. In other words, once I open a socket, I am not entirely sure what to do next. Do you have any suggestions or references that might help with my understanding? I hope to be experimenting with the device soon. When I am successful, I will share my experiences. --Geoff -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
