DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:content-type:date:message-id:mime-version
         :x-mailer:content-transfer-encoding;
        b=sVbf1ZR5G23U7HJ5fOkwy8nPJAwQTtL5X4vXz9IYO2x+ibOp/+/dVebd0laqq8u+OO
         F64q1d86JI9NQR5yFrDLe810z3Q/HPTVdNSHQZnIJFQWV0ef6znEfsCQALFPGY0L762P
         5jK+76YAPctLxUXSTeXxm+3lAHWivEb5R9A9s=
Subject: The work of ricoh_mmc isn't detected by pci core
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: philipl@alumni.utexas.net
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 24 Nov 2009 02:13:03 +0200
Message-ID: <1259021583.16650.9.camel@maxim-laptop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1009
Lines: 28

Hi,

I noticed that usage of ricoh_mmc will lead to this


07:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
07:00.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
07:00.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
07:00.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)


I don't have yet an MMC card to test if the driver itself working, 
but what happens is that once disabled, all pci functions shift 
one level, but kernel doesn't pick that up.

If one implements drivers for XD and memstick parts, this would break
everything. (And I have some plans for XD part)

ricoh_mmc is built-in, but this doesn't help.

Best regards,
Maxim Levitsky

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/