From: Alexander Aring <alex.aring@gmail.com>
To: Wei Chen <chenwei.sh99@gmail.com>
Cc: werner@almesberger.net, linux-wpan@vger.kernel.org
Subject: Re: 15.4 serial driver
Date: Tue, 31 Mar 2015 09:48:10 +0200 [thread overview]
Message-ID: <20150331074807.GA21839@omega> (raw)
In-Reply-To: <CABA_Ov2K0vJD5dDur7Vwa3h3AyLoXKEUyk5cDK9e_Qf-k_LJ1Q@mail.gmail.com>
On Tue, Mar 31, 2015 at 12:07:51AM -0700, Wei Chen wrote:
> Alex,
>
> I'm trying to follow the 6lowpan demos you did, and trying to write a
> driver a new hardware 15.4 dongle. But I'm confused about the status of
you mean a usb dongle?
> 15.4 driver. The mainline does not have either atusb or serial interface
> driver under ieee802154 dir. Will the serial driver be integrated on
> mainline?
If usb dongle I would be very happy to use the existing atusb protocol,
then you need write a firmware only and the driver already exists.
That's my idea to support the RAVENRZUSBSTICK [0]. The atusb and
RAVENRZUSBSTICK use both some atmel mcu and a at86rf23x. The
RAVENRZUSBSTICK uses the at86rf230 and I heard it's a little bit harder
to use them as the at86rf231.
The idea is to create a atusb firmware project to support building both
of them by replacing some $BOARD_CONFIG file.
Now to your questions:
atusb:
The atusb is in a very good state, except one thing. It does not support
async xmit handling. Maybe when I investigate ~2 days then I can bring
async xmit support, it's not so much complicated. You are welcome to
support it. The lastest driver version which should also easily
cherry-picked on current mainline, the lastest version can be found at [1].
For the xmit_async handling:
You need to use xmit_async instead xmit_sync, but this reuquire a async
usb handling inside this callback.
Firmware:
You can find the actual atusb firmware at [2].
serial driver:
That's not in a good state und if you want to support a "usb dongle" I don't
recommend to making some protocol stuff over usb. You have some usb
timing constraints and the atusb firmware tries to handle that with some
caching functionality etc.
The serial driver is okay for connecting to an UART bus only.
Nevertheless you can also try to get the serial driver mainline. I will
review the driver. Lastest version is [3]. But this driver is in an
horrible state, which begins with the name of this driver "serial"
which ends in a modulename "serial.ko". :-)
I hope I could answer your questions. Please let me know your further
handling about your dongle project.
- Alex
[0] http://www.atmel.com/tools/rzusbstick.aspx
[1] https://github.com/linux-wpan/linux-wpan-next/commit/60301df6c1f2833b1af982e3647e958414a76735
[2] http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/atusb/fw
[3] https://github.com/linux-wpan/linux-wpan-next/commit/546618171de2be30236aab86f3ee323b425e2bf5
parent reply other threads:[~2015-03-31 7:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CABA_Ov2K0vJD5dDur7Vwa3h3AyLoXKEUyk5cDK9e_Qf-k_LJ1Q@mail.gmail.com>]
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=20150331074807.GA21839@omega \
--to=alex.aring@gmail.com \
--cc=chenwei.sh99@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=werner@almesberger.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox