From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Michel Bouissou <michel@bouissou.net>
Cc: abrutschy@xylon.de, linux-kernel@vger.kernel.org
Subject: Re: Patch for Promise PDC20276
Date: Mon, 27 Oct 2003 10:49:32 +0100 [thread overview]
Message-ID: <200310271049.32819.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <200310271009.13054@totor.bouissou.net>
This was discussed few times before.
Just enable "Special FastTrak feature" (overriding BIOS) config option.
On Monday 27 of October 2003 10:09, Michel Bouissou wrote:
> Hi there,
>
> The patch that Arne Brutschy posted here (see
> http://www.cs.helsinki.fi/linux/linux-kernel/2003-22/0386.html) almost
> saved my life as it allowed me to understand why my 2.4.22 kernel didn't
> activate my Promise PDC20276 IDE controller properly.
>
> (For the record, my kernel was displaying the following message at boot:
> PDC20276: neither IDE port enabled (BIOS)
> )
>
> But this patch was only halfway satisfactory, as it enabled only one of my
> 2 controller channels.
>
> So I did a quick-and-dirty hack that gives the following patch, that allows
> activation of both channels of my PDC20276.
>
> This might help others encountering the same problem...
>
> ========== CUT HERE ==========
> --- drivers/ide/setup-pci.c.orig 2003-08-25 13:44:41.000000000 +0200
> +++ drivers/ide/setup-pci.c 2003-10-26 20:35:49.000000000 +0100
> @@ -577,7 +577,7 @@
> ata_index_t index;
> u8 tmp = 0;
> ide_hwif_t *hwif, *mate = NULL;
> - static int secondpdc = 0;
> +/* MiB static int secondpdc = 0; */
>
> index.all = 0xf0f0;
>
> @@ -637,10 +637,10 @@
> * by the bios for raid purposes.
> * Skip the normal "is it enabled" test for those.
> */
> - if (((d->vendor == PCI_VENDOR_ID_PROMISE) &&
> + if ((d->vendor == PCI_VENDOR_ID_PROMISE) &&
> ((d->device == PCI_DEVICE_ID_PROMISE_20262) ||
> - (d->device == PCI_DEVICE_ID_PROMISE_20265))) &&
> - (secondpdc++==1) && (port==1))
> + (d->device == PCI_DEVICE_ID_PROMISE_20265) ||
> + (d->device == PCI_DEVICE_ID_PROMISE_20276)))
> goto controller_ok;
>
> if (e->reg && (pci_read_config_byte(dev, e->reg, &tmp) ||
> ========== CUT HERE ==========
>
> Regards
next prev parent reply other threads:[~2003-10-27 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 9:09 Michel Bouissou
2003-10-27 9:49 ` Bartlomiej Zolnierkiewicz [this message]
2003-10-27 9:49 ` Michel Bouissou
2003-10-27 10:02 ` Bartlomiej Zolnierkiewicz
2003-10-27 12:50 ` Michel Bouissou
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=200310271049.32819.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=abrutschy@xylon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@bouissou.net \
/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®