From: iweiny@pacbell.net
To: linuxppc-dev@lists.linuxppc.org (linuxdev)
Subject: USB Bulk transfers
Date: Mon, 29 Nov 1999 17:20:47 -0800 (PST) [thread overview]
Message-ID: <199911300120.RAA01443@batcave2.localdomain> (raw)
Has anyone done anything with the USB bulk transfers?
DETAILS:
PowerMac 8500
USB card and Mouse WORK!
kernel 2.2.12 self compiled
USB 2.3.29 code from Pauls rsync tree (modified for 2.2 kernel)
I have a Kodak Digital camera (DC-265) and I would like to get the USB working
for it. I have been in contact with many from Intel linux side who have gotten
it to work with the recent dc2xx.c driver in the 2.3.xx USB stack.
My problem spcifically is this. The control messages seem to be fine and
recognize the camera, set up the Endpoints and pipes and report the dc2xx
driver to have claimed the interface. However, when user land accesses the
device the following message appears.
kernel: ohci_bulk_msg_completed 0, c1eae000, 68, c2235dd0
kernel: ohci_bulk_msg_completed 9, c1eae000, 0, c2235df0
kernel: ohci_bulk_msg done, status 9 (bytes_transferred = 0).
The second msg is the read request and the status 9 is... What? I thought it
was data underflow but that error number is -9 not 9?
I am not sure what is happening but I am thinking the camera is not getting the
68 bytes as the write msg claims. Or quite possibly I have an endianess issue
and when the camera gets the data it does not understand? I know the PCI is LE
and therefore USB is as well. But is the data passed as LE or BE or whatever
the processor sends?
Thanks in advance
Ira Weiny
iweiny@acm.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-30 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 1:20 iweiny [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-06 2:45 USB Bulk transfers harlan
1999-11-30 0:39 Dan Bethe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199911300120.RAA01443@batcave2.localdomain \
--to=iweiny@pacbell.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).