Re: the permissions, I reviewed the usbfs interface again and I think it
should be possible to get the device info in read-only mode, i.e. so write
access isn't needed.  If I get the JNI updated I will let you know.


On Sun, Sep 27, 2009 at 9:46 AM, Andre Juffer <ajuf...@sun3.oulu.fi> wrote:

> Hi Dan,
>
> thanks for the reply. I changed the permissions to ensure rw access to
> the nodes. That is, I have not changed w permissions for /dev or
> /dev/bus as this may result in all kinds of undesirable side effects,
> but but only for usb in /dev/bus:
>
> cd /dev/bus
> chmod -R a+w usb
>
> This affected the outcome of FindUsbDevice without any argument:
>
> Found 4 devices total.
> Found 1 devices with vendor ID 0xffff product ID 0xffff
> Found 3 devices with device class 0x09
> Found 0 devices with manufacturer string "This probably won't match
> anything"
>
> The machine has actually 4 USB ports, so the outcome seems compatible
> with this.
>
> I have attached to one of the USB port a memory stick. The command
> 'lsusb -t' is
>
> Bus#  2
> `-Dev#   1 Vendor 0x1d6b Product 0x0002
>    `-Dev#   2 Vendor 0x0781 Product 0x7113
> Bus#  1
> `-Dev#   1 Vendor 0x1d6b Product 0x0001
>
> The memory stick is identified on the third line (Vendor 0x0781 Product
> 0x7113). This is easy to verify with 'lsusb -v'. Running FindUsbDevice
> with idVendor=0x0781 idProduct=0x7113 gives me the following:
>
> Found 4 devices total.
> Found 1 devices with vendor ID 0x0781 product ID 0x7113
> Found 3 devices with device class 0x09
> Found 0 devices with manufacturer string "This probably won't match
> anything"
>
> Running with FindUsbDevice with manufacturer="SanDisk Corp.", I get:
>
> Found 4 devices total.
> Found 1 devices with vendor ID 0xffff product ID 0xffff
> Found 3 devices with device class 0x09
> Found 1 devices with manufacturer string "SanDisk Corp."
>
> So, I conclude that everything seems to work fine also on an AMD64 box.
>
> I am now in the process on trying javax-usb on Windows. I will report on
> this shortly.
>
> Thanks,
> Andre
>
>
> Dan Streetman wrote:
> > The library requires read-write access to the USB nodes, so try either
> > running the program as root or change the permissions on the
> > /dev/bus/usb/NNN/NNN nodes.
> >
> >
> > On Wed, Sep 23, 2009 at 5:31 PM, Andre Juffer <ajuf...@sun3.oulu.fi
> > <mailto:ajuf...@sun3.oulu.fi>> wrote:
> >
> >     Hello,
> >
> >     I was wondering whether the JavaxUsb library would properly work on
> an
> >     AMD64 Linux box (running Lenny Debian). I have successfully compiled
> and
> >     installed the library, compiled all java sources from scratch (with
> Java
> >      1.6) and everything seems to work.
> >
> >     On the Linux box, 'lsusb -t' gives the following:
> >
> >     Bus#  2
> >     `-Dev#   1 Vendor 0x1d6b Product 0x0002
> >     Bus#  1
> >     `-Dev#   1 Vendor 0x1d6b Product 0x0001
> >
> >
> >     If I run FindUsbDevice (one of the test classes) with for instance
> >     idVendor=0x1d6b, I get:
> >
> >     Found 1 devices total.
> >     Found 0 devices with vendor ID 0x1d6b product ID 0xffff
> >     Found 1 devices with device class 0x09
> >     Found 0 devices with manufacturer string "This probably won't match
> >     anything"
> >
> >     So, it apparently sees a device (I should note that nothing is
> connected
> >     to the USB ports).
> >
> >     Running FindUsbDevice without any arguments, I get:
> >
> >     Found 1 devices total.
> >     Found 1 devices with vendor ID 0xffff product ID 0xffff
> >     Found 1 devices with device class 0x09
> >     Found 0 devices with manufacturer string "This probably won't match
> >     anything"
> >
> >     The difference really is the second line of the output with and
> without
> >     an argument. It apparently sees an device with vendorID 0xffff
> although
> >     there is one with ID 0x1d6b.
> >
> >     The AMD64 Linux box also has a libusb-0.1.so.4 library. One possibly
> >     should use this library instead of libJavaxUsb.so. This library is
> also
> >     available for Window (see also http://www.libusb.org/). But its API
> may
> >     be completely different.
> >
> >     My intention is get this all going also on a Windows box, but for now
> I
> >     rely on Linux to get a basic understanding of USB communication.
> >
> >     Any suggestion or help is appreciated.
> >
> >     Thanks,
> >
> >     --
> >     Andre H. Juffer              | Phone: +358-8-553 1161
> >     Biocenter Oulu and           | Fax: +358-8-553-1141
> >     Department of Biochemistry   | Email: andre.juf...@oulu.fi
> >     <mailto:andre.juf...@oulu.fi>
> >     University of Oulu, Finland  | WWW:
> >     www.biochem.oulu.fi/Biocomputing/
> >     <http://www.biochem.oulu.fi/Biocomputing/>
> >     StruBioCat                   | WWW: www.strubiocat.oulu.fi
> >     <http://www.strubiocat.oulu.fi>
> >     NordProt                     | WWW: www.nordprot.org
> >     <http://www.nordprot.org>
> >     Triacle Biocomputing         | WWW: www.triacle-bc.com
> >     <http://www.triacle-bc.com>
> >
> >
> ------------------------------------------------------------------------------
> >     Come build with us! The BlackBerry&reg; Developer Conference in SF,
> CA
> >     is the only developer event you need to attend this year. Jumpstart
> your
> >     developing skills, take BlackBerry mobile applications to market and
> >     stay
> >     ahead of the curve. Join us from November 9&#45;12, 2009. Register
> >     now&#33;
> >     http://p.sf.net/sfu/devconf
> >     _______________________________________________
> >     javax-usb-devel mailing list
> >     javax-usb-devel@lists.sourceforge.net
> >     <mailto:javax-usb-devel@lists.sourceforge.net>
> >     https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> > Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> > is the only developer event you need to attend this year. Jumpstart your
> > developing skills, take BlackBerry mobile applications to market and stay
> > ahead of the curve. Join us from November 9&#45;12, 2009. Register
> now&#33;
> > http://p.sf.net/sfu/devconf
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > javax-usb-devel mailing list
> > javax-usb-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
>
> --
> Andre H. Juffer              | Phone: +358-8-553 1161
> Biocenter Oulu and           | Fax: +358-8-553-1141
> Department of Biochemistry   | Email: andre.juf...@oulu.fi
> University of Oulu, Finland  | WWW: www.biochem.oulu.fi/Biocomputing/
> StruBioCat                   | WWW: www.strubiocat.oulu.fi
> NordProt                     | WWW: www.nordprot.org
> Triacle Biocomputing         | WWW: www.triacle-bc.com
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> javax-usb-devel mailing list
> javax-usb-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
javax-usb-devel mailing list
javax-usb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel

Reply via email to