Date: Fri, 11 May 2012 02:28:14 +0400 From: Antuan Avdioukhine <antuan@gmail.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: Accessing USB from linux libusb-0.1-aware application (under linuxulator in freebsd 8) Message-ID: <CAL=HKs3zdkQfaToB9f67v25%2Bn=ADSYuuXG_0DjBsNio-Mk9Pyg@mail.gmail.com> In-Reply-To: <201205101801.03043.hselasky@c2i.net> References: <CAL=HKs0c289-Etg%2BowzBmKkKCwEc9sdUhS6Yzi9u9dBtQDW8RQ@mail.gmail.com> <201205101801.03043.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 10, 2012 at 8:01 PM, Hans Petter Selasky <hselasky@c2i.net>wrote: > On Thursday 10 May 2012 17:14:50 Antuan Avdioukhine wrote: > > Greetings! > > > > Can anybody assist me with URLs/docs/whatever how to access USB device > from > > linux application running on freebsd 8.2? > > > > I'm trying to get worked scanner which have binary-only linux driver for > > SANE. > > > > The first trouble is that linux libusb searches for usb device entries in > > /dev/bus/usb/<bus-no>/<dev>, and so it cannot search freebsd's > > /deb/usb/n.m.k device list. > > > > So, ok, it can be patched. But, there is a question: if I'll make patch > to > > change such behavior (change usb_os_find_devices and usb_os_find_busses > in > > linux.c from linusb-0.1 sources) and rebuild libusb as it is for linux > > environment -- is it will be enough linuxulator? I mean, will linuxulator > > translate correctly usb related ioctl calls? > > > > On the other hand, maybe I am going wrong way at all? :) Maybe there is a > > simple solution? > > Hi, > > Search for libusb2debian. > Found it. Looks like they took freebsd sources and compile it on debian. I had such idea, but I was confused after reading how linuxulator works, especially how it converts linux ioctl() calls to freebsd ones. Anyway, I'll try it. Thanks again. -- Antuan Avdioukhine Tech.S.A. Llc St.Petersburg, Russia.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAL=HKs3zdkQfaToB9f67v25%2Bn=ADSYuuXG_0DjBsNio-Mk9Pyg>