From: Denis Vlasenko <vda@ilport.com.ua>
To: andi@lisas.de
Cc: acx100-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH] TNETW1450: successful device initialization
Date: Wed, 1 Feb 2006 11:20:15 +0200 [thread overview]
Message-ID: <200602011120.15686.vda@ilport.com.ua> (raw)
In-Reply-To: <20060201085205.GA9315@rhlx01.fht-esslingen.de>
On Wednesday 01 February 2006 10:52, Andreas Mohr wrote:
> Hi all,
>
> - add initial support for new TNETW1450 USB chip (available on the market since
> June or so): successful firmware booting, driver initialization working up to
> a working iwconfig. Any network traffic whatsoever NOT working yet.
> VERY EXPERIMENTAL! (especially since TNETW1450 sometimes uses enhanced,
> longer structs for some IEs)
> - add a ton of different TNETW1450 USB device VID/PID combinations; it's
> highly likely that there will be many more TNETW1450 devices in the future...
> - add many more firmware command IEs
> - firmware upload cleanup (rename variables to better names, unify the various
> firmware upload implementations, ...)
> - add FIXME comment to remind about semaphore -> mutex conversion
Applied, mega thanks!
Do you have a "HOWTO sniff USB under Windows" or URL to it?
May be helpful for other potential developers.
> The TNETW1450 firmware image is currently called acx111usbcRR, with RR being
> the currently used radio ID 0x1b ("1b"): acx111usbc1b.
Patch actually says "tiacx..." which is what you obviously intended.
> NOTE that DWL-120+ firmware image - due to unified firmware name creation -
> now has a different name, too:
> acx100usbc0d! (Denis, simply revert it if you're offended by this change).
No objections, only changed that to _uppercase_ hex radio id
("tiacx111usbc1D") in order to match PCI firmware name convention.
> Total driver size increase: less than 2kB!
Wonderful
> ACX100 mini-PCI, DWL-120+ and TNETW1450 are all still working as before.
--
vda
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next parent reply other threads:[~2006-02-01 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060201085205.GA9315@rhlx01.fht-esslingen.de>
2006-02-01 9:20 ` Denis Vlasenko [this message]
2006-02-01 9:29 ` [PATCH] TNETW1450: successful device initialization Andreas Mohr
[not found] ` <1138786708.26656.4.camel@curcuma.ens.fr>
2006-02-01 9:55 ` Denis Vlasenko
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=200602011120.15686.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=acx100-devel@lists.sourceforge.net \
--cc=andi@lisas.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).