From: Alan Cox <alan@linux.intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linux-kernel@vger.kernel.org, linux-pcmica@lists.infradead.org
Subject: Re: [PATCH 5/5] pcmcia: add a new resource manager for non ISA systems
Date: Mon, 01 Jun 2015 14:59:29 +0100 [thread overview]
Message-ID: <1433167169.13900.140.camel@linux.intel.com> (raw)
In-Reply-To: <20150530144055.GA10043@light.dominikbrodowski.net>
On Sat, 2015-05-30 at 16:40 +0200, Dominik Brodowski wrote:
> Alan,
>
> On Thu, Dec 04, 2014 at 09:31:22PM +0000, Alan Cox wrote:
> > On a pure PCI platform we don't actually need all the complexity of the
> > rsrc_nonstatic manager, in fact we can just work directly with the pci
> > allocators and avoid all the complexity (and code bloat).
>
> I know you're re-working this thing by now, but still:
It's on the todo list to finish debugging
> Can we be certain that BIOS, ACPI etc. properly report all io resources
> which must not be utilized by other devices? Does this really depend on ISA
No you can't. However there appears to be a convention that for mmio the
windows are aligned on largish boundaries and vendors only hide hardware
so that it's next to existing resources on an alignment such that it
won't get allocated.
I've no idea if it's in a spec anywhere or that's just a "Hey it works
in Windows" bit of history.
> being set in Kconfig? Should this also be enabled for CardBus bridges on the
> root PCI bus? And: could doing a check for X86 like in rsrc_nonstatic.c
> ( avoid anything < 0x100 for ioports ) help to avoid some of the possible
> fallout?
Probably yes.
Added to the TODO list for it.
Alan
prev parent reply other threads:[~2015-06-01 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:28 [PATCH 0/5] pcmcia: 64bit fixes, anonymous cards, other bugs Alan Cox
2014-12-04 21:28 ` [PATCH 1/5] pcmcia: correct types Alan Cox
2014-12-04 21:29 ` [PATCH 2/5] pcmcia cis: on an out of range CIS read return 0xff, don't just warn Alan Cox
2014-12-04 21:30 ` [PATCH 3/5] pcmcia: Fix requery Alan Cox
2014-12-04 21:30 ` [PATCH 4/5] pcmcia: handle anonymous cards by generating a fake CIS Alan Cox
2015-06-14 19:52 ` Dominik Brodowski
2015-06-15 12:10 ` Alan Cox
2015-06-16 6:19 ` Dominik Brodowski
2014-12-04 21:31 ` [PATCH 5/5] pcmcia: add a new resource manager for non ISA systems Alan Cox
2015-05-30 14:40 ` Dominik Brodowski
2015-06-01 13:59 ` Alan Cox [this message]
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=1433167169.13900.140.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmica@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
/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