--- Hiji hijinio@yahoo.com wrote:
--- Lars Segerlund lars.segerlund@comsys.se
wrote:
What is the status of wines USB support ? Is there anything done yet or am I on my own
?
Can someone also giva a hint on the
feasibiliyt,
complexity of managing a USB implementation for wine ? I am rather good at
linux
device drivers and such. / regards, Lars Segerlund.
There's not much I can say in the way of development, but as a user, getting USB support (beyond
what's
supported in the kernel) would be a HUGE leap of improvement for Wine. I think others have said before that there are a lot of apps out there that will
run
on Wine, but are useless because they depend on their hardware counterpart. (In the music world, Guitarport comes to mind.)
Hiji
I have proposed several possible solutions for
using
USB under Linux. In fact, I have given 4 possible ways of doing it, one of which I have hacked up (and gotten to work, at least partially).
If you're interested in the details, let me know, and I'll email you (or look at the "Wine device
drivers
proposal" email in the Wine archives in the past month or so). Phew, I thought I'd type a short reply! Interested in working on this? I can't do it all alone. Damjan
There's not much I can do other then try to encourage you and Lars to work together (as I'm not a C developer). Damjan, it sounds like you have already covered a lot of the groundwork through your research and understanding of the USB infrastructure (from both the Windows, Linux and Wine worlds). Lars, I see you have both the motivation and experience with Linux device drivers to work on Wine USB.
To me, it sounds like a perfect match for you two to pair up and work on implementing additional USB functionality.
I suppose the last piece missing is to consult the expert on the wineserver (as far as USB is concerned) to see if any changes would truely need to be made there. Who would that be?
I think it might be Alexander, and I think the general suggestion was "avoid changes to the wineserver". Anyone else know?
Hiji
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
__________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide
I think it might be Alexander, and I think the general suggestion was "avoid changes to the wineserver". Anyone else know?
I'll point out to you once again that Wine is not the right place to implement drivers. Drivers that are loaded in the kernel in Windows also belong in the kernel in Linux, not in Wine.
Wine cannot present a driver interface to the rest of the system, nor to other programs.
If you want to get a scanner going, the best way would be to make it work with SANE or V4L, and then get SANE or V4L to work with Wine's still imaging interface. That is much better than getting it to only work in Wine, as other applications will be able to use it via SANE, etc.
Have a look at the work that Maarten Lankhorst is doing on Web cameras ... he's doing things the right way.
You can continue trying to modify CreateFile, ReadFile, WriteFile etc. to make it work, but you'll realize sooner or later that a handle is tied to a unix fd. This is by design. Alexandre has said time and time again that he considers Wine to be just like any other application on the system; it reads file through the 'nix FS, and through unix file descriptors.
If you still want to loader the Windows driver, go and have a look at ndis wrapper. http://ndiswrapper.sourceforge.net/
If you *still* insist that you're going to load drivers in Wine, then don't be suprised if your patches are quietly dropped, and your requests for help are quietly ignored.
Mike
-
Damjan Jovanovic -
Mike McCormack