linux-kernel - Re: Experimental driver for Ricoh Bay1Controller SD Card readers

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <45A0C3A7.2040506@gmail.com>
Date:	Sun, 07 Jan 2007 10:55:28 +0059
From:	Jiri Slaby <jirislaby@...il.com>
To:	Sascha Sommer <saschasommer@...enet.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, rmk+mmc@....linux.org.uk
Subject: Re: Experimental driver for Ricoh Bay1Controller SD Card readers

Sascha Sommer wrote:
> Hi,
> 
> Attached is a very experimental driver for a Ricoh SD Card reader that can be 
> found in some notebooks like the Samsung P35.
> 
> Whenever a sd card is inserted into one of these notebooks, a virtual pcmcia 
> card will show up:
> 
> Socket 0:
>   product info: "RICOH", "Bay1Controller", "", ""
>   manfid: 0x0000, 0x0000
> 
> In order to write this driver I hacked qemu to have access to the cardbus 
> bridge containing this card. I then logged the register accesses of the 
> windows xp driver and tryed to analyse them.
> 
> As the meanings of most of the register are still unknown to me, I consider 
> this driver very experimental. It is possible that this driver might destroy 
> your data or your hardware. Use at your own risk! 
> 
> Other problems:
> - I only implemented reading support
> - I only tested with a 128 MB SD card, no idea what would be needed to support
>   other card types
> - irqs are not supported
> - dma is not supported
> - it is very slow
> - the registers can be found on the cardbus bridge and not on the virtual 
>   pcmcia card. The cardbus bridge is already claimed by yenta_socket. 
>   Therefore the driver currently uses pci_find_device to find the cardbus

- pci_find_device is no go today. Use pci_get_device (+ pci_dev_get, _put).
- ioremap->pci_iomap
- iobase should be __iomem.
- codingstyle (char* buffer, for(loop, if(data){, ...)

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/