From: CaT <cat@zip.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: promise controller resource alloc problems with ~2.6.8
Date: Sat, 2 Oct 2004 14:57:25 +1000 [thread overview]
Message-ID: <20041002045725.GC1049@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0410010731560.2403@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
On Fri, Oct 01, 2004 at 07:34:34AM -0700, Linus Torvalds wrote:
> > BTW. I just realised (and I apologise for not doing so earlier) that I'm
> > not using ACPI on this box.
>
> For you, the bigger patch shouldn't have made any difference. But it's
> needed for some other people who have BIOS'es that mark PCI regions as
> being reserved for the motherboard, and they get resource conflicts
> otherwise (resource conflicts that largely go away with
> "insert_resource()", but if we want to change that to "request_resource()"
> then that other patch is needed).
Aha.
> Can you send me your ioports from 2.6.9-rc3 _with_ the
> "request_resource()" change..
Diff says that the file is thesame as the one without patch+change
that doesn't work.
Attached none-the-less.
--
Red herrings strewn hither and yon.
[-- Attachment #2: ioports.2.6.9-rc3 --]
[-- Type: text/plain, Size: 737 bytes --]
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial
0376-0376 : ide1
0378-037a : parport0
037b-037f : parport0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
1000-107f : 0000:00:0e.0
1000-107f : 0000:00:0e.0
1080-10bf : 0000:00:0d.0
10a0-10af : 0000:00:14.1
10a0-10a7 : ide0
10a8-10af : ide1
10c0-10df : 0000:00:14.2
10f0-10f7 : 0000:00:0d.0
10f8-10ff : 0000:00:0d.0
1400-14ff : 0000:00:0f.0
1400-14ff : tulip
1800-1803 : 0000:00:0d.0
1804-1807 : 0000:00:0d.0
f800-f83f : 0000:00:14.3
fc00-fc1f : 0000:00:14.3
next prev parent reply other threads:[~2004-10-02 4:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 8:45 promise controller resource alloc problems with ~2.6.8 CaT
2004-09-30 23:03 ` CaT
2004-09-30 23:21 ` Linus Torvalds
2004-09-30 23:30 ` CaT
2004-09-30 23:56 ` Linus Torvalds
2004-10-01 0:14 ` Greg KH
2004-10-01 1:23 ` CaT
2004-10-01 10:30 ` CaT
2004-10-01 14:34 ` Linus Torvalds
2004-10-02 4:57 ` CaT [this message]
2004-10-02 19:17 ` Linus Torvalds
2004-10-10 2:19 ` CaT
2004-10-10 3:15 ` Linus Torvalds
2004-10-10 3:30 ` Linus Torvalds
2004-10-10 4:51 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 5:28 Li, Shaohua
2004-10-10 17:00 ` Linus Torvalds
2004-10-12 12:52 ` CaT
2004-10-12 16:03 ` Greg KH
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=20041002045725.GC1049@zip.com.au \
--to=cat@zip.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@osdl.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 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.