Hi all.

As most of you know, testing of the upcoming new code from Atheros is
currently work in progress. This new code, lets call it madwifi-ng for
now, will be the new base for Madwifi in the future - I already talked
about that before.

Due to the amount of requests from different users, and following to a
discussion in madwifi-devel, we decided to start the public testing
phase of madwifi-ng. This means basically that anyone will be able to
access the code of madwifi-ng for testing purposes.

Before you start your euphoric dances now:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
IMPORTANT: Please read the complete mail, and make sure you follow the
guidelines that it contains.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Requirements
============
First off: madwifi-ng is highly experimental. It's not ready for
prime-time yet, lacks a lot of functionality and might behave unexpected.

Don't use it if you are not willing to deal with the problems it might
cause! Stick with the current Madwifi code in that case.

You should be knowledged with the use of the current Madwifi versions,
and you should have experience in solving minor to medium problems (for
example compilation issues) yourself. This does not mean that you
necessarily need to know about the inner structures of the driver, but
you should have programming experiences (C).

You will need a subversion client to access the repository. There is no
tarball generated for madwifi-ng, nor is it feasible to access the
repository via Web. And neither a tarball nor a sophisticated web
interface will be available - don't even think about asking that. ;)

You are expected to read the documentation that comes along with
madwifi-ng. Trivial support questions will be silently ignored. In
addition, check the list archives of the dedicated mailing list (see
below) before asking your questions.

You are expected to make use of the dedicated madwifi-test mailing list
(see below) for everything that is related to madwifi-ng. Don't post
questions, reports or patches to any of the "usual" mailing lists
(madwifi-devel, madwifi-users), in order to avoid confusion.

Still reading? Cool :)

Accessing the madwifi-ng code
=============================
We have set up a Subversion repository that contains the source of
madwifi-ng. The address of the repository is:

http://svn.madwifi.org/madwifi-ng

In order to check out a working copy into a local subdirectory called
"madwifi-ng", you would use:

svn checkout http://svn.madwifi.org/madwifi-ng/trunk madwifi-ng

You get the idea.

Joining the madwifi-test mailing list
=====================================
In order to avoid confusion of people who don't care to test the new
code, we created a dedicated mailing list called "madwifi-test". This is
the place for all your questions, reports, patches and other stuff
related to madwifi-ng.

Again: please avoid posting stuff related to madwifi-ng to any of the
"normal" mailing lists!

To subscribe to madwifi-test please visit:
http://lists.otaku42.de/mailman/listinfo/madwifi-test

You will be requested to confirm your subscription. Please note that
confirmation via e-mail doesn't work currently. Instead please confirm
by visiting the link mentioned in that e-mail. Sorry for the
inconvenience, I'll try to fix that asap.

Next step would be to check the mailing list archives to see what
happened so far. Up to now you didn't miss too much, but it won't hurt
anyway :)

Known issues
============
madwifi-ng suffers from some problems, some of them already have been
reported by other testers. I'm going to sum them up and send them to
madwifi-test tomorrow.

Information about repository updates
====================================
Every change to the madwifi-ng repository will be announced in madwifi-test.

What to do now?
===============
Be sure to read the users guide, as well as the README_FIRST file in
your working copy. madwifi-ng is a little different and you will run
into troubles without learning about these differences.

Now go ahead, test as much as possible, and report back about your
experiences. Any report is welcome, no matter if it is about things that
worked or about things that didn't. If you find bugs, try to describe
them as extensively as possible. Even better if you can provide patches
to fix problems that you came across.

Questions?
==========
Go ahead, ask them. But please remember to make use of madwifi-test
where possible if your questions are directly related to madwifi-ng.

Bye, Mike
-- 
Sign EDRI petition against data retention:
http://www.dataretentionisnosolution.com
Use PGP/GPG!
My key: http://keys.indymedia.org/cgi-bin/lookup?op=get&search=62C29B94
Fingerprint: BC2E 79BF 0C8F 0282 864B 9CEC 8343 5169 62C2 9B94

-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl