Subject: Re: Acx driver news and current status - msg#00026

Previous Message by Date:

Re: Acx driver news and current status

Hi Duane, thanks for your e-mail. 2008/7/31 Duane Griffin <duaneg@xxxxxxxxx>: > [...] I've got one of these suckers languishing in a > drawer and would love to help. I recently bought a PCMCIA-to-PCI > bridge card for my desktop for just this purpose. However, I'm > avoiding the code until/unless the legal status is clarified. > If you want to avoid the code and you are willing to contribute, you could help by testing, for example. Regards, David. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Next Message by Date:

Re: Acx driver news and current status

Hi Helmut, 2008/7/31 Helmut Schaa <hschaa@xxxxxxx>: [...] > > David, maybe the patches should be added to the master branch too > (encapsulated by ifdefs)? Which patches are you refering to exactly? If you mean a kind of merge from wireless-new to master + #ifdefs, I would not do something like that just yet. We have enough #ifdefs in master simply to support 3 different kernels, and I would not like to add more for a tree (wireless-testing) which changes at a much more quicker pace than the upstream kernel tree. In any case, if you'd like to discuss this further, please feel free to start a new thread, as I'd like to keep the current topic to a more general discussion about the state and future of the driver. Thanks. Regards, David. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Previous Message by Thread:

Re: Acx driver news and current status

Hi, Am Mittwoch, 30. Juli 2008 23:37:04 schrieb David Planella: <snip> > * The acx111 chipset has been reported to work with WPA, WPA2 and WEP > encryption. The acx100 support is currently broken. You can start the > interface on acx100, but nout much more. What about the USB part? Does it work? I only have two acx111 pcmcia cards here for testing. Thanks, Helmut ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/

Next Message by Thread:

Re: Acx driver news and current status

Hi David, thanks for the update. On Wed, Jul 30, 2008 at 11:37 PM, David Planella <david.planella@xxxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > I have recently joined the project administrator's group and would > simply like to comment on the current status and future direction of > the acx driver. > > I'll start by stating that we have the same problems as ever, which > are basically the lack of resources and the fact that the driver has > not yet been included in mainline kernel. My initial intention is > simply to get the project back to its feet: by first working on its > infrastructure so it is in a state in which it is easy for prospective > developers, users and testers to contribute -and to ultimately get a > functional driver. > > These are not going to be ground-breaking changes, as I cannot offer > full-time dedication to the project, but they are small things which I > hope will make some difference. These are the main initial points: > > * Make the codebase easy to access, to contribute to (developers) and > to fetch (testers, users) > ** Create a central public repository. Status: done (see [1] and the > information below) > ** Identify current issues as tasks for prospective contributors (or > for the current devs). Status: done [2] > ** Create an article on the wiki on how to use the acx repository. Status: > TODO > ** Leave all repository branches in a usable state for the most used > current kernels (2.6.24, 2.6.25, 2.6.26), so we can concentrate on bug > fixing rather than fixing build failures. Status: done (thanks to > Xazz!) Thanks a lot for this, unfortunately I have to report that 2.6.27-rc1 breaks the build yet again. This time at least ieee80211_tx_control was dropped and got replaced by ieee80211_tx_info and beacon/beacon_control fields were removed from ieee80211_if_conf. > ** Update the INSTALL and README files. Status: INSTALL done, README TODO > > * Keep information on the wiki up-to-date > ** Add a development section. Status: started > ** Add a debugging section. Status: TODO > > * Use the current Sourceforge resources > ** Bug tracker cleanup. Status: started > ** Keep the news up to date. Status: TODO > > * Try to break the current isolation with regards to the other > wireless kernel drivers > ** Send an e-mail to the linux-wireless mailing list describing the > current status of the drivers. Someone might even be able to help us > with review and the locking issues. Status: TODO > ** Try to clear up the legal status of the driver regarding its > initial reverse-engineering process. Contact the SFLC?. Note: the > driver was mentioned here [3] (section 2.1.2). > > New code repository. > - -------------------- > > The repository at > http://gitorious.org/projects/acx-mac80211/repos/mainline has now been > appointed as the "official" acx repo. There is a read-only mirror at > http://repo.or.cz/w/acx-mac80211.git, which is synced every hour. > Please note that the current status of the driver is rather unstable. > > The following branches are available: > > * master: > This is the main branch, which currently contains the mac80211 version > of the driver. This is what most users will want to use. > > * non-mac80211: > This is the branch from which all other ones come from. It corresponds > to the original driver with its own wifi stack. > At some point it diverged from master and the mac80211 was merged to > the master branch. This branch should be considered in > maintenance/legacy mode and no new development should happen here. > Note that I might rename this to "legacy" at some point. You should > not probably use this branch unless you explicitly want to use the > plain driver (i.e. non-mac80211). > > * mac80211: > Originated from the initial d80211 and mac80211 patches to the > original (non-mac80211) driver, and contains the version of the driver > with support for the mac80211wifi stack. It is a temporary branch, > which was eventually merged to master and will be deleted at some > point. Do not use it. > > * wireless-new: > This branch build against the wireless-testing kernel tree from John > Linville and against the compat-wireless patch for older kernels. This > is what users with kernels which feature those codebases will want to > use (i.e. openwrt, and maybe Fedora?). > > Here's [4] the original repo announcement. I will also release a news > article at some point. > > Current status. > - --------------- > > * As mentioned several times, the driver is unstable, so don't hold > your breath yet. On multicore machines with SMP kernels it will often > lock, whereas on uniprocessor machines it will run for long periods of > times and only occasional locks might occur when e.g. unloading it. > This is currently the main problem with the driver. > > * The acx111 chipset has been reported to work with WPA, WPA2 and WEP > encryption. The acx100 support is currently broken. You can start the > interface on acx100, but nout much more. > > * There are currently only two developers: myself, which cannot > dedicate much time to it anyway, and Xazz, who was the one which > picked up the mac80211 port and started maintaining it. He has been > doing by far the most development work in the last few months. Some of > the project admins are currently inactive, which applies for most (or > all) of the original developers. > > I believe that is all for now. Needless to say, any comments/ideas or > help in implementing any of these points (or others) will be very much > welcome. > > Regards, > David. > > [1] http://acx100.sourceforge.net/wiki/Main_Page#Development > [2] http://acx100.sourceforge.net/wiki/DevelopmentTasks > [3] http://ols.fedoraproject.org/OLS/Reprints-2008/linville-reprint.pdf > [4] > http://sourceforge.net/mailarchive/forum.php?thread_name=1d9d9b240806161003j21fbfbd1se21c9b5f1cc14c1e%40mail.gmail.com&forum_name=acx100-devel > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFIkN7a+hJnr3MCmLgRAjtYAKCksYChsLY5YvbNO4kIcR5GOa7wYQCcDpb2 > M0J1RlRbj5NVC3jnAJ75/Ng= > =xbqS > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Acx100-devel mailing list > Acx100-devel@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/acx100-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/