From: "Antoine Beaupré" <anarcat@koumbit.org>
To: Ben Hutchings <ben@decadent.org.uk>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: 645055@bugs.debian.org
Subject: Re: Bug#645055: realtek 8188CE ad-hoc mode not supported
Date: Wed, 12 Oct 2011 21:46:07 -0400 [thread overview]
Message-ID: <87wrc9r7ds.fsf@marcos.anarcat.ath.cx> (raw)
In-Reply-To: <1318461858.4024.197.camel@deadeye>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Thu, 13 Oct 2011 00:24:12 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> I looked a little further and saw that nl80211 does support changing
> interface type (mode). But this driver (rtl8192ce) only supports
> creating new interfaces, not changing their type.
>
> Should mac80211 drivers generally support changing interface type
> (change_interface operation)?
Seems to me really counter-intuitive that it didn't work. It was the
first time I ever see such a problem.
I have seen numerous drivers not support "Master" or "Monitor" mode,
because of limitations of the implementation or the hardware, but if
this is purely a API problem, it seems like a problem that should be
fixed...
Is this the right place though?
A.
--
The idea that Bill Gates has appeared like a knight in shining armour to
lead all customers out of a mire of technological chaos neatly ignores
the fact that it was he who, by peddling second-rate technology, led
them into it in the first place. - Douglas Adams (1952-2001)
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-10-13 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111012052940.17383.59248.reportbug@localhost>
[not found] ` <1318424918.4024.180.camel@deadeye>
[not found] ` <87pqi2s0cg.fsf@marcos.anarcat.ath.cx>
[not found] ` <20111012160135.GK3366@decadent.org.uk>
2011-10-12 23:24 ` Bug#645055: realtek 8188CE ad-hoc mode not supported Ben Hutchings
2011-10-13 1:46 ` Antoine Beaupré [this message]
2011-10-13 2:10 ` Larry Finger
2011-10-13 2:25 ` Ben Hutchings
2011-10-13 2:31 ` Antoine Beaupré
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=87wrc9r7ds.fsf@marcos.anarcat.ath.cx \
--to=anarcat@koumbit.org \
--cc=645055@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.