Hin-Tak Leung <hintak_leung <at> yahoo.co.uk> writes:
> Well, if the vendor driver 2.22.00 works with 2.6.12, you can grab my patch
set (sorry it is 'pathset' in the
> web location - I made a mistake in May and haven't fixed it yet):
> which would take you up to 2.6.29. I haven't tried 2.6.30 as I already moved
to the vendor driver 3.0 by then.
> You need the other patch set
> to take you up to 2.6.29, and the last one (attached) to take you to 2.6.30..
It may also work for the 2.22
> driver but I haven't tried, but it will at least give you some ideas if you
like to make the vendor 2.22 driver
> work on 2.6.30.
> The 3.0 vendor driver is at:
> Hmm, the firmware upload problem seems to have come up from time to time...
> if either versions of the vendor drivers work (but the rw driver does not) I
like to know. You will need to set
> up the blacklist to stop udev from autoloading kernel modules, but presumably
you already know that.
Ok, finally managed with the help of a friend to compile the vender driver
220.127.116.11 with the mips 2.6.30 kernel i use here.
Here is a patch that was needed to get it finally compiled under 2.6.30.
Firmware Upload works !!! and interface comes up as ath0.
But: looks like the driver doesnt work or like my WPA-Supplicant 0.6.9
Here is a Bootlog and outputs that come: http://pastebin.com/m232e0dfa
iface ath0 inet dhcp
iface eth0 inet dhcp
This configuration works flawless with an other machine and a ath5k mini-pci
card or on the same machine with an rt73usb stick running wpa-supplicant 0.6.9
and the wext driver.
Any Idea ?
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/