linux-kernel - Re: PCIE-to-PCI bridge doesn't pass mem resources downstream [Re: yenta cardbus problem]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 27 Apr 2011 16:41:40 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Germán Sanchis <eaglecros@...il.com>
Cc:	Dominik Brodowski <linux@...inikbrodowski.net>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: PCIE-to-PCI bridge doesn't pass mem resources downstream [Re:
 yenta cardbus problem]

On Wed, Apr 27, 2011 at 4:07 PM, Germán Sanchis <eaglecros@...il.com> wrote:
> Hi!
> Well, that did work, so the sound card is being recognized now, and in fact
> I already managed to do a couple of successful sound tests.
> I am attaching the output of lspci -vvv after specifying pci=cbmemsize=8M,
> in case it helps you further... I am happy with my card working, but I don't
> know if this should be considered in future releases of the kernel.

Good, I'm glad the workaround works.

It sure seems like the kernel could be smarter about this.  After all,
we can (at least in principle) find out what devices are behind the
CardBus bridge and how much space they need.  Unfortunately, we don't
really have good support for dynamically rearranging things, so we
tend to request more space than we need in case the user later plugs
in another device.  It's a known problem and people are thinking about
it, but I'm afraid a complete solution is still a ways off.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/