Re: Atmel AT76C503 USB 802.11b device driver
On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote: Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. The messages are sumited twice by your mailclient - it's not the MTAs fault. See that there are several minutes between them and that they have different message-ids. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Sounds interesting. Is this just to configure a WLAN-Ethernet bridge, or can you transmit network data over USB? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed Oct 08, 05:27P +0200, Bernd Walter wrote: On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote: Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. The messages are sumited twice by your mailclient - it's not the MTAs fault. See that there are several minutes between them and that they have different message-ids. They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. Anyway, I finally got around to installing exim and everyone is happy. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Sounds interesting. Is this just to configure a WLAN-Ethernet bridge, or can you transmit network data over USB? It's treated like any other network device. Raw network data is sent and received over the USB transfer pipes and dealt with using mbufs in the normal way. The main difference is that you can only submit one packet at a time, so there is effectively no hardware queue/ring. The wireless part seems to be a cross between 'ath' devices and 'wi' devices. WEP is done in hardware, as is scanning. Scan results are processed in software. Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, 8 Oct 2003 16:49:34 +0100 Stuart Walsh [EMAIL PROTECTED] wrote: They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. mailq or mailq -Ac? Bye, Alexander. -- Secret hacker rule #11: hackers read manuals. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, 8 Oct 2003 16:49:34 +0100 Stuart Walsh [EMAIL PROTECTED] wrote: They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. mailq or mailq -Ac? I think we've established I was at fault, but thanks :) It really was just an off the cuff remark, I didn't intend to start an MTA war or a sendmail usage lecture. Can we restrict all further posts in this thread to feedback on my driver? :) Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Tue Oct 07, 02:36P +0100, Stuart Walsh wrote: Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
