From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Attila Fazekas <turul64@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Herton Ronaldo Krzesinski <herton@canonical.com>
Subject: Re: [PATCH] rtl8187: Add Ad-hoc mode
Date: Wed, 22 Feb 2012 21:51:37 +0000 (GMT) [thread overview]
Message-ID: <1329947497.90659.YahooMailClassic@web29504.mail.ird.yahoo.com> (raw)
In-Reply-To: <CAFmNhL=5TSTZ94ZrSUztG9Hs28Mqk8vMB7rS51SNgE2RCK5s7g@mail.gmail.com>
--- On Tue, 21/2/12, Attila Fazekas <turul64@gmail.com> wrote:
> I think it is worth the effort.
>
> Hostapd AFAIK is not working with rtl8187 now.
> Until we can make it work in master mode, the adhoc mode
> could be an
> alternative. I think even if we can use it in master mode,
> ad-hoc mode
> should be implemented.
You (and others) could comment on the issue of not-working hostapd a bit more; we might want to get it working properly anyway.
As Larry requested - please send the patch without munching from your
e-mail client. Since you are on gmail, I could offer a little advice on git-send-email, which may or may not be something you already know. This is what I do to send patches from my gmail account (change "name" and "acct" and "FILLTHISIN" and "patch-file" to suit yourself), and you could add --cc a few of us there also:
git send-email --from 'name <acct@gmail.com>' \
--to linux-wireless@vger.kernel.org --to linville@tuxdriver.com \
--smtp-server smtp.gmail.com --smtp-server-port 465 --smtp-user \ acct@gmail.com --smtp-pass FILLTHISIN --smtp-ssl patch-file
You can do "man git-send-email" (all git man pages uses "git-something" to document the "git something" sub commands, with a dash between) to read about all the switches and what they are supposed to do.
> About refactoring:
>
> rtl8180_beacon_work()
> Now is almost the same, I think it is possible to make it
> generic by a
> macro, or by creating new source/object file linked to both
> driver, or
> even possible to create a common module.
> But, this function will be different if someone will be able
> to add
> some hardware aided beacon timestamp update. (If I can have
> more
> information about this hardware I'll try it)
> Creating a new common module just for one small function,
> IMHO not
> worth the effort.
> Please advice.
>
> struct rtl8187_vif, struct rtl8180_vif now are the
> same, they might
> be the same in the future as well.
> We can remove them and create new one named rtl818x_vif in
> the rtl818x.h .
> Shall I do it ?
I haven't got a strong opinion on this - but we probably like to try your patch out first :-).
Thanks for the work!
Hin-Tak
next prev parent reply other threads:[~2012-02-22 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 19:54 [PATCH] rtl8187: Add Ad-hoc mode Attila Fazekas
2012-02-19 21:19 ` Larry Finger
2012-02-19 23:17 ` Hin-Tak Leung
2012-02-21 17:44 ` Attila Fazekas
2012-02-22 21:51 ` Hin-Tak Leung [this message]
2012-02-22 23:35 ` Larry Finger
2012-02-23 0:44 ` Hin-Tak Leung
2012-02-23 0:59 ` Julian Calaby
2012-02-23 2:17 ` Larry Finger
2012-02-23 2:27 ` Hin-Tak Leung
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=1329947497.90659.YahooMailClassic@web29504.mail.ird.yahoo.com \
--to=htl10@users.sourceforge.net \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=turul64@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