Re: Re: Re: Re: problem with ATMEL RFMD503A driver
Joerg Albert <[email protected]>
| Newsgroups | gmane.linux.drivers.atmel-wlan |
|---|---|
| Message-ID | <[email protected]> |
Hi Arnaud, On Wed, 9 Jul 2003, Arnaud Fontaine wrote: > Excuse me for this later answer but i have no time this days. People who > lend me this card have modified the belkin usb adaptor to put an better > antenna than the original. But they didn't do that correctly so i modify > this wire between antenna and card and now i ping without any problem with > the two drivers. OK, didn't know you talked about the wire to the antenna. > Now, the two drivers lists all APs found during scan and i can ping after > i do ifconfig and configured properly the card. Before, i have following > that you say (opened the netdevice after the driver found the APs) > so the problem comes from wire between antenna and Atmel WLAN > adaptor. > > I would like to thanks you a lot for your help... I would also > to know what's the major difference between the atmel and the berlios > driver ? Why do you say that the berlios driver are better ? ;) The Berlios driver is a complete rewrite of the Sourceforge one with: - Intersil radio support (SF dropped it in December 2002) - problems with SMP kernels fixed - IMHO a better structure of the code -> easier to maintain - structured debug output -> easier to let users obtain debug information - it tries to be endian clean for ports to big-endian machines - no config script -> easier to compile - no own config tools, just full support for iwconfig -> all graphical tools based on iwconfig run I dealt with the Sourceforge driver in 2002 and felt the urgent need to rewrite it completely. Oliver eventually started this project. Regards, Jörg