понеділок 14 січень 2008, Kirk Davis, Ви написали:
= I have ported the uberry driver from OpenBSD over to FreeBSD. I have
= done a lot of changed and support for the new devices and am just
= working on some final changed before submitting it. I abandoned the
= linux uberry driver as I didn't
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mikhail Teterin
I'm trying to port a suit called barry, which provides a library and
some = utilities to work with RIM's BlackBerry devices.
I have ported the uberry driver from OpenBSD over to
Duane H Hesser wrote:
The only work-around is to not have umass, etcetera in your kernel,
but that sucks, because one may want to be able to access /some/
devices as mass-storage, and some others as merely generics...
A similar problem occurs to many of us who have HP printers which
hook
On п'ятниця 11 січень 2008, Hans Petter Selasky wrote:
= I think you misunderstand. If there is a mass storage device it will appear
= like /dev/da0. If there is a libusb device it will have t
= use /dev/usbX.Y.Z.
I understand, that you have no intention of /replacing/ daX with /dev/usbX.Y.Z
My
On п'ятниця 11 січень 2008, Hans Petter Selasky wrote:
= /dev/usbbus_no.dev_no.iface_no.ep_no
[...]
= What do you think ?
I still prefer the elegance of /dev/umassX and /dev/ugenY to the
nameless /dev/usbX.Y.Z
For example, all SCSI devices have names (da, st, cd, pt, etc.), even though
they
On Friday 11 January 2008, Mikhail Teterin wrote:
On п'ятниця 11 січень 2008, Hans Petter Selasky wrote:
= /dev/usbbus_no.dev_no.iface_no.ep_no
[...]
= What do you think ?
I still prefer the elegance of /dev/umassX and /dev/ugenY to the
nameless /dev/usbX.Y.Z
For example, all SCSI devices
On Thursday 10 January 2008, Duane H Hesser wrote:
On Wed, 9 Jan 2008 10:15:16 -0500
Does anyonw (Hans?) know whether the ugen driver can be altered to
attach to a single interface, just like any other driver, leaving
other interface setups alone?
ugen takes the whole device ... It will
= I'm trying to port a suit called barry, which provides a library and some
= utilities to work with RIM's BlackBerry devices.
= It compiles cleanly, but fails to find a connected device at run time. In
= fact, it fails to find _any_ devices, even though ``usbdevs -v'' lists
= several including
On Wednesday 09 January 2008, Mikhail Teterin wrote:
= I'm trying to port a suit called barry, which provides a library and
some = utilities to work with RIM's BlackBerry devices.
= It compiles cleanly, but fails to find a connected device at run time. In
= fact, it fails to find _any_
середа 09 січень 2008 01:34 по, Hans Petter Selasky Ви написали:
My plan is to extend /dev/usbX so that it becomes a so-called clonable
device. When you open up /dev/usb0.2.3 for example, you open up the
device having index 2 on USB bus 0 and endpoint 3. This will need some
modifications in
On Jan 10, 2008 2:34 AM, Hans Petter Selasky [EMAIL PROTECTED] wrote:
On Wednesday 09 January 2008, Mikhail Teterin wrote:
We really need the low-level (ugen?) interfaces available for all
USB-devices -- even those, which are /also/ handled by higher-level
interfaces (like ulpt, uscan,
11 matches
Mail list logo
