From: Clemens Ladisch <clemens@ladisch.de>
To: Donnie Menig <soundprizm@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Tascam US-1641 Firmware File
Date: Thu, 05 Feb 2009 13:08:25 +0100 [thread overview]
Message-ID: <498AD6B9.4070903@ladisch.de> (raw)
In-Reply-To: <58f7a09c0902021427i3eaa9955nf862b1ef282569ca@mail.gmail.com>
Donnie Menig wrote:
> I have the Tascam US-1641 firmware now... I'm pretty sure I did everything
> right, but I keep getting the "can't modify CPUCS: Broken pipe" or "unable
> to open for input." error.
You didn't tell what you're doing with the firmware, or how you're doing
it, but I guess you are trying to download it.
"Broken pipe" means error code EPIPE, which means, according to
linux/Documentation/usb/error-codes.txt, "endpoint is stalled", which
means that the device did not like what you did to it.
The "CPUCS" indicates that you're trying to use the EZ-USB download
protocol; however, the firmware file is too big for that, i.e., your
device is based on some other chipset.
Best regards,
Clemens
prev parent reply other threads:[~2009-02-05 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 22:27 Tascam US-1641 Firmware File Donnie Menig
2009-02-05 9:24 ` Takashi Iwai
2009-02-05 12:08 ` Clemens Ladisch [this message]
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=498AD6B9.4070903@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=soundprizm@gmail.com \
/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