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: <20091123162119.3777e14d@fido2.homeip.net>
Date:	Mon, 23 Nov 2009 16:21:19 -0800
From:	Philip Langdale <philipl@...rt.org>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	philipl@...mni.utexas.net
Subject: Re: The work of ricoh_mmc isn't detected by pci core

On Tue, 24 Nov 2009 02:13:03 +0200
Maxim Levitsky <maximlevitsky@...il.com> wrote:

> 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

Hmm, yes, that's true (and if you do a warn reboot, the effect is
sticky and then MMC is missing). I don't know how to make the pci
core re-enumerate devices, but maybe there is a way. I'm not in
a position to do this myself in the near future; so I'm afraid
that if you need this fixed, you'll have to do the digging.

Is it sufficient to call pci_rescan_bus at the end of the disable/enable
routine in ricoh_mmc?

--phil
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ