From: Christian Lamparter <chunkeey@googlemail.com>
To: Tomasz Guszkowski <tsg@o2.pl>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54usb: corrected USB ID for T-Com Sinus 154 data II
Date: Thu, 7 Feb 2013 16:20:15 +0100 [thread overview]
Message-ID: <201302071620.16014.chunkeey@googlemail.com> (raw)
In-Reply-To: <20130206233951.0cf8e25b7963bbd170b37899@o2.pl>
On Wednesday, February 06, 2013 11:39:51 PM Tomasz Guszkowski wrote:
> On Tue, 5 Feb 2013, Christian Lamparter wrote:
> > OT: The latest supported firmware for LM87 is: 2.13.25.0.lm87.arm
> > Did you experience issues with the new version, or do you simply
> > stick with the old 2.13.1.0 because it does work just as well?
>
> I have just tested behavior of T-Com with 2.13.25.0.lm87.arm
> (md5sum 39be687c87544b892e7a8ffe7ffd9371) in managed mode.
> Ewerything what was tested worked perfectly:
> 1. iwlist wlan0 scan
> 2. connecting to open network
> 3. connecting to WEP 128-bit
> 4. connecting to WPA-PSK (TKIP)
> 5. connecting to WPA2-PSK (AES)
>
> I am particularly impressed by working WPA2, with 2.13.1.0
> it didn't work.
Ok, that is actually important. I didn't know that 2.13.1.0
had problems with AES, I'll check that again. Thanks for
letting me know about this.
> Thanks for pointing newer firmware, with WPA2 support it's
> an excellent, sensitive card despite its age.
:-) [But of course: the driver is not done yet, I hope I'll get
around and add the automatic-reset-when-firmware-crashes feature
in the near future.]
Regards
Christian
next prev parent reply other threads:[~2013-02-07 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 22:39 [PATCH] p54usb: corrected USB ID for T-Com Sinus 154 data II Tomasz Guszkowski
2013-02-07 15:20 ` Christian Lamparter [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-05 22:39 Tomasz Guszkowski
2013-02-05 21:10 Tomasz Guszkowski
2013-02-05 21:43 ` Christian Lamparter
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=201302071620.16014.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tsg@o2.pl \
/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).