Commit 015664d1 authored by Bastien Nocera's avatar Bastien Nocera Committed by Greg Kroah-Hartman
Browse files

USB: rio500: Remove Rio 500 kernel driver 

The Rio500 kernel driver has not been used by Rio500 owners since 2001
not long after the rio500 project added support for a user-space USB stack
through the very first versions of usbdevfs and then libusb.

Support for the kernel driver was removed from the upstream utilities
in 2008:
https://gitlab.freedesktop.org/hadess/rio500/commit/943f624ab721eb8281c287650fcc9e2026f6f5db



Cc: Cesar Miquel <miquel@df.uba.ar>
Signed-off-by: default avatarBastien Nocera <hadess@hadess.net>
Cc: stable <stable@vger.kernel.org>
Link: https://lore.kernel.org/r/6251c17584d220472ce882a3d9c199c401a51a71.camel@hadess.net


Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 54ecb8f7

Documentation/usb/rio.rst

deleted100644 → 0
+0 −109
Original line number Diff line number Diff line 
============

Diamonds Rio

============



Copyright (C) 1999, 2000 Bruce Tenison



Portions Copyright (C) 1999, 2000 David Nelson



Thanks to David Nelson for guidance and the usage of the scanner.txt

and scanner.c files to model our driver and this informative file.



Mar. 2, 2000



Changes

=======



- Initial Revision





Overview

========



This README will address issues regarding how to configure the kernel

to access a RIO 500 mp3 player.

Before I explain how to use this to access the Rio500 please be warned:



.. warning::



   Please note that this software is still under development.  The authors

   are in no way responsible for any damage that may occur, no matter how

   inconsequential.



It seems that the Rio has a problem when sending .mp3 with low batteries.

I suggest when the batteries are low and you want to transfer stuff that you

replace it with a fresh one. In my case, what happened is I lost two 16kb

blocks (they are no longer usable to store information to it). But I don't

know if that's normal or not; it could simply be a problem with the flash

memory.



In an extreme case, I left my Rio playing overnight and the batteries wore

down to nothing and appear to have corrupted the flash memory. My RIO

needed to be replaced as a result.  Diamond tech support is aware of the

problem.  Do NOT allow your batteries to wear down to nothing before

changing them.  It appears RIO 500 firmware does not handle low battery

power well at all.



On systems with OHCI controllers, the kernel OHCI code appears to have

power on problems with some chipsets.  If you are having problems

connecting to your RIO 500, try turning it on first and then plugging it

into the USB cable.



Contact Information

-------------------



   The main page for the project is hosted at sourceforge.net in the following

   URL: <http://rio500.sourceforge.net>. You can also go to the project's

   sourceforge home page at: <http://sourceforge.net/projects/rio500/>.

   There is also a mailing list: rio500-users@lists.sourceforge.net



Authors

-------



Most of the code was written by Cesar Miquel <miquel@df.uba.ar>. Keith

Clayton <kclayton@jps.net> is incharge of the PPC port and making sure

things work there. Bruce Tenison <btenison@dibbs.net> is adding support

for .fon files and also does testing. The program will mostly sure be

re-written and Pete Ikusz along with the rest will re-design it. I would

also like to thank Tri Nguyen <tmn_3022000@hotmail.com> who provided use

with some important information regarding the communication with the Rio.



Additional Information and userspace tools



	http://rio500.sourceforge.net/





Requirements

============



A host with a USB port running a Linux kernel with RIO 500 support enabled.



The driver is a module called rio500, which should be automatically loaded

as you plug in your device. If that fails you can manually load it with



  modprobe rio500



Udev should automatically create a device node as soon as plug in your device.

If that fails, you can manually add a device for the USB rio500::



  mknod /dev/usb/rio500 c 180 64



In that case, set appropriate permissions for /dev/usb/rio500 (don't forget

about group and world permissions).  Both read and write permissions are

required for proper operation.



That's it.  The Rio500 Utils at: http://rio500.sourceforge.net should

be able to access the rio500.



Limits

======



You can use only a single rio500 device at a time with your computer.



Bugs

====



If you encounter any problems feel free to drop me an email.



Bruce Tenison

btenison@dibbs.net

MAINTAINERS

+0 −7
Original line number Diff line number Diff line
@@ -16762,13 +16762,6 @@ W: http://www.linux-usb.org/usbnet 
S:	Maintained

F:	drivers/net/usb/dm9601.c













USB DIAMOND RIO500 DRIVER













M:	Cesar Miquel <miquel@df.uba.ar>













L:	rio500-users@lists.sourceforge.net













W:	http://rio500.sourceforge.net













S:	Maintained













F:	drivers/usb/misc/rio500*



























USB EHCI DRIVER















M:	Alan Stern <stern@rowland.harvard.edu>















L:	linux-usb@vger.kernel.org

































arch/arm/configs/badge4_defconfig



+0
−1






























Original line number
Diff line number
Diff line








@@ -91,7 +91,6 @@ CONFIG_USB_SERIAL_PL2303=m













CONFIG_USB_SERIAL_CYBERJACK=m















CONFIG_USB_SERIAL_XIRCOM=m















CONFIG_USB_SERIAL_OMNINET=m













CONFIG_USB_RIO500=m















CONFIG_EXT2_FS=m















CONFIG_EXT3_FS=m















CONFIG_MSDOS_FS=y

































arch/arm/configs/corgi_defconfig



+0
−1






























Original line number
Diff line number
Diff line








@@ -195,7 +195,6 @@ CONFIG_USB_SERIAL_XIRCOM=m













CONFIG_USB_SERIAL_OMNINET=m















CONFIG_USB_EMI62=m















CONFIG_USB_EMI26=m













CONFIG_USB_RIO500=m















CONFIG_USB_LEGOTOWER=m















CONFIG_USB_LCD=m















CONFIG_USB_CYTHERM=m

































arch/arm/configs/pxa_defconfig



+0
−1






























Original line number
Diff line number
Diff line








@@ -581,7 +581,6 @@ CONFIG_USB_SERIAL_XIRCOM=m













CONFIG_USB_SERIAL_OMNINET=m















CONFIG_USB_EMI62=m















CONFIG_USB_EMI26=m













CONFIG_USB_RIO500=m















CONFIG_USB_LEGOTOWER=m















CONFIG_USB_LCD=m















CONFIG_USB_CYTHERM=m









































































CRA Git | Maintained and supported by SUSTech CRA and CCSE