From: Vojtech Pavlik <vojtech@suse.cz>
To: David Balazic <david.balazic@uni-mb.si>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ATA 100
Date: Thu, 19 Apr 2001 18:15:20 +0200 [thread overview]
Message-ID: <20010419181520.C1641@suse.cz> (raw)
In-Reply-To: <3ADEFA2B.2DCEAE41@uni-mb.si>
In-Reply-To: <3ADEFA2B.2DCEAE41@uni-mb.si>; from david.balazic@uni-mb.si on Thu, Apr 19, 2001 at 04:46:03PM +0200
On Thu, Apr 19, 2001 at 04:46:03PM +0200, David Balazic wrote:
> Vojtech Pavlik (vojtech@suse.cz) wrote :
>
> > On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
> >
> > > El Mié 18 Abr 2001 15:16, escribiste:
> > > > I don't know about other possible problems with the kernel, but you must
> > > > use an 80 wire IDE cable for UDMA66/100 to work.
> > > >
> > > > > -----------------------Primary IDE-------Secondary IDE------
> > > > > Cable Type: 40w 40w
> > >
> > >
> > > Strange thing. With previous version of kernel (2.4.1 I think), I
> > > haven't got this problem. May be a bios detection problem?
> > >
> > > Extract from /usr/src/linux/drivers/ide/via82cxxx..c:
> > >
> > > *
> > > * PIO 0-5, MWDMA 0-2, SWDMA 0-2 and UDMA 0-5
> > > *
> > > * (this includes UDMA33, 66 and 100) modes. UDMA66 and higher modes are
> > > * autoenabled only in case the BIOS has detected a 80 wire cable. To ignore
> > > * the BIOS data and assume the cable is present, use 'ide0=ata66' or
> > > * 'ide1=ata66' on the kernel command line.
> > > *
> > >
> > > I've tried with ide0=ata100, but this options doesn't work.
> >
> > Try ide0=ata66 instead. The option should have been named ide0=80wire,
> > but, well, "ata66" was chosen as the name, because that was it at the
> > time.
>
> Any chance of auto detecting this ?
None. It's different on each (pre-686b) VIA motherboard.
> I just hate when linux is relaying on the BIOS ...
We don't have any other chance here. Actually we'll have to rely on the
BIOS for even more in the next release of the driver to make it work on
all boards out there.
> BTW , why are there 666 CONFIG_.*IDE.*DMA.* switches ?
Ask Andre. :)
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-04-19 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 14:46 ATA 100 David Balazic
2001-04-19 16:15 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 14:50 David Balazic
2001-04-19 6:24 Nicholas Petreley
2001-04-19 6:01 Nicholas Petreley
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=20010419181520.C1641@suse.cz \
--to=vojtech@suse.cz \
--cc=david.balazic@uni-mb.si \
--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