linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: linux-ide@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 12/12] ide: mark "idebus=" kernel parameter as obsoleted
Date: Thu, 13 Mar 2008 23:45:07 +0100	[thread overview]
Message-ID: <20080313224507.7051.33673.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20080313224352.7051.44005.sendpatchset@localhost.localdomain>

We have per host driver "vlb|pci|cmd_clock=" parameters now.

Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
---
 Documentation/ide/ide.txt |   10 ----------
 drivers/ide/ide.c         |    2 +-
 2 files changed, 1 insertion(+), 11 deletions(-)

Index: b/Documentation/ide/ide.txt
===================================================================
--- a/Documentation/ide/ide.txt
+++ b/Documentation/ide/ide.txt
@@ -214,16 +214,6 @@ Summary of ide driver parameters for ker
 
  "hdx=nodma"		: disallow DMA
 
- "idebus=xx"		: inform IDE driver of VESA/PCI bus speed in MHz,
-			  where "xx" is between 20 and 66 inclusive,
-			  used when tuning chipset PIO modes.
-			  For PCI bus, 25 is correct for a P75 system,
-			  30 is correct for P90,P120,P180 systems,
-			  and 33 is used for P100,P133,P166 systems.
-			  If in doubt, use idebus=33 for PCI.
-			  As for VLB, it is safest to not specify it.
-			  Bigger values are safer than smaller ones.
-
  "ide=reverse"		: formerly called to pci sub-system, but now local.
 
 The following are valid ONLY on ide0, which usually corresponds
Index: b/drivers/ide/ide.c
===================================================================
--- a/drivers/ide/ide.c
+++ b/drivers/ide/ide.c
@@ -979,7 +979,7 @@ static int __init ide_setup(char *s)
 			idebus_parameter = vals[0];
 		} else
 			printk(" -- BAD BUS SPEED! Expected value from 20 to 66");
-		goto done;
+		goto obsolete_option;
 	}
 
 bad_option:

  parent reply	other threads:[~2008-03-13 22:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 22:43 [PATCH 1/12] ali14xx: add "vlb_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:43 ` [PATCH 2/12] ht6560b: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 3/12] qd65xx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 4/12] aec62xx: add "pci_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 5/12] alim15x3: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 6/12] amd74xx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 7/12] cmd64x: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 8/12] cy82c693: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 9/12] opti621: " Bartlomiej Zolnierkiewicz
2008-03-13 22:44 ` [PATCH 10/12] via82cxxx: " Bartlomiej Zolnierkiewicz
2008-03-13 22:45 ` [PATCH 11/12] cmd640: add "cmd_clock=" parameter Bartlomiej Zolnierkiewicz
2008-03-13 22:45 ` Bartlomiej Zolnierkiewicz [this message]
2008-03-15 12:36 ` [PATCH 1/12] ali14xx: add "vlb_clock=" parameter Alan Cox
2008-03-15 21:44   ` Bartlomiej Zolnierkiewicz

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=20080313224507.7051.33673.sendpatchset@localhost.localdomain \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).