linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: developers@islsm.org
Cc: Jan Willies <jan@willies.info>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	kyle@mcmartin.ca, linux-wireless@vger.kernel.org
Subject: Re: [Developers] ISL3880IK crashes with 2.6.19.1 / .21.1
Date: Thu, 22 Nov 2007 22:35:43 +0100	[thread overview]
Message-ID: <200711222235.44079.chunkeey@web.de> (raw)
In-Reply-To: <4745EE3E.8090601@willies.info>

>
> Hmmz, I wasn't aware that p54 doesn't support encryption or AP mode yet.
> Is there any website/blog or something apart from linvilles commit log
> where I can read about its progress?
>
> Funny thing is, I had a chat with Michael Wu because p54 was segfaulting
> for me. Turned out that I was missing some crypto modules, which are
> only needed for encryption I guess. Therefore I assumed encryption is
> working.
>
"hardware encryption" does not work, since no one has implemented it.
but the software encryption is always available...

The AP Mode is a pain... Beause the firmware of the device changes the beacon
frames and does some accouting for the powersaving features...
There're workarounds, but they'll probably break something else.

Regards,
	Chr

  reply	other threads:[~2007-11-22 21:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 19:51 ISL3880IK crashes with 2.6.19.1 / .21.1 Jan Willies
2007-06-03 20:23 ` [Developers] " Jean-Baptiste Note
2007-06-03 22:33   ` Jan Willies
2007-11-22  1:03     ` Luis R. Rodriguez
2007-11-22  1:13       ` Luis R. Rodriguez
2007-11-22 21:01         ` Jan Willies
2007-11-22 21:35           ` Chr [this message]
2007-11-27  1:03             ` Jan Willies
2007-11-27  0:54           ` loswillios
     [not found] ` <200711271005.05396.chunkeey@web.de>
     [not found]   ` <474BE1BB.1010408@willies.info>
2007-11-27 11:58     ` Chr
2009-02-16 21:57 ` Jan Willies

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=200711222235.44079.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=developers@islsm.org \
    --cc=jan@willies.info \
    --cc=kyle@mcmartin.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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).