From: Stefan Schmidt <stefan@osg.samsung.com>
To: Geoff Chapman <geoff.chapman@mmbresearch.com>,
Alexander Aring <alex.aring@gmail.com>,
linux-wpan@vger.kernel.org
Subject: Re: atusb availability
Date: Fri, 22 May 2015 15:05:53 +0200 [thread overview]
Message-ID: <555F29B1.4010503@osg.samsung.com> (raw)
In-Reply-To: <CAHwW563+_YBjKLU7Pm8igBeOmWfUg_VEMhQ9Y-GosTdCPLBGUw@mail.gmail.com>
Hello.
On 13/05/15 19:24, Geoff Chapman wrote:
> Hi Alex,
> I just wanted to thank-you for your reply, it certainly helped with my
> understanding. Initially, I thought the device was a HardMAC device,
> so thank-you for correcting me on that. It seems that the device
> simply implements a USB-to-SPI interface.
Funny enough our first driver for it was actually a fake spi master
driver which did nothing else but connected to the normal at86rf23x
driver and transmitted all SPI message over usb to the device. :)
That worked ok-ish but was a performance problem for transmit and
receive. Thus this part was moved into the firmware. We kept the way of
setting register for configurations like this though.
> I have used the schematics at [0] to build a few boards of my own. I
> would like to use the two boards to send data between two laptop
> computers running linux.
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.
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.
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.
I'm not doing hardware myself so I'm not sure how risky this all could
be but I see a need for this kind of devices. Especially with good
plug'n'play support in the mainline kernel this could have potential.
Still not talking thousands here as it will stay a developer/hacker only
device.
If you have no time/interest/infrastructure for this but someone else
has please speak up here. Going a route through indigogo or kickstarter
might also help to determine the interest to have a better idea who big
a run should be.
> The description at [1] indicates that the ATMega firmware implements a
> "home-brew protocol on top of USB". My plan is to do the following:
>
> 1. Examine the source ATUSB firmware source code to determine the
> home-brew protocol.
> 2. Write some application software in C for the two linux PCs using
> Netlink sockets to communicate with the devices and transfer data
> between the two PCs.
>
> I was wondering -- do you think I am on the right track? Do you have
> any suggestions?
Hmm, you really only want to transmit some data between two linux hosts
here, right?
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. :)
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-22 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 15:55 atusb availability Geoff Chapman
2015-04-23 8:30 ` Alexander Aring
2015-05-13 17:24 ` Geoff Chapman
2015-05-13 20:05 ` Alexander Aring
2015-05-22 13:05 ` Stefan Schmidt [this message]
2015-05-26 18:29 ` Geoff Chapman
2015-05-27 9:06 ` Stefan Schmidt
2015-05-27 13:00 ` Michael Richardson
2015-05-27 13:18 ` Stefan Schmidt
2015-05-27 13:29 ` Ralph Droms (rdroms)
2015-05-27 13:32 ` Stefan Schmidt
2015-05-27 13:47 ` Alexander Aring
2015-05-27 16:04 ` Ralph Droms (rdroms)
2015-06-02 16:03 ` Alexander Aring
2015-05-27 16:06 ` Ralph Droms (rdroms)
2015-05-27 16:36 ` Stefan Schmidt
2015-05-27 14:00 ` Michael Richardson
2015-05-27 16:07 ` Ralph Droms (rdroms)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=555F29B1.4010503@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=geoff.chapman@mmbresearch.com \
--cc=linux-wpan@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.