From: Jeff Garzik <jgarzik@pobox.com>
To: Mateusz Berezecki <mateuszb@gmail.com>
Cc: kernel-mentors@selenic.com, netdev <netdev@vger.kernel.org>
Subject: Re: atheros driver - desc
Date: Fri, 05 Aug 2005 13:46:30 -0400 [thread overview]
Message-ID: <42F3A5F6.6030209@pobox.com> (raw)
In-Reply-To: <42F2D523.9020702@gmail.com>
Mateusz Berezecki wrote:
> Hi list members,
>
> I just post the code for review for anyone interested.
> I would be more than pleased to hear some feedback from you on the code.
>
> Im sending a series of 8 patches splitted and diffed as in
> SubmittingPatches documentation.
>
> The driver is not yet fully working because I didn't finish kernel
> integration yet. Almost all
> driver I/O ops are reverse engineered independently of openbsd openhal
> which is missing just too much.
>
>
> Ok, enough talking. Most of the atheros 5212 hal is now open :)
>
> sending patches...
It's a good start. When you get a basic working driver, I'll push it
into ieee80211 branch, and further review and work can occur.
Jeff
next prev parent reply other threads:[~2005-08-05 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 2:55 atheros driver - desc Mateusz Berezecki
2005-08-05 10:14 ` Michael Renzmann
2005-08-05 16:46 ` Bryan O'Sullivan
2005-08-05 17:46 ` Jeff Garzik [this message]
2005-08-06 19:57 ` Kalle Valo
2005-08-06 20:53 ` Jeff Garzik
2005-08-06 21:45 ` Harald Welte
2005-08-07 7:32 ` Kalle Valo
2005-08-07 15:01 ` Harald Welte
2005-08-12 7:37 ` Chris Wedgwood
2005-08-12 11:45 ` Harald Welte
2005-08-25 16:36 ` [OT] legal status of re-engineering (was Re: atheros driver - desc) Harald Welte
2005-08-06 21:38 ` atheros driver - desc Mateusz Berezecki
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 18:07 Mateusz Berezecki
2005-08-05 18:39 ` Jeff Garzik
2005-08-05 18:54 ` Mateusz Berezecki
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=42F3A5F6.6030209@pobox.com \
--to=jgarzik@pobox.com \
--cc=kernel-mentors@selenic.com \
--cc=mateuszb@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).