All of lore.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Sergei Shtylyov <sshtylyov@ru.mvista.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: Wed, 23 May 2007 16:53:56 -0500	[thread overview]
Message-ID: <20070523215356.GD5921@austin.ibm.com> (raw)
In-Reply-To: <4654A375.4080807@ru.mvista.com>

On Thu, May 24, 2007 at 12:26:29AM +0400, Sergei Shtylyov wrote:
> 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.

Right. I wrote "drive" in the first email, and then quickly
changed that :-)

>    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


OK, great, thanks!

I'll give this a spin. If it works, I'll suggest backporting it to the
stable branch 2.6.21.2. 

--linas


      reply	other threads:[~2007-05-23 21:54 UTC|newest]

Thread overview: 7+ 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:24   ` Alan Cox
2007-05-23 20:27   ` Sergei Shtylyov
2007-05-23 21:06   ` Chuck Ebbert
2007-05-23 20:26 ` Sergei Shtylyov
2007-05-23 21:53   ` Linas Vepstas [this message]

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=20070523215356.GD5921@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.