From: Philip Langdale <philipl@overt.org>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, sdhci-devel@list.drzeus.cx,
drzeus@drzeus.cx, fseidel@suse.de, weyland@library.ethz.ch,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] ricoh_mmc: Handle newer models of Ricoh controllers
Date: Wed, 26 Nov 2008 06:42:20 -0800 [thread overview]
Message-ID: <492D604C.10707@overt.org> (raw)
In-Reply-To: <200811261436.57946.elendil@planet.nl>
Frans Pop wrote:
>> The latest generation of laptops are shipping with a newer
>> model of Ricoh chip where the firewire controller is the
>> primary PCI function but a cardbus controller is also present.
>
> Note that the current separate ricoh_mmc disabling module approach has
> been shown to break during suspend/resume. Matthew Garret proposed a
> patch for that which (with minor fixups) I tested successfully.
Hmm. Well, I'm interested as to what Pierre thinks. He explicitly didn't
want a quirk when we originally looked at the problem and that's why
ricoh_mmc exists - but maybe this is a good enough reason to revisit that
decision.
--phil
next prev parent reply other threads:[~2008-11-26 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 8:42 [PATCH] ricoh_mmc: Handle newer models of Ricoh controllers Philip Langdale
2008-11-25 9:27 ` Mathias Weyland
2008-11-25 10:45 ` Pierre Ossman
2008-11-26 15:22 ` Frank Seidel
2008-11-26 13:36 ` Frans Pop
2008-11-26 14:42 ` Philip Langdale [this message]
2008-11-26 14:45 ` Pierre Ossman
2008-11-26 14:50 ` Matthew Garrett
2008-11-26 14:53 ` Philip Langdale
2008-11-26 15:12 ` Pierre Ossman
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=492D604C.10707@overt.org \
--to=philipl@overt.org \
--cc=drzeus@drzeus.cx \
--cc=elendil@planet.nl \
--cc=fseidel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=sdhci-devel@list.drzeus.cx \
--cc=weyland@library.ethz.ch \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.