From: Arvind Sankar <nivedita@alum.mit.edu>
To: Trevor Jacobs <trevor_jacobs@aol.com>
Cc: "Michael ." <keltoiboy@gmail.com>,
Arvind Sankar <nivedita@alum.mit.edu>,
Ulf Hansson <ulf.hansson@linaro.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kris Cleveland <tridentperfusion@yahoo.com>,
Jeff <bluerocksaddles@willitsonline.com>,
Morgan Klym <moklym@gmail.com>,
Philip Langdale <philipl@overt.org>,
Pierre Ossman <pierre@ossman.eu>,
Maxim Levitsky <maximlevitsky@gmail.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: PCI device function not being enumerated [Was: PCMCIA not working on Panasonic Toughbook CF-29]
Date: Tue, 25 Feb 2020 23:51:05 -0500 [thread overview]
Message-ID: <20200226045104.GA2191053@rani.riverdale.lan> (raw)
In-Reply-To: <6e9db1f6-60c4-872b-c7c8-96ee411aa3ca@aol.com>
On Tue, Feb 25, 2020 at 09:12:48PM -0600, Trevor Jacobs wrote:
> That's correct, I tested a bunch of the old distros including slackware,
> and 2.6.32 is where the problem began.
>
> Also, the Panasonic Toughbook CF-29s effected that we tested are the
> later marks, MK4 and MK5 for certain. The MK2 CF-29 worked just fine
> because it has different hardware supporting the PCMCIA slots. I have
> not tested a MK3 but suspect it would work ok as it also uses the older
> hardware.
>
> Thanks for your help guys!
> Trevor
>
Right, the distros probably all enabled MMC_RICOH_MMC earlier than
upstream. Can you test a custom kernel based off your distro kernel but
just disabling that config option? That's probably the easiest fix
currently, even though not ideal. Perhaps there should be a command line
option to disable specific pci quirks to make this easier.
An ideal fix is I feel hard, given this quirk is based on undocumented
config registers -- it worked on Dell machines (that's where the
original authors seem to have gotten their info from), perhaps they had
only one Cardbus slot, but the code ends up disabling your second
Cardbus slot instead of disabling the MMC controller.
next prev parent reply other threads:[~2020-02-26 4:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFjuqNihuEb4_5Lny5X7vA258c0ogemVg8pQ5Y_ANgOsqhSXhg@mail.gmail.com>
2019-10-29 17:02 ` PCI device function not being enumerated [Was: PCMCIA not working on Panasonic Toughbook CF-29] Bjorn Helgaas
2020-02-22 16:56 ` Bjorn Helgaas
2020-02-22 18:14 ` Michael .
2020-02-25 15:03 ` Ulf Hansson
2020-02-25 19:15 ` Bjorn Helgaas
2020-02-25 23:46 ` bluerocksaddles
2020-02-26 1:13 ` Arvind Sankar
2020-02-26 1:50 ` Michael .
2020-02-26 3:12 ` Trevor Jacobs
2020-02-26 4:51 ` Arvind Sankar [this message]
2020-02-26 5:20 ` Philip Langdale
2020-02-26 6:10 ` Michael .
2020-02-26 19:46 ` bluerocksaddles
2020-07-28 1:50 ` Michael .
2020-08-02 5:58 ` Michael .
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=20200226045104.GA2191053@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=bluerocksaddles@willitsonline.com \
--cc=helgaas@kernel.org \
--cc=keltoiboy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=maximlevitsky@gmail.com \
--cc=moklym@gmail.com \
--cc=philipl@overt.org \
--cc=pierre@ossman.eu \
--cc=trevor_jacobs@aol.com \
--cc=tridentperfusion@yahoo.com \
--cc=ulf.hansson@linaro.org \
/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 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).