public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Greg Felix <gregfelixlkml@gmail.com>
Cc: linux-kernel@vger.kernel.org, John Linville <linville@redhat.com>
Subject: Re: PROBLEM: ICH7 SATA drive not detected.
Date: Wed, 30 Mar 2005 14:33:32 -0500	[thread overview]
Message-ID: <424AFF0C.4010409@pobox.com> (raw)
In-Reply-To: <e16ac85e05022517024beb5b38@mail.gmail.com>

Greg Felix wrote:
> 00:1f.2 Class 0101: 8086:27c0 (prog-if 8f [Master SecP SecO PriP PriO])
>         Subsystem: 103c:3011
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium
> 
>>TAbort- <TAbort- <MAbort- >SERR- <PERR-
> 
>         Latency: 0
>         Interrupt: pin B routed to IRQ 5
>         Region 0: I/O ports at 10d8 [size=8]
>         Region 1: I/O ports at 10f0 [size=4]
>         Region 2: I/O ports at 10e0 [size=8]
>         Region 3: I/O ports at 10f4 [size=4]
>         Region 4: I/O ports at 10b0 [size=16]
>         Region 5: Memory at e04c4400 (32-bit, non-prefetchable)
> [disabled] [size=1K]


I was hoping that we could detect when this PCI BAR is disabled, and 
base the logic on that.  But it appears that's not feasible for some BIOSen.

I suppose your patch is the best we can do.

	Jeff



      parent reply	other threads:[~2005-03-30 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 23:36 Intel ICH7 SATA support question for ATA_PIIX Greg Felix
2005-02-26  0:00 ` Jeff Garzik
2005-02-26  1:02   ` PROBLEM: ICH7 SATA drive not detected Greg Felix
2005-02-26  1:05     ` Greg Felix
2005-02-26  4:35     ` Jeff Garzik
2005-02-28 17:22       ` Greg Felix
2005-03-30 19:33     ` Jeff Garzik [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=424AFF0C.4010409@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=gregfelixlkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox