From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.21.1: ide-pci is not finding ide controller.
Date: Thu, 24 May 2007 00:26:29 +0400 [thread overview]
Message-ID: <4654A375.4080807@ru.mvista.com> (raw)
In-Reply-To: <20070523201118.GZ5921@austin.ibm.com>
Hello.
Linas Vepstas wrote:
> I've got a rather old x86 box that I'm booting 2.6.21.1 on;
> this kernel is not finding an ide controller on it.
> The motherboard has 4 ide controllers total; two olde-fashioned
> ones (PIIX4, using the original 40-pin IDE ribbon cable) and two
You should have said "channels". PIIX4 has only one IDE controller.
> "HighPoint HPT366" controllers, taking the 80-pin cable.
> BIOS allows the two olde-fashioned channels to be enabled
> or disabled; but the HPT seems to alaways be on (I could not
> find any BIOS entry to play with them.)
> A bit of debugging localized the symptoms to drivers/ide/setup-pci.c
> It seems that there was some recent ide-pci fix that changed/fixed
> the way that pci config space is read' this "fix" breaks my recognition
> of my controller.
Actually, it was a bug that I've introduced into drivers/ide/pci/hpt366.c
-- the patch has been already merged into 2.6.22-rc1:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fdb0d72be4decaade6cedb5012ddd679a4817b5f
MBR, Sergei
next prev parent reply other threads:[~2007-05-23 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 20:11 [BUG] 2.6.21.1: ide-pci is not finding ide controller Linas Vepstas
2007-05-23 20:24 ` Alan Cox
2007-05-23 20:27 ` Sergei Shtylyov
2007-05-23 21:06 ` Chuck Ebbert
2007-05-23 20:26 ` Sergei Shtylyov [this message]
2007-05-23 21:53 ` Linas Vepstas
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=4654A375.4080807@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linas@austin.ibm.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