All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: Elmar Stellnberger <estellnb@elstel.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Rajat Jain <rajatxjain@gmail.com>
Subject: [Bug 43192] ExpressCards are not recognized
Date: Mon, 3 Nov 2014 12:29:30 -0700	[thread overview]
Message-ID: <20141103192930.GA26548@google.com> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=43192

Elmar reported this bug over two years ago.  Anybody who's interested is
more than welcome to take a look at it.

> Whether I try to use ExpressCards on a system with native ExpressCard
> interface (Amilo Xi2550, AdapterNo: 07473DD) or with a PCMCIA to
> ExpressCard adapter (DeLock Card Adapter CardBus for E-Card) lspci does not
> recognize my ExpressCards (tried with DeLock and Transcend USB 3.0
> adapter). The only thing which is recognized is the PCMCIA to ExpressCard
> adapter, not the ExpressCards themselves.
> 
> # lspci | grep -i cardbus
> 00:0b.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
> 
> # diff lspci-n_adapter-only/transcend/delock.msg lspci-n_none.msg
> 17,18d16
> < 03:00.0 0c03: 1033:0035 (rev 44)
> < 03:00.1 0c03: 1033:00e0 (rev 05)

There are also other bugs languishing in the PCI bugzilla:

https://bugzilla.kernel.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&columnlist=assigned_to%2Cbug_status%2Ccf_kernel_version%2Cshort_short_desc&component=PCI&order=bug_id%20DESC

I try to mention new incoming bugs on linux-pci in the hope that somebody
will adopt them, but sometimes I forget.  Sometimes I can look at things
myself, but I don't have time to work on them all.

Bjorn

                 reply	other threads:[~2014-11-03 19:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141103192930.GA26548@google.com \
    --to=bhelgaas@google.com \
    --cc=estellnb@elstel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rajatxjain@gmail.com \
    --cc=yinghai@kernel.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 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.