From: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.75-bk update help texts for PDC202 (was [PATCH] Update COnfigure.help for PDC202 options)
Date: Sat, 12 Jul 2003 17:48:20 +0100 [thread overview]
Message-ID: <200307121748.20148.ruth@ivimey.org> (raw)
In-Reply-To: <Pine.SOL.4.30.0307121706520.19333-100000@mion.elka.pw.edu.pl>
On Saturday 12 Jul 2003 4:18 pm, Bartlomiej Zolnierkiewicz wrote:
> > - integrate that patch with mine & resubmit
> Please do.
Ok. I will carry on. In my reply to the thread you pointed me to, I have
proposed some other choices.
> > Does ataraid work well on 2.4? I have never used it as I have preferred
> > the user-space tools available for Linux-raid. On 2.5 KConfig as ataraid
> > doesn't
> I do not know. Hint: search lkml archive for bugreports :-).
The answer seems to be that people are happy with ataraid in 2.4, apart from
Promise who would prefer it didn't exist :-)
> > work I guess the right thing is to always configure as non-raid, so not
> > requiring a user-question and therefore no help.
> Promise binary drivers can be used in 2.5.
Ahh.
> > I have updated my Configure.help patch in ways that I hope address your
> > concerns above. I can see from Steven Drake's patch that I should also
> > modify
>
> You don't. This patch looks (almost?) exactly as previous one.
It wasn't. This is what it looks like without 'diff' stuff around it. I have
removed refs to Ultra33 in the new bit, and rewritten the main paras in both.
However, as I said I did an alternative version in the other mail that you
might prefer. However that didn't actually have as much information in it
(e.g. stuff about using DMA by default, BIOS version problems):
PROMISE PDC20246/PDC20262/PDC20263/PDC20265/PDC20267 support
CONFIG_BLK_DEV_PDC202XX_OLD
Promise Ultra 33 [PDC20246]
Promise Ultra 66 [PDC20262]
Promise FastTrak 66 [PDC20263]
Promise MB Ultra 100 [PDC20265]
Promise Ultra 100 [PDC20267]
This driver adds support for the older series of Promise EIDE disk
interface devices. Each device supports up to 4 disk drives that
can use UDMA disk access (33MHz for Ultra 33 up to 100MHz for Ultra
100).
If multiple cards are installed you might have problems booting if
the BIOS versions for the cards are different. Therefore the driver
attempts to do dynamic tuning of the chipset at boot-time.
If you are using an Ultra 33, BIOS version 1.25 or newer is required
to support more than one card and you should say Y to "Special UDMA
Feature" to force UDMA mode for connected UDMA capable disk drives.
If you say Y here, you need to say Y to "Use DMA by default when
available" as well.
If unsure, say N.
PROMISE PDC202{68|69|70|71|75|76|77} support
CONFIG_BLK_DEV_PDC202XX_NEW
Promise Ultra 100 TX2 [PDC20268]
Promise Ultra 133 PTX2 [PDC20269]
Promise FastTrak LP/TX2/TX4 [PDC20270]
Promise FastTrak TX2000 [PDC20271]
Promise MB Ultra 133 [PDC20275]
Promise MB FastTrak 133 [PDC20276]
Promise FastTrak 133 [PDC20277]
This driver adds support for the older series of Promise EIDE disk
interface devices. Each device supports up to 4 disk drives that
can use UDMA disk access (100MHz for Ultra 100 up to 133MHz for
Ultra 133).
If multiple cards are installed you might have problems booting if
the BIOS versions for the cards are different. Therefore the driver
attempts to do dynamic tuning of the chipset at boot-time.
If you say Y here, you need to say Y to "Use DMA by default when
available" as well.
If unsure, say N.
--
Engineer, Author and Webweaver
next prev parent reply other threads:[~2003-07-12 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 19:39 [PATCH] Update COnfigure.help for PDC202 options Ruth Ivimey-Cook
2003-07-11 20:49 ` [PATCH] 2.5.75-bk update help texts for PDC202 (was [PATCH] Update COnfigure.help for PDC202 options) Steven Cole
2003-07-12 0:00 ` Bartlomiej Zolnierkiewicz
2003-07-12 1:10 ` Ruth Ivimey-Cook
2003-07-12 15:18 ` Bartlomiej Zolnierkiewicz
2003-07-12 16:48 ` Ruth Ivimey-Cook [this message]
2003-07-12 0:11 ` Ruth Ivimey-Cook
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=200307121748.20148.ruth@ivimey.org \
--to=ruth.ivimey-cook@ivimey.org \
--cc=linux-kernel@vger.kernel.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 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®