Quoting abuas_z <rocky7-5tc4TXWwyLM@xxxxxxxxxxxxxxxx>:
> Hello,
>
> Is this project developped? From this as I can see in CVS orinoco
> drivers project is no longer developped from about half year.. Is
> there is any orinoco developper who can answer this question?
I can answer. The developers are busy with other things. Also, the first
priority is getting the existing code into the kernel. For this to happen, the
changes should be split into small logical pieces. David Gibson is doing this
work, and the driver is on its way into the mainline kernel (I believe it's in
the "-mm" branch now).
Another problem is that we tried to do something that is hard to maintain.
There are three branches in CVS, and synchronizing them is time consuming.
Something need to be done about it. I'm going to discuss it in a separate
post.
> There are many problems with CVS code:
> a) cvs and 0.15 drivers do not work correctly in monitor mode with
> 8.72 firmware;
I believe the problem is in the firmware. You mentioned in another post that
you have 7.xx firmware. You'll help us a lot if you do following:
- disable the firmware version check from the driver (see below if you don't
like changingthe code)
- use a card with 7.xx firmware
- test monitor mode with Airsnort and channel scanning for more than 20 minutes
- check if Airsnort is still getting packets
- check kernel log for error messages
- report the results, including the exact firmware version
If Airsnort with channel scanning works for you, the firmware check will be
relaxed.
Note to myself - we need a parameter to disable the firmware version check for
monitor mode. After all, not all users need channel scanning, and simple
monitoring works even with 8.xx firmware. The parameter will be in CVS
tomorrow.
> b) orinoco-usb drivers do not allow monitor mode with any version of
> firmware (system hang, no kismet support with orinoco-usb driver).
> What about it?
It's completely orphaned, unfortunately. Its author died in a car accident.
Somebody should take over the maintenance. Also, we need a better way to handle
locking. Conditional locking used in the HEAD branch is not a good idea.
There are other wireless USB drivers, and there is a lot to be learned from
them. Chris Rankin is working on cleaning up USB support in linux-wlan-ng.
zd1201 driver appeared in the kernel recently. zd1211 is under development.
One possible solution would be to make orinoco_usb a separate driver. Later it
could possibly incorporate Prism USB and even zd1201 support. They all use
similar configuration mechanisms via so called RIDs with mostly the same
numbers and data format.
--
Regards,
Pavel Roskin
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
|
