From: David Gnedt <david.gnedt@davizone.at>
To: Kalle Valo <kvalo@adurom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Grazvydas Ignotas <notasas@gmail.com>,
Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Subject: Re: [PATCH 00/18] wl1251: feature ports / monitor mode / packet injection
Date: Mon, 31 Jan 2011 23:57:54 +0100 [thread overview]
Message-ID: <4D473E72.3050307@davizone.at> (raw)
In-Reply-To: <87r5btdsb8.fsf@purkki.adurom.net>
Am 2011-01-31 16:08, schrieb Kalle Valo:
> How did you test the patches? For example, what hardware did you use
> etc.
I tested the patches with compat-wireless and a modified fremantle 2.6.28 kernel
on my Nokia N900.
> About the code from fremantle kernels. Few weeks ago nokia sent me
> privately the original patches from their internal git tree, I gave
> some comments and never heard back. So, in theory I should have all
> the fremantle patches somewhere in my email archives. I would just
> need to clean them up and send them here. I'll go over your patches
> and let's see what we should do.
It would be interesting if I missed some features. I diffed the drivers, but I
am not 100% sure if I overlooked something useful.
One thing I haven't included in this patchset is the netlink interface from the
fremantle code for NVS loading because I thought it wouldn't be accepted anyway.
next prev parent reply other threads:[~2011-01-31 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D45A583.3060605@davizone.at>
2011-01-30 19:10 ` [PATCH 00/18] wl1251: feature ports / monitor mode / packet injection David Gnedt
2011-01-31 15:08 ` Kalle Valo
2011-01-31 22:57 ` David Gnedt [this message]
2011-02-01 6:39 ` Kalle Valo
2011-02-02 11:01 ` Grazvydas Ignotas
2011-02-02 22:41 ` Grazvydas Ignotas
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=4D473E72.3050307@davizone.at \
--to=david.gnedt@davizone.at \
--cc=GNUtoo@no-log.org \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=notasas@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).