public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: IDE probing IDE_MAX_HWIFS
Date: Sat, 25 Jun 2005 12:10:37 +0100	[thread overview]
Message-ID: <200506251210.37623.nick@linicks.net> (raw)

Hello everybody,

I am investigating the IDE probing at boot (i386), and wanted to find an easy 
way to pass the 'noprobe' command line to all the (non-existant) IDE 
interfaces at once(ish) rather than having 'ide2=noprobe ide3=noprobe 
ide4=noprobe...'

Now I have traced the code, I see that HWIFS is 6 or 10
include/asm-i386/ide.h:

#ifndef MAX_HWIFS
# ifdef CONFIG_BLK_DEV_IDEPCI
#define MAX_HWIFS       10
# else
#define MAX_HWIFS       6
# endif
#endif

Looking at the Kconfig, I see APLHA & SUPERH do get an option to change this 
to suit
drivers/ide/Kconfig

config IDE_MAX_HWIFS
        int "Max IDE interfaces"
        depends on ALPHA || SUPERH
        default 4
        help
          This is the maximum number of IDE hardware interfaces that will
          be supported by the driver. Make sure it is at least as high as
          the number of IDE interfaces in your system.

Now my question :-)  Is there a specific reason why this isn't included in 
other architectures?  I am asking as I guess one hell of a lot of people 
running on i386 have only two IDE interfaces anyway, and it could do with 
defining it as 2...

Thanks,

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

             reply	other threads:[~2005-06-25 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25 11:10 Nick Warne [this message]
2005-06-26 17:51 ` IDE probing IDE_MAX_HWIFS Alan Cox
2005-06-26 18:08   ` Nick Warne
2005-06-26 19:33     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-06-25 13:47 Nick Warne

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=200506251210.37623.nick@linicks.net \
    --to=nick@linicks.net \
    --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