From: Gunther Mayer <gunther.mayer@gmx.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nick Evgeniev <nick@octet.spb.ru>, linux-kernel@vger.kernel.org
Subject: Re: linux 2.4.19-rc1 i845e workaround udma fix
Date: Sat, 29 Jun 2002 19:45:07 +0200 [thread overview]
Message-ID: <3D1DF223.C56731EF@gmx.net> (raw)
In-Reply-To: E17O821-0007we-00@the-village.bc.nu
Alan Cox wrote:
> Complain to your BIOS vendor
>
> A workaround for this BIOS flaw will be in the -ac tree in a week or so
Or try this patch today:
--- linux-2.4.19-rc1/arch/i386/kernel/pci-i386.c Sat Jun 29 20:39:05
2002
+++ linux/arch/i386/kernel/pci-i386.c Sat Jun 29 20:37:25 2002
@@ -314,8 +314,8 @@
for(idx=0; idx<6; idx++) {
r = &dev->resource[idx];
if (!r->start && r->end) {
- printk(KERN_ERR "PCI: Device %s not available because
of resource collisions\n", dev->slot_name);
- return -EINVAL;
+ printk(KERN_ERR "PCI: Device %s not available because
of resource collisions on idx=%d %x %x\n",
dev->slot_name,idx,r->start,r->end);
+ printk("Temporary Workaround for 845E/845G:
ignoring.\n");
}
if (r->flags & IORESOURCE_IO)
cmd |= PCI_COMMAND_IO;
This increases hdparm -t from 3MB/sec to 41MB/sec.
-
Gunther
next prev parent reply other threads:[~2002-06-29 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-29 1:54 linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work Nick Evgeniev
2002-06-29 2:32 ` Alan Cox
2002-06-29 17:45 ` Gunther Mayer [this message]
2002-06-29 19:59 ` linux 2.4.19-rc1 i845e workaround udma fix Andre Hedrick
2002-07-01 11:49 ` linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work Nick Evgeniev
2002-07-03 15:28 ` Dave Jones
2002-07-03 19:17 ` Andre Hedrick
2002-07-04 13:14 ` Nick Evgeniev
2002-07-06 0:25 ` Andre Hedrick
2002-07-06 12:41 ` Nick Evgeniev
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=3D1DF223.C56731EF@gmx.net \
--to=gunther.mayer@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@octet.spb.ru \
/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