From: linux-wireless-5/S+JYg5SzeELgA04lAiVw@public.gmane.org
To: David Planella <david.planella-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: acx100-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: The future of the TI ACX wireless driver
Date: Sun, 10 Jun 2007 19:06:28 +0200 [thread overview]
Message-ID: <466C2F94.8050501@hauke-m.de> (raw)
In-Reply-To: <1d9d9b240706100735k374b5800ie64370e1e9bff1ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
Nice work David.
I have extracted the acxsm driver out of the wireless-2.6 git tree and
made it compile on at least kernel 2.6.20 and 2.6.22-rc4
It can be found here:
http://www.hauke-m.de/fileadmin/acx/tiacx-20070522.tar.bz2
I also chanced some lines in the normal acx driver so it compiles with
kenrel 2.6.22 and later
http://www.hauke-m.de/fileadmin/acx/acx-20070610.tar.bz2
Bouth are loading on my system, but I can't test them because I haven't
got any acx100 chip based card any more, it would be nice to get
positive feedback, when it's working.
I will write some pages into the Wiki for these versions, so everyone
can test them.
I am not a big kernel hacker but I want to learn it too.
Hauke Mehrtens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGbC+UrcX0gpXFjnsRAiZvAJ9HqeLhYD71ziIY8nn1/s165IgW9wCeOkta
jcvdcupbincXF0WpXVQse5s=
=1Dty
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-06-10 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 14:35 The future of the TI ACX wireless driver David Planella
[not found] ` <1d9d9b240706100735k374b5800ie64370e1e9bff1ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-10 15:21 ` Jeff Williams
2007-06-10 17:06 ` linux-wireless-5/S+JYg5SzeELgA04lAiVw [this message]
2007-06-10 17:27 ` David Planella
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=466C2F94.8050501@hauke-m.de \
--to=linux-wireless-5/s+jyg5szeelga04laivw@public.gmane.org \
--cc=acx100-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=david.planella-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).