LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: Sergey Yanovich <ynvich@gmail.com>, linux-kernel@vger.kernel.org
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>
Subject: Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Date: Thu, 19 Apr 2007 19:17:27 -0700 (PDT) [thread overview]
Message-ID: <204224.14405.qm@web36703.mail.mud.yahoo.com> (raw)
In-Reply-To: <4627D402.8020107@gmail.com>
Have you looked at the last version (0.8)? It fixed all outstanding issues (as far as I know).
--- Sergey Yanovich <ynvich@gmail.com> wrote:
---------------------------------
Hi,
The device is present in many notebooks. Notebooks depend heavily onsuspend/resume functionality.
tifm_core/7xx1/sd family is an ambitous,but uncompleted project. It used to crash on resuming, or
hang up onsuspending. A less common failure used to be trigerred by a fast cardinsert/removal
sequence. Finally, tifm_sd module needs to be manuallyinserted.
I have found it easier to rewrite the driver, than to fix. This driveris kind of mutant. The bones
are taken from sdhci and omap, the meat -from tifm_*. It contains all features (and bugs except
named above) oftifm_* as it was in kernel 2.6.21-rc7.
I have been testing this version since linux-2.6.18 (daily readingphotos from cards, daily
suspending/resuming) without a single glitch.
This patch only provides sources.
[PATCH1/2] [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Kernel configuration in this message.
[PATCH2/2] [mmc] alternative TIFM driver config for 2.6.21-rc7
Alex Dubov has done exceptionally great lots of work to teach linuxspeak to TIFM. This is just a
reorganization of his project.
The driver seems to be practically stable, but it definitely must betested by more people. Please
also report any issues with this driverto linux bug#8352 so that valuable info is not lost.
Best regards,
Sergey Yanovich
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next parent reply other threads:[~2007-04-20 2:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4627D402.8020107@gmail.com>
2007-04-20 2:17 ` Alex Dubov [this message]
2007-04-20 8:20 ` Brad Campbell
2007-04-20 8:31 ` Fabio Comolli
2007-04-20 10:10 ` Sergey Yanovich
2007-04-22 1:34 ` Alex Dubov
2007-04-22 12:15 ` Sergey Yanovich
2007-04-23 7:04 ` Matthew Garrett
2007-04-23 7:29 ` Sergey Yanovich
2007-04-23 13:16 ` Alex Dubov
2007-04-23 14:12 ` Sergey Yanovich
2007-04-24 2:55 ` Alex Dubov
2007-04-24 8:05 ` Sergey Yanovich
2007-04-26 6:36 ` Pierre Ossman
2007-04-27 2:41 ` Alex Dubov
2007-04-27 7:50 ` Sergey Yanovich
2007-04-27 11:23 ` Alex Dubov
2007-04-27 12:14 ` Sergey Yanovich
2007-04-27 16:55 ` Alex Dubov
2007-04-27 18:36 ` Sergey Yanovich
2007-04-28 8:10 ` Alex Dubov
2007-04-28 8:41 ` Sergey Yanovich
2007-04-28 9:08 ` Sergey Yanovich
2007-04-28 11:34 ` Pierre Ossman
2007-04-28 11:44 ` Alex Dubov
2007-04-28 17:07 ` Sergey Yanovich
2007-04-19 20:53 Sergey Yanovich
2007-04-19 22:56 ` Arnd Bergmann
2007-04-20 9:22 ` Sergey Yanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=204224.14405.qm@web36703.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=ynvich@gmail.com \
--subject='Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).