Rev= 1.02
S: Manufacturer=Ensure Technologies, Inc.
S: Product=Ensure Technologies XyLoc Lock model #U-1
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 60mA
I:* If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
Ron Gage
-
This
Ron Gage wrote:
> Alan Stern wrote:
>
>> Umm. I'm not familiar with USB programming under Windows, so I can't
>> say what (if anything) the "Function: 0019" means. It's probably
>> something specific to the Windows USB API
Alan Stern wrote:
> On Sun, 22 Jul 2007, Ron Gage wrote:
>
>
>> OK, I'll be the first to admit that doing USB work is a new area for me
>> and I might have some terminology conflated. That said, I can only go
>> by what is in front of my eyes.
>>
>>
Hi Alan:
Alan Stern wrote:
> On Sat, 21 Jul 2007, Ron Gage wrote:
>
>
>> Greetings:
>>
>> I am in the process of (trying to) write a device driver for a Xyloc USB
>> Lock and am having a bit of a problem. You see, the device makes
>> extensiv
code to a device. I have a snoopypro dump of the communications with
the device if anyone is interested in that.
Thanks!
Ron Gage
Westland, Michigan
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping throu
Greg KH wrote:
>> Uggg - no joy
>>
>> [EMAIL PROTECTED]:/etc/udev# udevinfo --query=all --name=/dev/sda
>> P: /block/sda
>> N: sda
>>
>
> What does:
> tree /sys/block/sda/
>
> show?
>
>
[EMAIL PROTECTED]:~# tree /sys/block/sda
/sys/block/sda
|-- dev
|-- device ->
../../devices/pc
Greg KH wrote:
> On Mon, Jan 01, 2007 at 08:00:05PM -0500, Ron Gage wrote:
>
>> Steve Bangert wrote:
>>
>>> Check out the udev page at:
>>>
>>> http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
>>>
>>> Steve
>&
Greg KH wrote:
> On Mon, Jan 01, 2007 at 08:00:05PM -0500, Ron Gage wrote:
>
>> Steve Bangert wrote:
>>
>>> Check out the udev page at:
>>>
>>> http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
>>>
>>> Steve
>&
procfs and/or
sysfs). I really don't want to go down that road if at all possible.
Thanks!
Ron Gage
>
>
> On Mon, 2007-01-01 at 17:30 -0500, Ron Gage wrote:
>
>> Hi:
>>
>> I am trying to find a way (without resorting to patching the kernel) of
>
and
the associated system node name. I, of course, could be wrong.
Does anyone have any way to tie the data for a device to it's node
name. My end goal is to be able to list out the device manufacturer,
model and serial number for each device in /dev/sd[a-z].
Than
10 matches
Mail list logo
