Bug 18542 - No driver for Ricoh 0xE852 xD/MS card reader
Summary: No driver for Ricoh 0xE852 xD/MS card reader
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Flash/Memory Technology Devices (show other bugs)
Hardware: All Linux
: P1 enhancement
Assignee: David Woodhouse
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-15 07:24 UTC by Christopher Head
Modified: 2013-12-10 22:05 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.6.11
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Christopher Head 2010-09-15 07:24:49 UTC
The mtd/nand/r852 driver supports PCI device ID 0x0852, but my laptop has a Ricoh card reader with device ID 0xE852, for which there doesn't seem to be a driver.

There are actually four Ricoh devices detected by lspci:
0xE822 is an MMC/SD reader which works fine
0xE230 is something. I don't know what exactly.
0xE852 is the xD (and maybe also MemoryStick?) card reader, at least according to a poke around in Windows.
0xE832 is a Firewire controller, which is picked up by OHCI but I've never tested.

I have no idea if the E852 is so similar to the 852 it's as simple as just adding another PCI ID, or if it's so different it needs a new driver, or what. Therefore, I haven't yet tested just adding the new PCI ID to the existing driver, since if it's a substantially different device, I'd rather not destroy my reader or cards.
Comment 1 Christopher Head 2010-12-23 20:26:53 UTC
I just found out about the -q option to lspci, and the database does have entries for some of these ID numbers.

Apparently, the device are:
06:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 01)

06:00.1 System peripheral [0880]: Ricoh Co Ltd Memory Stick Host Controller [1180:e230] (rev 01)

06:00.2 System peripheral [0880]: Ricoh Co Ltd Device [1180:e852] (rev 01)

06:00.3 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd FireWire Host Controller [1180:e832] (rev 01)
Comment 2 Christopher Head 2012-08-14 03:37:13 UTC
Why is this ticket closed? The current mainline kernel does not appear to have changed anything in this respect?
Comment 3 Christopher Head 2013-02-03 23:08:42 UTC
I have reopened this ticket and fixed the kernel version number field to indicate that there is still no driver for this device.
Comment 4 Alan 2013-12-10 22:05:44 UTC
That isn't a bug. Linux can only support hardware people contribute drivers for

Note You need to log in before you can comment on or make changes to this bug.