From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Andries E. Brouwer" <Andries.Brouwer@cwi.nl>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ide boot failure 2.6.36/2.6.28 - 2.6.27 works
Date: Sat, 20 Nov 2010 13:04:01 +0000 [thread overview]
Message-ID: <20101120130401.59d8b8a1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20101120121121.GA30338@iq>
> The author of the regression knew that he was breaking some setups
> and cleared his conscience by adding a printk
> + printk(KERN_INFO DRV_NAME ": please use \"probe_mask=0x3f\" module "
> + "parameter for probing all legacy ISA IDE ports\n");
> at boot time. Of course this scrolls off the screen too quickly to read.
I pointed out at the time that this was totally bogus hackery, but
without result. On a PCI box however you should always have a matching
PCI driver, and if not you want to force ide-generic to bind to it in
almost all cases, so if its hitting a lot of people then something else
is wrong in the config choices of the distro
The libata driver tries to be a bit smarter, firstly by not leaking
random resources but also knows not to bind against ports mapped to PCI
devices, or to certain special cases (non PCI standard but PCI space
using) devices.
If you have a PCI ATA driver which is not handled by any of the libata
drivers and is not known by ata_generic then please let me know. I
think we have pretty much everything old, weird and wonderful covered in
libata.
Alan
next prev parent reply other threads:[~2010-11-20 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 3:28 Andries E. Brouwer
2010-11-20 7:45 ` Borislav Petkov
2010-11-20 12:11 ` Andries E. Brouwer
2010-11-20 13:04 ` Alan Cox [this message]
2010-11-21 1:29 ` Andries E. Brouwer
-- strict thread matches above, loose matches on Subject: below --
2010-11-20 2:15 Andries E. Brouwer
2010-11-20 2:59 ` Justin P. Mattock
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=20101120130401.59d8b8a1@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Andries.Brouwer@cwi.nl \
--cc=bp@alien8.de \
--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
all inboxes | Powered by JetHome®