From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kirill Zut <kirill.zut@promwad.com>,
linux-wireless@vger.kernel.org,
Hin-Tak Leung <htl10@users.sourceforge.net>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Subject: Re: [PATCH 2.6.34] rtl8187: ad-hoc mode support
Date: Thu, 29 Jul 2010 14:03:50 -0500 [thread overview]
Message-ID: <4C51D096.7090607@lwfinger.net> (raw)
In-Reply-To: <20100729180426.GC2424@tuxdriver.com>
On 07/29/2010 01:04 PM, John W. Linville wrote:
> Don't you need something to make it beacon?
Indeed he does. This code allows the user to set ad-hoc mode, but I could not
establish a connection. The setup that I used worked for a b43 - b43 link, but
failed if either end used rtl8187. NACK.
Larry
next prev parent reply other threads:[~2010-07-29 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007291835.46159.kirill.zut@promwad.com>
2010-07-29 17:01 ` [PATCH 2.6.34] rtl8187: ad-hoc mode support Hin-Tak Leung
2010-07-29 18:04 ` John W. Linville
2010-07-29 19:01 ` Larry Finger
2010-07-29 19:03 ` Larry Finger [this message]
2010-07-29 20:52 ` Hin-Tak Leung
2010-07-30 23:53 ` jpo
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=4C51D096.7090607@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--cc=kirill.zut@promwad.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).