linux-kernel - Re: Is the Ricoh R5C822 documentation available?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 21 Dec 2008 17:59:20 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	David Härdeman <david@...deman.nu>
Cc:	linux-kernel@...r.kernel.org, tbm@...ius.com
Subject: Re: Is the Ricoh R5C822 documentation available?

On Mon, 8 Dec 2008 22:54:58 +0100
David Härdeman <david@...deman.nu> wrote:

> The Ricoh R5C822 card reader in my laptop includes a smart card reader 
> (http://www.ricoh.com/LSI/product_pcif/pcc/5c821/index.html) but it 
> doesn't seem supported by the kernel.
> 
> So I was wondering whether the documentation for the Ricoh card reader is 
> available from somewhere (or is the sdhci support the result of reverse 
> engineering?).
> 
> Ricoh told me to ask HP and HP hasn't answered at all...
> 

In which case you've gotten further than most of us. Ricoh are not an
helpful vendor so getting their hardware up and running is always an
uphill battle.

sdhci was the result of reverse engineering yes, but that is hardly
relevant here as it is not a ricoh interface but a standardised one.
The fixes in ricoh_mmc were based on information received from an OEM,
not from Ricoh directly.

So right now I'd say reverse engineering is your only option if you
want to support that piece of hardware.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)