From: David Brownell <david-b@pacbell.net>
To: Kallol Biswas <kallol.biswas@efi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: netchip's net2280 usb 2.0 device
Date: Mon, 31 Mar 2003 11:55:32 -0800 [thread overview]
Message-ID: <3E889D34.3000303@pacbell.net> (raw)
In-Reply-To: 3E85CA77.2020301@pacbell.net
David Brownell wrote:
> Hi,
>
>> We have been using the net2280 chip (usb 2.0) as a usb target
>> printer device. We have been seeing data corruption problems
>> during a bulk out transfer when data is taken out the device
>> quite slow. The corruption size is only 4 bytes suggesting
>> a device problem. Is anyone using this chip and has anyone
>> encountered similar problem?
>
>
> I've certainly been using it ... there's a Linux driver for it,
> part of a "USB Gadget" framework that could support other such
> "target mode" hardware, at http://kernel.bkbits.net/~david-b
> for general use. (Download from BK, the 2.5.64 patch doesn't
> include the net2280 driver and there's no 2.4 patch yet. I'll
> send out an announcement soon, when I update the patches.)
Just done. There are now patches for 2.4 and 2.5 kernels.
> I haven't run into that particular problem, but it sounds
> like it might be a known erratum ... have you asked NetChip, or
> checked the 14-March errata at their website? They've been
> pretty responsive to my questions.
I have in mind particularly erratum 0106 ... which might have
been what was making my TTCP testing from working. Well, at
least the latest code for that is now behaving.
- Dave
>> Is there any other 2.0 usb chip that can be used as a target mode
>> device?
>
>
> The net2280 is the only such chip I know of that talks PCI
> directly. So it's particularly Linux-friendly: it doesn't
> need special bus adapter hardware.
>
> - Dave
>
>
next prev parent reply other threads:[~2003-03-31 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 16:31 netchip's net2280 usb 2.0 device David Brownell
2003-03-31 19:55 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-29 0:34 Kallol Biswas
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=3E889D34.3000303@pacbell.net \
--to=david-b@pacbell.net \
--cc=kallol.biswas@efi.com \
--cc=linux-kernel@vger.kernel.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