public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Maxwell Spangler <maxwax@mindspring.com>
Cc: Meelis Roos <mroos@linux.ee>, linux-kernel@vger.kernel.org
Subject: Re: [COMMENTS IDE 2.5] - "idebus=66" in 2.5.8 results in "ide_setup: idebus=66 -- BAD OPTION"
Date: Tue, 16 Apr 2002 00:39:31 +0200	[thread overview]
Message-ID: <20020416003931.A31385@ucw.cz> (raw)
In-Reply-To: <E16xA96-0002Ru-00@roos.tartu-labor> <Pine.LNX.4.44.0204151804100.1145-100000@tyan.doghouse.com>

On Mon, Apr 15, 2002 at 06:04:54PM -0400, Maxwell Spangler wrote:
> On Mon, 15 Apr 2002, Meelis Roos wrote:
> 
> > MH> Kernel command line: BOOT_IMAGE=2.5.8-without-TCQ ro root=303 video=matrox:vesa:0x118 idebus=66 profile=2
> > MH> ide_setup: idebus=66
> > MH> ide: system bus speed 66MHz
> > 
> > MH> works like a charm :)
> > 
> > Do you really have an IDE controller that does 66 MHz PCI? What kind on IDE
> > controller is this?
> 
> I have a Promise Ultra133TX2 card on my shelf that is 32-bit PCI with 66Mhz 
> operation.
> 
> I don't know to what extent it is supported yet.. Andre?

The promise driver ignores the idebus= value anyway. :) And for others
66 is usually an invalid setting.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-04-15 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  9:23 [COMMENTS IDE 2.5] - "idebus=66" in 2.5.8 results in "ide_setup: idebus=66 -- BAD OPTION" Morten Helgesen
2002-04-15  8:25 ` Martin Dalecki
2002-04-15  9:34   ` Morten Helgesen
2002-04-15  9:40     ` Jens Axboe
2002-04-15 12:16   ` Morten Helgesen
2002-04-15 11:24     ` Martin Dalecki
2002-04-15 17:20     ` Meelis Roos
2002-04-15 22:04       ` Maxwell Spangler
2002-04-15 22:39         ` Vojtech Pavlik [this message]
2002-04-15 22:55         ` Andre Hedrick
2002-04-15 23:43           ` Maxwell Spangler

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=20020416003931.A31385@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxwax@mindspring.com \
    --cc=mroos@linux.ee \
    /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