From: CaT <cat@zip.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: promise controller resource alloc problems with ~2.6.8
Date: Tue, 12 Oct 2004 22:52:02 +1000 [thread overview]
Message-ID: <20041012125202.GA920@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0410100955120.3897@ppc970.osdl.org>
On Sun, Oct 10, 2004 at 10:00:32AM -0700, Linus Torvalds wrote:
> which has a "insert_resource()" in it. That "insert_resource()" should be
> a "request_resource()" (and for you it won't matter, but other people will
> likely want to additionally apply Shaohua's patch to put in ACPI resources
> last).
>
> Hope this clears it all up. Knock wood.
Well with all the fun and the mind bendiness of the results of my
earlier tests I thought that there might be a slim chance that something
got buggered up with the lifetime of patching that particular kernel
tree got on my system and since rc4 was out I decided to start afresh.
I untarred 2.6.5, patched to 2.6.9-rc4, turned on the PCI debugging as
per request, compiled and rebooted. End result?
PDC20267: IDE controller at PCI slot 0000:00:0d.0
IRQ for 0000:00:0d.0:0 -> PIRQ 60, mask 0ef8, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:0d.0
PDC20267: chipset revision 2
PDC20267: 100% native mode on irq 11
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x1080-0x1087, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x1088-0x108f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: IC35L060AVV207-0, ATA DISK drive
ide2 at 0x10f0-0x10f7,0x1802 on irq 11
Probing IDE interface ide3...
hdh: ST3200822A, ATA DISK drive
ide3 at 0x10f8-0x10ff,0x1806 on irq 11
It worked!
Now thinking that I may have just right royally buggered up I compiled
rc3 again, starting from a totally fresh tree like I did with rc4 and
the problem was still there. No promise card. (phew... kinda)
So basically, something got fixed between rc3 and rc4. Personally, I
call shenanigans.
--
Red herrings strewn hither and yon.
next prev parent reply other threads:[~2004-10-12 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 5:28 promise controller resource alloc problems with ~2.6.8 Li, Shaohua
2004-10-10 17:00 ` Linus Torvalds
2004-10-12 12:52 ` CaT [this message]
2004-10-12 16:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-09-27 8:45 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
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
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=20041012125202.GA920@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.