From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: USB device debugging
Date: Wed, 25 May 2016 14:56:56 +0200 [thread overview]
Message-ID: <87h9dmnvmv.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAL0PPtKPSshhoODhUiK6B5oObYvZG1WaOF26QeCaTbzT40OGNg@mail.gmail.com> (Narasimha M.'s message of "Wed, 25 May 2016 18:07:09 +0530")
Narasimha M <mnarasimha786@gmail.com> writes:
> Thanks for clear explanation. Could you please let me know where does
> host_controller will be present is it in USB device or USB core part
> of kernel.
>
> Actually my issue is that we ported Gobinet driver from open source to
> support one dongle. After porting, it is working fine on little endian
> host (linux-2.6.31 kernel). We have added some changes in driver code
> o support it for big endian hosts. After adding the changes with the
> help of le16_to_cpu () function dongle is working in one of our big
> endian hosts (which has linux-3.10.20), but facing corrupted packet
> issue in other bigendian supported host (linux-2.6.32). Could you
> please help in providing some pointers here
Sounds like you have a bug in your code. Did you expect me to make a
more precise guess?
Bj?rn
next prev parent reply other threads:[~2016-05-25 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 7:39 USB device debugging Narasimha M
2016-05-24 7:59 ` Carlo Caione
2016-05-24 8:18 ` Narasimha M
2016-05-24 14:46 ` Greg KH
2016-05-24 17:00 ` Bjørn Mork
2016-05-25 9:00 ` Narasimha M
2016-05-25 10:11 ` Bjørn Mork
2016-05-25 10:51 ` Narasimha M
2016-05-25 11:06 ` Bjørn Mork
2016-05-25 11:29 ` Narasimha M
2016-05-25 12:01 ` Bjørn Mork
2016-05-25 12:37 ` Narasimha M
2016-05-25 12:56 ` Bjørn Mork [this message]
2016-05-25 15:24 ` Narasimha M
2016-05-25 15:42 ` Narasimha M
2016-05-25 18:20 ` Greg KH
2016-05-26 5:31 ` Narasimha M
2016-05-26 5:51 ` Greg KH
2016-05-26 6:23 ` Narasimha M
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=87h9dmnvmv.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.