From: Manfred Spraul <manfred@colorfullife.com>
To: "Alec H. Peterson" <ahp@hilander.com>
Cc: linux-kernel@vger.kernel.org, Dominik Brodowski <linux@brodo.de>,
netdev@oss.sgi.com
Subject: Re: PCI memory reservation failure - 2.4/2.6
Date: Sat, 15 May 2004 21:34:49 +0200 [thread overview]
Message-ID: <40A670D9.5010409@colorfullife.com> (raw)
In-Reply-To: <9C9F57570B19C8A682D96940@[192.168.0.100]>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
Alec H. Peterson wrote:
>
> A module parameter sounds like a grand idea. I'd be happy to take a
> stab at it if others feel it is the way to go.
There are two possible approaches:
- just a module parameter. Probably something for 2.4.
- a combination of a dmi detection of buggy bios versions plus a pci
quirk that resets start and end to 0.
Attached is the module parameter patch against 2.6. If it works I can
write a backport to 2.4 and try to convince Marcelo to merge it.
Could you send me the output of dmidecode? I'll try to write the
autodetection patch for 2.6.
--
Manfred
[-- Attachment #2: patch-yenta --]
[-- Type: text/plain, Size: 905 bytes --]
--- 2.6/drivers/pcmcia/yenta_socket.c 2004-05-15 11:21:38.000000000 +0200
+++ build-2.6/drivers/pcmcia/yenta_socket.c 2004-05-15 15:00:22.000000000 +0200
@@ -40,7 +40,7 @@
#define to_ns(cycles) ((cycles)*120)
static int yenta_probe_cb_irq(struct yenta_socket *socket);
-
+static int override_bios;
/*
* Generate easy-to-use ways of reading a cardbus sockets
@@ -548,7 +548,7 @@
start = config_readl(socket, offset) & mask;
end = config_readl(socket, offset+4) | ~mask;
- if (start && end > start) {
+ if (start && end > start && !override_bios) {
res->start = start;
res->end = end;
if (request_resource(root, res) == 0)
@@ -1105,6 +1105,8 @@
};
MODULE_DEVICE_TABLE(pci, yenta_table);
+MODULE_PARM (override_bios, "i");
+MODULE_PARM_DESC (override_bios, "yenta ignore bios resource allocation");
static struct pci_driver yenta_cardbus_driver = {
.name = "yenta_cardbus",
next prev parent reply other threads:[~2004-05-15 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 13:07 PCI memory reservation failure - 2.4/2.6 Alec H. Peterson
2004-05-12 21:07 ` Manfred Spraul
2004-05-12 21:35 ` Alec H. Peterson
2004-05-15 19:34 ` Manfred Spraul [this message]
2004-05-17 13:49 ` Alec H. Peterson
-- strict thread matches above, loose matches on Subject: below --
2004-05-08 14:30 Alec H. Peterson
[not found] ` <200405081542.39712.s0348365@sms.ed.ac.uk>
2004-05-08 14:50 ` Alec H. Peterson
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=40A670D9.5010409@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=ahp@hilander.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=netdev@oss.sgi.com \
/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.