From: Russell King <rmk@arm.linux.org.uk>
To: linux-pcmcia@infradead.org,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: PCMCIA PATCHES: rsrc_mgr.c
Date: Sun, 15 Jun 2003 16:47:16 +0100 [thread overview]
Message-ID: <20030615164716.C5417@flint.arm.linux.org.uk> (raw)
I have three patches which I'm intending pushing to Linus tonight. They
are:
http://patches.arm.linux.org.uk/pcmcia/pcmcia-20030615-1.diff
Remove the racy check_mem_resource() function. Instead, claim
the region while we check it, passing a resource structure to
the core validation functions.
http://patches.arm.linux.org.uk/pcmcia/pcmcia-20030615-2.diff
We must always allocate windows below 1MB when a socket driver indicates
that it does not have "page registers". Handle this case in rsrc_mgr.c
within find_mem_region rather than each use of find_mem_region().
http://patches.arm.linux.org.uk/pcmcia/pcmcia-20030615-3.diff
Turn the resource management on its head. Rather than using PCMCIA's
resource database as the primary object to allocate resources, use
Linux's standard resource allocation instead.
When we have a socket on a PCI bus, we always use the PCI resource
allocation functions rather than the kernels core resource allocation,
so that we can take account of any bridges.
The first two should be mostly harmless. The third patch needs greater
testing. Unfortunately, the PCI groundwork for this patch was recently
reversed, so I just can't be bothered to separate out that change again
from the other PCI changes I have. You basically need to make the
function non-static, add a declaration to include/linux/pci.h and
re-export it.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
reply other threads:[~2003-06-15 15:33 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=20030615164716.C5417@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@infradead.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).