From: Stefan Schmidt <stefan@osg.samsung.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>, linux-wpan@vger.kernel.org
Cc: alex.aring@gmail.com, werner@almesberger.net
Subject: Re: [PATCH atubs-fw 0/4] ATUSB firmware changes towards a 0.2 release
Date: Thu, 21 May 2015 16:40:14 +0200 [thread overview]
Message-ID: <555DEE4E.4020307@osg.samsung.com> (raw)
In-Reply-To: <555C8A77.3070203@datenfreihafen.org>
Hello.
On 20/05/15 15:21, Stefan Schmidt wrote:
> Hello.
>
> On 20/05/15 15:18, Stefan Schmidt wrote:
>> Hello.
>>
>> Nothing to be appliad to the kernel but rather the atusb firmware repo. Just
>> sending it here as it is releated to the mainline driver and the device users
>> are reading here.
>>
>> These are the four patches I consider we need to have a working 0.2 release.
>> The revert might be only needed for my qemu setup with USB passthrough, but
>> without it I'm not able to get the device to show up in qemu. Thoughts
>> appreciated.
>>
>> Using RX_AACK_ON sounds like a good idea as we loose nothing but work also work
>> well with nodes using ARET.
>>
>> Bumping to version 0.2 and adding the need magic to add a valid DFU suffix to
>> the firmware file. I will followup with a mail attaching the binary I'm using
>> right now and I consider the final 0.2 if everyone agrees with these patches.
>>
> Binary firmware image attached. Alexander, if you could give that a test
> it would be appreciated.
>
> Everyone else with a atusb please test as well if you have the time.
The pending patches have been pushed and I tagged the atusb firmware 0.2
release in git:
http://projects.qi-hardware.com/index.php/p/ben-wpan/source/changes/v0.2-atusb-fw/
The firmware binary should be available from the website soon. If you
are eager you can get it here:
http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/web/releases/atusb-0.2.dfu
If anyone has patches for the firmware pending or upcoming please CC me.
I should be able help reviewing, testing and pushing them.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-05-21 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 13:18 [PATCH atubs-fw 0/4] ATUSB firmware changes towards a 0.2 release Stefan Schmidt
2015-05-20 13:18 ` [PATCH atubs-fw 1/4] Revert "atusb/fw/usb/: enable MCU reset on USB bus reset after config selection" Stefan Schmidt
2015-05-20 15:33 ` Alexander Aring
2015-05-20 16:37 ` Stefan Schmidt
2015-05-20 13:18 ` [PATCH atubs-fw 2/4] atusb/fw: Use RX_AACK_ON instead of RX_ON in the firmware Stefan Schmidt
2015-05-20 13:18 ` [PATCH atubs-fw 3/4] atusb/fw: Add build system support for adding a DFU suffix to the fw file Stefan Schmidt
2015-05-20 16:31 ` Werner Almesberger
2015-05-20 16:39 ` Stefan Schmidt
2015-05-21 8:19 ` Stefan Schmidt
2015-05-20 13:18 ` [PATCH atubs-fw 4/4] atusb/fw: Bump minor version to mark first public release Stefan Schmidt
2015-05-20 13:21 ` [PATCH atubs-fw 0/4] ATUSB firmware changes towards a 0.2 release Stefan Schmidt
2015-05-21 14:40 ` Stefan Schmidt [this message]
2015-05-21 15:39 ` Alexander Aring
2015-05-21 16:39 ` Stefan Schmidt
2015-05-21 20:45 ` Alexander Aring
2015-05-21 21:01 ` Alexander Aring
2015-05-22 7:58 ` Stefan Schmidt
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=555DEE4E.4020307@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@datenfreihafen.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