> From: Michael Dickens
>
> logging. Until then, the best I can reasonably do is modify LIBUSB
> to do debugging printouts ... but I think I'll just ask my advisor to
Inserting a call to usb_set_debug(99) will probably give you enough
debugging chatter to send you into the woods screaming.
> From: Steve Sisak
>
> Having developed Mac USB drivers since the original iMac shipped, I
> recently had occasion to port some code that used libusb, looked at
> it, and ran away in horror. ;-)
I won't disagree with your conclusion; libusb gets several abstractions
"wrong" in my book. Different projects will have different tradeoffs of
platform-specific code vs. abstractions available on multiple OSes. So
libusb does have a place in the world.
I do have a project[1] with a non-trivial user base that uses libusb
successfully on a number of platforms. I have users with confirmed
success with Rosetta on the various Intel Macs (I was honestly suprised
that worked when I first heard it...) including the various MBP models.
That said, I fully realize that success with MY code and hardware that
likely has nothing whatsoever in common with the hardware and code paths
that interests you really doesn't mean very much.
Though intellecually it's appealing, I haven't been terribly motivated
to replace it directly with calls to IOKit becuase it's not really
_that_ broken for my use. The risk/payoff just isn't there for me. (If
I had access to a variety of OS/X hardware and OS combinations, I'd
probably feel differently.)
RJL
[1] http://www.gpsbabel.org uses libusb to communicate with a variety of
Garmin GPSes over USB.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
This email sent to email@hidden
