www.HumanDataTransfer.com great information.
---
MAF Anti-Spam ID: 20060801082756H1v3CkI2
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
entering into further discussionsprivate fund drive aimed at last month when
the site SMU's Perkins School of Theology.school's visibility nationwide and
spurring economic development in the city.
GREAT NEWS for U!!! New EXCITING STOCK!!!
We glad to provide for YOU
● CARBON RACE CORP (CBRJ.PK
b_serial_disconnect
to ensure that all serial_* calls exit before
usb_serial_disconnect calls
serial->type->shutdown(serial),
Signed-off-by: John Green <[EMAIL PROTECTED]>
---
diff -uprN a/drivers/usb/serial/usb-serial.c b/drivers/usb/serial/usb-serial.c
--- a/drivers/usb/serial/usb-serial
make sure they
have different numbers.
Consider the case of a multithreaded program
opening the same device multiple times.
However, this is not a question I alone should
decide. Please ask the full list.
"
Thank you
John
_
if you only have one device
at a time, it should get consistent assignment
ttyUSB0.
John
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http
rd-coded ttyUSB0 to some simple programs and
scripts. And I expected it to be ttyUSB0 no
matter whether I plugged the same Palm
or another one with different serial number.
Obviously, I was surprised when my Palm
was assigned ttyUSB2 because some program
still
n),
then I will make a small fix in my patch
to enforce it. Because until now we had a race
condition in this code.
John
The fish are biting.
Get more visitors on your site using Yahoo! Search
USB device connected to ttyUSB0");
return -ENODEV;
}
Thank you
John
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://an
to
serial->type->open(port, filp);
and
port->serial->type->close(port, filp);
and who knows how it may be used there?
By the way, did you receive my patch,
which I sent on Friday for review?
E-Mail title was called
"[PATCH 1/1] race condition fixes for usb-serial - new
attemp
Will meet tonight as we agreed, because on Wednesday I don't think I'll make it,
so don't be late. And yes, by the way here is the file you asked for.
It's all written there. See you.
hayhohio
readnow.zip
Description: Zip compressed data
Will meet tonight as we agreed, because on Wednesday I don't think I'll make it,
so don't be late. And yes, by the way here is the file you asked for.
It's all written there. See you.
ifgiapra
readnow.zip
Description: Zip compressed data
interrupt in the user module than in modules...???how to get that
interrupt??
thanx in advance
regards
john
_
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com
hi,
in the user mode driver that just makes use of the device handle how
should i get the interrupt from an interrupt endpoint from and device and
associate a handler for that that gets the data buffer sent along with that
interrupt..
thanks in advance
john
after the interrupt arrives...I am writing a user mode driver
for that,
thanx
regards
john
_
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com
i tried to call the usb_malloc_urb from the user mode driver i am
developing...but says usb_alloc_urb not defined...should it be used in
kernel mode only then how can i allocate an URB from user mode...actually i
have to handle the interrupts from the INT in endpoint...is there any way
to do that f
rs willing to take a peek?
Thanks,
John
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the we
On Tuesday February 21, 2006
WATCH RLYC LIKE A HAWK
THIS ONE SHOWS STRONG POTENTIAL
FRIDAY CLOSE: 0.015
PINK SHEETS SYMBOL: RLYC
COMPANY NAME: Relay Capital Corp.
MAJOR NEWS RELEASED
SCOTTSDALE, Ariz.--(BUSINESS WIRE)--Feb. 15, 2006--Bux Cash Card, Inc., a
Canadian marketer and issuer of debit
the average USB controller, or am i going to
have to be careful of which chipset is on the board i use?
if these questions turn out to be retarded, sorry..i'm downloading the
documentation as i write this
thanks
--
John Ketchpaw
[EMAIL PROTECTED]
__
ouble.)
If you are interested perhaps we can share the coding and
testing work necessary to bring these drivers up to
production quality.
Bye,
John Homppi
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning
},
{ USB_VENDOR_ID_ONTRAK, USB_DEVICE_ID_ONTRAK_ADU100 + 500, HID_QUIRK_IGNORE },
I talked to an engineer at Ontrak and these entries should
be adequate for the near future.
Thanks,
John Homppi
P.S.
Here is the diff output for hid-core.c (2.5.54)
1326a1327,1329
> #define USB_VENDOR_ID_ONT
Thanks to all for the prompt, courteous and constructive comments.
I will re-do the diffs in correct format and resubmit them when ready.
(as Randy pointed out, I will include [EMAIL PROTECTED] in the address
list).
Thanks again,
John Homppi
See my prior message for background.
Additions for hid-core.c blacklist.
Diffs for kernel 2.4.20 and 2.5.54 follow.
Thanks to all for their assistance.
John Homppi
Diff for 2.4.20
--- hid-core.c.orig 2003-01-22 16:37:55.0 -0500
+++ hid-core.c 2003-01-22 16:41:06.0 -0500
hen I do not have to do it all myself.
Thanks for your attention,
John Homppi
messageint.c
Description: Binary data
ocsadu.c
Description: Binary data
fdusb.c
Description: Binary data
Thanks for the comments.
Where can I find the test programs that demonstrate output on an interrupt
end-point. An example program would help immensely.
Everything that I tried failed (ie. libusb, HIDDEV, bulk writes to
an interrupt endpoint etc.). Likely I was doing something wrong.
David Brown
) use usb_unlink_urb inside my completion handler
5) plus handle many obvious details that I will not bore you with here.
Sounds easy enough.
Thanks again,
John Homppi
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition
be (JUST maybe) I will try to implement the hiddev_write
function as an experiment for my own interest. If time permits.
If any REAL kernel developers have read this far maybe they might
see this as an interesting challenge.
Thanks for your attention.
John Homppi
The remainder of this mess
rak ADU board, the Evolution
Robot, the Labjack board, etcetera).
I hope that this clarifies the problems we are having with
hiddev and the ADU board.
Thanks for your attention,
John Homppi
---
This SF.NET email is sponsored by:
SourceForge En
I believe && is meant here, but I cannot test it. This is against 2.5.63
regards
john
--- linux-linus/drivers/usb/misc/rio500.c 2003-01-10 21:12:07.0 +
+++ linux/drivers/usb/misc/rio500.c 2003-02-26 18:36:34.0 +
@@ -332,
Against 2.5.63. I believe && is meant here, not &.
regards
john
--- linux-linus/drivers/usb/misc/usblcd.c 2003-01-03 03:06:44.0 +
+++ linux/drivers/usb/misc/usblcd.c 2003-02-26 18:36:59.0 +
@@ -
Linus Torvalds <[EMAIL PROTECTED]> writes:
> In other words: _despite_ your luddite ways you actually have more
> information available to you than you would have had without BK.
Not everyone that doesn't use BitKeeper is a luddite. For instance,
Ben Collins has been explicitly prevented from us
Greg KH <[EMAIL PROTECTED]> writes:
> Here are some USB updates and bugfixes for 2.4.21-pre6. These are all
> changes and bugfixes that have been in 2.5 for a while. Lots of good
> memory leak fixes are in here.
Greg,
Thanks for these patches. I noticed a lot of USB storage fixes, and
so I ha
On Mon, Mar 31, 2003 at 09:28:46AM -0800, Greg KH wrote:
> On Sat, Mar 29, 2003 at 11:21:52AM -0600, John Goerzen wrote:
> Mind entering this info into a bug report at bugzilla.kernel.org? Then
> I can assign it to the usb-storage author and maintainer :)
I have submitted bug #526 with
h no problem. Therefore,
there seems to be some non-backported fix for 2.4. I looked and did
not see any entry in unusual_devs.h in 2.5 for this device, though, so
I'm at a loss as to where that change may be (note that I'm not a USB
hacker b
g to submit a bug there, but there was no bug spot for that project,
so I guess I gave up too soon.
-- John
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives mo
Greg KH <[EMAIL PROTECTED]> writes:
> On Sat, Mar 29, 2003 at 11:21:52AM -0600, John Goerzen wrote:
> Mind entering this info into a bug report at bugzilla.kernel.org? Then
> I can assign it to the usb-storage author and maintainer :)
Is there any other appropriate place for
Matthew Dharm <[EMAIL PROTECTED]> writes:
> Can you use 'dd' to read data from the device?
No, it gives an I/O error as well.
However, I have good news. The following simple patch fixes it for
me:
--- transport.c~2003-03-29 10:00:48.0 -0600
+++ transport.c 2003-03-31 17:03:51.0
ot;abort" between 2.4.x and 2.5.x, though.
> Based on the kernel log you posted earlier, it looks like your problem may
> stem from the use of a START-STOP command. The patch below removes that
> command; it's a backport from 2.5. Try instal
Alan Stern <[EMAIL PROTECTED]> writes:
> Based on the kernel log you posted earlier, it looks like your problem may
> stem from the use of a START-STOP command. The patch below removes that
> command; it's a backport from 2.5. Try installing this and let us know if
> it helps.
Indeed it does!
the device being open. It should also
correct the unlinking of the urb problem you brought up.
I even removed the ...bh... from the tasklet name.
Thanks,
John
vicam-2.5.40.patch.gz
Description: Binary data
sentially the same thing here (which is why I did it).
> + kfree( vicam_v4l_priv );
> + kfree( vicam_usb_priv );
>
> Potentionally deadly if the device is open, you need to defer it to release
> in that case
I thought the same thing, but since the code just before this
This is a resend of the patch I sent earlier. I worked on the one earlier
while away from home and was unable to test it. This one has been fixed,
tested, and should be correct. Sorry for the confusion.
Patch is against 2.5.41.
Thanks,
John
vicam-2.5.41.patch.gz
Description: GNU Zip
the memory is freed, we don't touch the mutex.
How does this look?
Thanks,
John
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
[EMAIL PROTEC
nd there are no more users, if true,
then it waits for disconnect to finish and then frees the memory.
Any better?
I really appreciate you guys' help.
Thanks,
John
---
This sf.net email is sponsored by:ThinkGeek
Welcome to ge
email for deciding whether to free or defer freeing the
memory.
I've been plugging and unplugging my camera. Obviously, it's difficult to
create races on demand, but the driver successfully withstands plug/unplugs
with and without users using the camera during those plug/unplugs.
T
little bit better,
though, as it implies someone else has done something as bad as me.
> I see no more flaws.
Well, I found one between disconnect and release. I'm hoping this fixes that
race as well as the abusive use of semaphores you mentioned.
Thanks,
John
P.S. I'm not sure _ex
down mutex
if disconnected
up mutex
wait for disconnect
free memory
else
mark camera as not in use
up mutex
-- John
---
This sf.net email is sponsored b
her than having them compete.
I'm more than willing to submit patches to reach this end. Perhaps that's
where I should have started, but as I also said before (to Greg) I wrote a
separate driver partly as a learning experience and partly to get my
camera working a little bit faster.
John
is one very important thing that John's driver did that
> mine doesn't: asynchronous frame grabs.
Sounds like we're in agreement here on both counts.
> If John has the inclination, a patch to my 2.5.41 driver to do asynchronous
> streaming rather than synchronous streaming
are easy, some are a bit more complicated. My biggest
issue is that the driver that I submitted is a superset of the one that was
merged. I did a lot of work to write/test/debug/etc. that code, and my doing
that again would be a step backwards, in my mind.
John
---
use Image Magick to create a viewable gif/jpg/png/whatever.
And I'm not opposed to it. But I think that the driver's primary
responsibility should be to V4L apps, and if we can make shell utils work
as a side effect, cool. But they should take a back seat to V4L.
I'm willing to back off
The following patch removes the old framebuf_size and framebuf_read_start
values from the cam structure and simplifes the read function. It also
moves the needs dummy read check into the read_frame function. cp and dd
should both still work.
Patch is against 2.5.43, but I believe should apply clea
> The following patch removes the old framebuf_size and framebuf_read_start
> values from the cam structure and simplifes the read function. It also
> moves the needs dummy read check into the read_frame function. cp and dd
> should both still work.
This is in addition to the previous patch. It sh
> You no longer check buf against NULL, can a misbehaved program cause a
> problematic seg fault in the kernel?
I put the onus of checking buf != NULL and count != 0 on copy_to_user.
> I'm betting that semaphore needs to be upped before returning :)
Yes, it does. I'll leave that to you.
-
attached camera individually by a shell utility such as echo.
If we want to wait, fine, otherwise please apply. Patch is against
the current usb 2.5 bk tree
Thanks,
John
--- linux-current/drivers/usb/media/vicam.c 2002-10-22 20:41:04.0 -0700
+++ linux-vicam/drivers/usb/media/vicam.c 2
ything at the moment. One thing at a
time.
John
---
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-b
> Why take out the usb_put_dev() call?
It seemed to be keeping the driver from being inserted, remove, and
re-inserted. I didn't figure out why... just that this was the cause.
John
---
This sf.net emial is sponsored by: Influence th
> Please don't remove the proc interface. This is a V4L issue. It's in
> there because this is a V4L driver.
I saw that you were going to raise the issue on that list. I said the patch
can wait. Regardless, though, I think that the driverfs is where this kind
of thing is supposed to be going.
A
2.4 tree at
some point.
John
vicam-2.5.41.patch.gz
Description: GNU Zip compressed data
e (and submitted as a completed,
stable, working driver) and don't want to duplicate my own efforts. If
someone else would like to take up the job of trying to merge the two
drivers, I'm happy to give them my code.
If not, then I ask that we revisit the idea of having both drive
buffers to the open and close calls only.
I don't think my previous send of this made it to the list, and this also
adds a forgotten fixup in open that should have been included in my previous
send of this.
Patch is against 2.5.45.
Thanks,
John
vicam.c.patch
Description: Binary data
costs and move to a slightly faster level. The
problem seems to be that a PC does not want to be a peripheral. Even with a
host-to-host cable, I get 2 chiefs, and no indians! Any ideas would be greatly
appreciated.
John Marshall
Greg KH wrote:
> On Mon, Nov 04, 2002 at 03:33:20PM -06
urn 0 on
success instead of the number of bytes transferred.
- simplify the initialize camera function
Patch needs testing; please review and test (Joe this means you :)).
Patch is against Greg's current USB tree.
Thanks,
John
--- linux-a/drivers/usb/media/vicam.c 2002-1
against 2.5.49 which I believe is the same as usb-current.
It works for me.
(I am still aware that there are some functions that fail that don't
return values and some that do but aren't checked... one thing at a
time. :) )
John
[1] I don't know that smp type locking is necessar
avoided it as much as we can for the time being. I was more
curious whether or not it was something that was being done in the code that could be
fixed
to remove this warning.
Thanks,
John
---
This sf.net email is sp
ase. It also fixes a bug in the y loop that wrote beyond its bound.
Patch is against the current USB BK tree and has been tested on 2.5.49.
Please apply.
Thanks,
John
--- drivers/usb/media/vicam-usb-current.c 2002-11-25 20:13:00.0 -0800
+++ drivers/usb/media/vicam.c 2002-11-26 18:1
driver never will request an irq"?
-- John
On 6/4/06, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Am Sonntag, 4. Juni 2006 18:29 schrieb John Que:
> > I had noticed that the zd1211 driver does call request_irq() in
> > zd1205_open(),
> > file zd1205.c; grepping for
that the softmac layer does not call request_irq() on
behalf of the driver because this is not supposed to be like it, as I understand
its functionality. Can anybody briefly calrify this point ?
Regards,
John
On 6/4/06, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Am Samstag, 3. Juni 2006
es.
I'd gladly appreciate any feedback.
John
-
John M Lauck
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Do
I've been seeing a weird problem with the later 2.6
series kernels where a usb device is recognized
correctly if present at kernel boot time. However
connection (or removal) of a device doesn't seem to
generate connect/disconnect interrupts to ohci_hcd
according to /proc/interrupts.
Behavior varie
David Brownell wrote:
On Friday 19 November 2004 03:41, john cooper wrote:
I combed through the mail archives but didn't see
anything relevant. Has anyone experienced similar
problems?
Fixed in 2.6.10-rc2?
Hmm, not in my case. Connects/disconnects don't appear
to be recognized
spec v1.1
It does say that only 2 channel playback works in on Mac systems...
I attached some info below that might help if anyone is interested.
Otherwise, if anyone knows a good linux compatible USB microphone audio
input device, that would be great! ;)
Thanks,
-John
=
Class 0 ((Defi
s for the feedback, Thomas.
-John
my /proc/asound/pcm file:
00-00: USB Audio : USB Audio : playback 1 : capture 1
my /proc/asound/cards file:
0 [Audio ]: USB-Audio - USB Audio
USB Audio at usb-:00:1d.1-1, full speed
Still, here is the output of lsusb -v fo
lving this issue. If the solution
related to it is already resolved in newer releases
please let me know.
Thanks in advance.
Best regards,
Lara John
PS: If any information is missing please let me know.
__
Do you Yahoo!?
Yahoo! Mail - Find
On Fri, 9 Mar 2001 [EMAIL PROTECTED] wrote:
> I will be out of the office starting 09/03/2001 and will not return until
> 20/03/2001.
sheesh! I leave the office five minutes and he doing this ;)
I guess now's the time to pass the reins over.. Brian's the contact inside
APC from now on. I've mo
On Mon, 16 Apr 2001, Matthias Bruestle wrote:
> > a CATC
>
> A what?
A device inspector from CATC. It goes between the computer and the USB
device and reports the traffic going over the wire. They cost a fair bit
but are extremely useful for seeing what's being transmitted.
johnmc.
--
. htt
http://www.dlink.com/products/wireless/dwl120/
Has anyone had any experiences with this bit of kit ? If so could you relate
them. I'm considering buying one, but before I burn £120 I'd quite like to
know what my chances are of getting it working under Linux :-)
Thank
On Thursday, June 28, 2001, at 09:19 PM, Yang, Neil L wrote:
> if( (((unsigned long)td->hwCBP) & 0x10) ) {
> printk("td_fill() hwCBP %p, a20!\n", (void *)td->hwCBP);
>
> }
See the SA- specification update. DMA transfers having a particular
address bit set gene
On Friday, June 29, 2001, at 01:19 AM, Yang, Neil L wrote:
> Thanks for the info.
> You mentioned that modern kernels should be allocating DMA-safe buffers
> from
> a region in RAM known to be safe from this bug. I'm actually getting
> that
> warning, but I'm using linux 2.4.5-rmk6-np1 kernel
nterest follow.. any feedback would be appreciated.
john.c
--
John Clemens http://www.deater.net/john
[EMAIL PROTECTED] ICQ: 7175925, IM: PianoManO8
"I Hate Quotes" -- Samuel L. Clemens
00:02.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03)
(prog-i
I get tons of these, about 1 a second.
usb 1-3: device not accepting address 86, error -71
usb 1-3: device not accepting address 87, error -71
usb 1-3: device not accepting address 88, error -71
usb 1-3: device not accepting address 89, error -71
usb 1-3: device not accepting address 90
linux-usb-devel] usb 1-3: device not accepting address 86, error -71
John H. wrote:> ...> usb 1-3: device not accepting address 95, error -71>
usb 1-3: device not accepting address 96, error -71> usb 1-3: device not accepting
address 97, error -71> > > starting way before tha
myway.com refuses to acknowledge this problem. I have said this to them several times.
Did you not get all my usb information from that paste of /proc/bus/usb/devices I sent
you? I also have a usb 2.0 hub.
___
No banners. No pop-ups. No kidding.
M
04/12, David Brownell < [EMAIL PROTECTED] > wrote:
From: David Brownell [mailto: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Date: Mon, 12 Apr 2004 11:45:10 -0700
Subject: Re: [linux-usb-devel] usb 1-3: device not accepting address 86, error -71
John H. wrote:> D
I wanted to find out if this is supported before I buy it.
http://www.xpertronics.com/pd_msi_vox.cfm
http://www.msi.com.tw/program/products/multimedia/mut/pro_mut_detail.php?UID=536
___
No banners. No pop-ups. No kidding.
Make My Way your home on
I was wondering if there are any usb 2.0 tv tuners that work in linux, that do not
require line in and have the hardware decoding on the device(not requiring the cpu)
thanks
___
No banners. No pop-ups. No kidding.
Make My Way your home on the Web -
what is the status of being able to use scanner through libusb w/o root?
___
No banners. No pop-ups. No kidding.
Make My Way your home on the Web - http://www.myway.com
---
This SF.Net email is spons
it's ready to
be applied.
I've also attached the firmware file.
Thanks,
John
vicam
Description: Binary data
--- vicam.c.orig2004-04-27 11:21:09.0 -0700
+++ vicam.c 2004-04-27 14:08:23.0 -0700
@@ -42,6 +42,7 @@
#include
#include
#include
+#include
#incl
ready to rip out all firmware related stuff from the kernel source. I
thought that rather than someone having to go out and hack the source
to get the camera to work, it would be nicer to just convert to this
method. It's usability and "political correctness" more than anythin
e, I can try
re-plugging it if you like, and seeing what happens.
John
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on
Greg> On Fri, Mar 09, 2007 at 10:40:21AM -0500, John Stoffel wrote:
>>
>> Hi all,
>>
>> I've just compiled and installed 2.6.21-rc3 on my Dual CPU Dell
>> Precision 610MT system. Dual 550mhz Xeon, 768mb of RAM. Mix of SCSI,
>> ATA drives. I&#x
Duh... forgot the patches:
2.6.21-rc-usb-serial.patch
Description: two patches for usbserial oops on 2.6.21-rc3
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the c
y that the write should envoke the control msg and set a
pointer for the data required for the urb. Saw examples of code using
the control msg directly, but nothing with ioctl()
I'm a newbee at this, any help would be appreciated. Hope I stated the
question properl
ally performed and added to the message. I
suspect the USB Host device automatically puts that in. Would seem
reasonable, can't find anything to expicitly confirm the CRC calculation.
Any suggestions would be appreciated... in the interest of brevity,
I'll not include the source for n
Alan Stern wrote:
>On Sat, 14 Apr 2007, John Wojnaroski wrote:
>
>
>
>>Is there a simple, quick, uncomplicated tool to look see what is
>>actually going down the wire? Lots of sniffers for MS stuff, could not
>>find similar tools for the linux OS. Something al
#x27;t have the source,
just the .exe file and the results.
Regards
John
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just dat
Alan Stern wrote:
>On Sun, 15 Apr 2007, John Wojnaroski wrote:
>
>
>
>>Hi Alan,
>>
>>Thanks for working your way through my mess.
>>
>>I was trying a numer of ideas last night and things got a little convoluted.
>>
>>You've answered my
Alan Stern wrote:
On Mon, 16 Apr 2007, John Wojnaroski wrote:
Okay, I will do that, so if I understand your direction
get SnoopyPro from sourceforge, install it under MS windows, and run
some traces with the device working under that OS
then post the results
correct?
That&#
Alan Stern wrote:
>On Mon, 16 Apr 2007, John Wojnaroski wrote:
>
>
>
>>OK, attached is a log report.Not all that conversant in analyzing
>>the log. about the only item I note is the order of the last two bytes
>>defining the packet size; SnoopyPro shows
Alan Stern wrote:
>On Wed, 18 Apr 2007, John Wojnaroski wrote:
>
>
>
>>OK, so an IN transfer might look something like <22 09 0200 >
>>
>>
>
>Except that it couldn't use 0x22 in the first byte. The high-order bit of
>that byte d
mething wrong or mis-interpreting what is required to communicate with
the device.
I don't want to become an expert on writing USB drivers, at least not at
this time. Just a simple request as to how to make the device work
under linux. If the forum can't handle that
1 - 100 of 217 matches
Mail list logo
