From: kernel@ddx.a2000.nu
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: linux-kernel@vger.kernel.org, jonathan@explainerdc.com,
adam.johansson@madsci.se, ataraid-list@redhat.com,
dakota@dakotabcn.net, mast@lysator.liu.se,
alanmiles@hfx.eastlink.ca
Subject: Re: Promise 202XX: neither IDE port enabled
Date: Sat, 5 Apr 2003 11:43:07 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.53.0304051138110.31947@ddx.a2000.nu> (raw)
In-Reply-To: <3E8E48C2.60203@gmx.net>
On Sat, 5 Apr 2003, Carl-Daniel Hailfinger wrote:
> CONFIG_PDC202XX_FORCE=y
>
> "Special FastTrak Feature"
>
> and set it to Y.
this does work :
PDC20270: IDE controller at PCI slot 03:01.0
PDC20270: chipset revision 2
PDC20270: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0x9040-0x9047, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x9048-0x904f, BIOS settings: hdg:pio, hdh:pio
ide4: BM-DMA at 0x90c0-0x90c7, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0x90c8-0x90cf, BIOS settings: hdk:pio, hdl:pio
PDC20267: IDE controller at PCI slot 05:06.0
PCI: Found IRQ 11 for device 05:06.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER
Mode.
ide6: BM-DMA at 0xb800-0xb807, BIOS settings: hdm:pio, hdn:pio
ide7: BM-DMA at 0xb808-0xb80f, BIOS settings: hdo:pio, hdp:pio
wasn't the 'CONFIG_PDC202XX_FORCE' to enable fasttrak support istead of
using it like an Ultra controller ?
* Linux kernel will misunderstand FastTrak ATA-RAID series as Ultra
* IDE Controller, UNLESS you enable "CONFIG_PDC202XX_FORCE"
* That's you can use FastTrak ATA-RAID controllers as IDE controllers.
next prev parent reply other threads:[~2003-04-05 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 3:08 Carl-Daniel Hailfinger
2003-04-05 9:43 ` kernel [this message]
2003-04-05 11:02 ` Andre Hedrick
[not found] <200304051721.21663.markus.kossmann@inka.de>
2003-04-05 20:56 ` Andre Hedrick
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=Pine.LNX.4.53.0304051138110.31947@ddx.a2000.nu \
--to=kernel@ddx.a2000.nu \
--cc=adam.johansson@madsci.se \
--cc=alanmiles@hfx.eastlink.ca \
--cc=ataraid-list@redhat.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=dakota@dakotabcn.net \
--cc=jonathan@explainerdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mast@lysator.liu.se \
/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
all inboxes | Powered by JetHome®