From: Florian Engelhardt <dot@dot-matrix.de>
To: linux-kernel@vger.kernel.org
Subject: rio500 driver broken in linux 2.6.x
Date: Wed, 28 Jan 2004 14:31:23 +0100 [thread overview]
Message-ID: <20040128143123.69b6f281@HAL2000> (raw)
Hello,
the rio500 driver seems to be broken, more and more people are talkin
about it. I allready wrote a mail to the maintainer of this dirver but
i got no response. The mailinglist which i found in the
/usr/src/linux/MAINTAINERS file is dead.
The Bug:
You con compile the driver without proplems, and when you connect the
rio500 to the usb bus, the kernel reports that he found it. But you can
not do any operations on it with the rio500 utils from sourceforge.
If i try to upload a file, or to create a folder on the rio500 the
connection to the player freezes and when i´m not killing the process,
the system hangs.
Does anyone of you know about this problem?
The problem depends on the new kernel, couse with the 2.4.x kernel there
are no problems with the rio utils from sourceforge.
Regards
Florian Engelhardt
--
[X] Nail here for a new monitor
next reply other threads:[~2004-01-28 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 13:31 Florian Engelhardt [this message]
2004-02-01 15:34 ` rio500 driver broken in linux 2.6.x Yury V. Umanets
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=20040128143123.69b6f281@HAL2000 \
--to=dot@dot-matrix.de \
--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