linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Franz Apeltauer <franz.apeltauer@gmx.at>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: 2 compile errors: rt2x00firmware.c and mesh.c
Date: Tue, 11 Mar 2008 23:22:45 +0100	[thread overview]
Message-ID: <200803112322.45274.IvDoorn@gmail.com> (raw)
In-Reply-To: <47D70459.7000703@gmx.at>

On Tuesday 11 March 2008, Franz Apeltauer wrote:
> Luis R. Rodriguez schrieb:
> >>  Loaded the new tarball.
> >>  It compiles fine.
> > 
> > And it works too I hope? :)
> > 
> >   Luis
> > 
> Unfortunately not. I am still trying to find out, if it is my fault or not.
> 
> It seems, that it only allows Managed mode.
> "iwconfig wlan0 mode Ad-Hoc" and "iwconfig wlan0 mode Master" both give 
> me this error:
> Error for wireless request "Set Mode" (8B06) :
>      SET failed on device wlan0 ; Invalid argument.
> 
> I intended to use an ad-hoc connection between 2 PCs.
> Since I have no access point I cannot test much at the moment.
> 
> Is it supposed to provide ad-hoc and master mode on rt2500 (pci)?
> Probably not yet, because it is not in the list 
> (http://linuxwireless.org/en/users/Drivers). Right?

rt2500pci should work with adhoc and master mode, I have to note that
with versions up to 2.6.25 this is disabled due to lack of testing.
I don't know which rt2x00 version is packaged in the tarball, but if it
is older then 2.1.0 then adhoc and master mode is disabled in the driver.

Also note that although it is currently enabled, I still have not
received test reports about it, so I cannot claim that it is working.

Ivo

  reply	other threads:[~2008-03-11 22:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 23:42 2 compile errors: rt2x00firmware.c and mesh.c Franz Apeltauer
2008-03-03  0:32 ` Johannes Berg
2008-03-03  3:52   ` Luis R. Rodriguez
2008-03-05 23:12     ` Franz Apeltauer
2008-03-05 23:15       ` Johannes Berg
2008-03-05 23:25         ` Franz Apeltauer
2008-03-05 23:34           ` Johannes Berg
2008-03-10 23:09             ` Franz Apeltauer
2008-03-08  2:59       ` Luis R. Rodriguez
2008-03-10 21:41         ` Franz Apeltauer
2008-03-10 22:21           ` Ivo van Doorn
2008-03-10 23:33             ` Luis R. Rodriguez
2008-03-11  0:07               ` Franz Apeltauer
2008-03-11  1:26                 ` Luis R. Rodriguez
2008-03-11 20:06                   ` Hauke Mehrtens
2008-03-11 21:24                     ` Luis R. Rodriguez
2008-03-11 22:14                   ` Franz Apeltauer
2008-03-11 22:22                     ` Ivo van Doorn [this message]
2008-03-11 23:01                       ` Franz Apeltauer
2008-03-11 23:09                         ` Ivo van Doorn
2008-03-16  0:33                           ` Franz Apeltauer
2008-03-17 17:12                             ` Luis R. Rodriguez
2008-03-03  9:37   ` Ivo Van Doorn

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=200803112322.45274.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=franz.apeltauer@gmx.at \
    --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).