Hi!
mmc0: error -95 whilst initialising SD card
That's interesting. Would you mind trying to bisect? (Knowing whether
2.6.38 final does it, for example, would be very helpful.)
It may need one or two tries on 2.6.38 but it's there too.
There aren't many -EOPNOTSUPP returns in
Hi,
(Adding linux-mmc@.)
On Tue, Apr 12 2011, Cyril Hrubis wrote:
Hi!
When I insert the mmc card to zaurus, it gets properly detected and prints
some
info into console. Mounting reading/writing files works fine.
However when the card is removed (doesn't need to be mounted before), the
Hi!
When I insert the mmc card to zaurus, it gets properly detected and prints
some
info into console. Mounting reading/writing files works fine.
However when the card is removed (doesn't need to be mounted before), the
removal is most likely not detected, so when I insert it again,
Hi,
On Tue, Apr 12 2011, Cyril Hrubis wrote:
Your symptoms match the bug that was fixed by:
bad3babace2ee4d (mmc: fix CONFIG_MMC_UNSAFE_RESUME regression)
but this fix made it into 2.6.38, so if you're using 2.6.38 final then
you shouldn't be seeing this. Could you confirm that you have
Hi!
Your symptoms match the bug that was fixed by:
bad3babace2ee4d (mmc: fix CONFIG_MMC_UNSAFE_RESUME regression)
but this fix made it into 2.6.38, so if you're using 2.6.38 final then
you shouldn't be seeing this. Could you confirm that you have this
patch?
It seems that the
Hi,
On Tue, Apr 12 2011, Cyril Hrubis wrote:
Tried 2.6.39-rc3 both with and without CONFIG_MMC_UNSAFE_RESUME and the
insert/remove detection works but both with and without unsafe resume, if the
card is removed for more than second or two it fails to recognize the card
after insertion failing
Hi,
On Tue, Apr 12 2011, Chris Ball wrote:
There aren't many -EOPNOTSUPP returns in the stack. I see:
card/block.c: mmc_blk_issue_secdiscard_rq and mmc_blk_issue_discard_rq
card/core.c: mmc_erase
core/sd_ops.c: mmc_app_cmd
Mind doing some instrumentation to figure out which it is?
Hi!
Tried 2.6.39-rc3 both with and without CONFIG_MMC_UNSAFE_RESUME and the
insert/remove detection works but both with and without unsafe resume, if
the
card is removed for more than second or two it fails to recognize the card
after insertion failing with:
mmc0: error -95 whilst
