From: Daniel Drake <dsd@gentoo.org>
To: Daniel Drake <dsd@gentoo.org>,
Michael Wu <flamingice@sourmilk.net>,
netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>,
Luis Rodriguez <mcgrof@gmail.com>
Subject: Re: zd1211 ported to Devicescape stack
Date: Sat, 02 Dec 2006 13:55:08 -0500 [thread overview]
Message-ID: <4571CC0C.2070309@gentoo.org> (raw)
In-Reply-To: <20061202175737.GA5577@p15091797.pureserver.info>
Ulrich Kunitz wrote:
> I intend to track the d80211 stack, care for the forward porting
> and see also a number of things, which should be done for d80211.
OK, sorry for the false assumptions in my last mail.
In that case, I guess we should both switch to developing zd1211rw on
d80211 primarily. I am still interested in seeing stuff in mainline so I
will spend time backporting some of the new developments (but nothing
major).
We should also use this opportunity to switch to developing in kernel
git trees (as opposed to external kernel module git trees) for the
d80211 port.
To start with, I would ask you to pull my git tree then John (or
Michael?) would pull from you. We should start this at the point when
Michael's port enters wireless-dev.git
What do you think?
> Daniel your hardware crypto patches should certainly be included
> here.
The patch only enables hardware decryption and doesn't work completely.
Needs more work.
Daniel
next prev parent reply other threads:[~2006-12-02 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 8:16 zd1211 ported to Devicescape stack Michael Wu
2006-12-02 13:25 ` Ulrich Kunitz
2006-12-02 14:54 ` Michael Wu
2006-12-02 15:58 ` Daniel Drake
2006-12-02 17:57 ` Ulrich Kunitz
2006-12-02 18:32 ` Michael Wu
2006-12-02 18:55 ` Daniel Drake [this message]
2006-12-02 19:53 ` Ulrich Kunitz
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=4571CC0C.2070309@gentoo.org \
--to=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=netdev@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 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).