From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, linux-ia64@vger.kernel.org,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] IDE: don't offer IDE_GENERIC on ia64
Date: Thu, 11 Aug 2005 23:07:30 +0000 [thread overview]
Message-ID: <200508111707.30861.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <42FBC985.4030602@pobox.com>
On Thursday 11 August 2005 3:56 pm, Jeff Garzik wrote:
> Jeff Garzik wrote:
> > 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
> > (rev 02) (prog-if 8a [Master SecP PriP])
> > Subsystem: Hewlett-Packard Company d530 CMT (DG746A)
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
> > ping- SERR- FastB2B-
> > Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
> > - <MAbort- >SERR- <PERR-
> > Latency: 0
> > Interrupt: pin A routed to IRQ 169
> > Region 0: I/O ports at <ignored>
> > Region 1: I/O ports at <ignored>
> > Region 2: I/O ports at <ignored>
> > Region 3: I/O ports at <ignored>
> > Region 4: I/O ports at 14c0 [size\x16]
> > Region 5: Memory at 40000000 (32-bit, non-prefetchable) [size=1K]
> >
> > Trust me, IDE on PCI is still quite weird.
>
> The above configuration also indicates that the IRQs for the PCI device
> are 14 and 15, _not_ 169.
You deduce this by the absence of SecO and PriO? I wonder if lspci
should be enhanced to notice this, too. I assume that the IRQ 169
doesn't correspond to anything in /proc/interrupts.
So the scenario in question (correct me if I'm wrong) is that we
have a PCI IDE device that is handed off in compatibility mode (and
may only work in that mode). In that case, the PCI *device* still
exists, so shouldn't the IDE PCI code claim that device, notice that
it's in compatibility mode, and use the legacy ports and IRQs if
necessary?
It seems like that all should work even if we don't have IDE_GENERIC.
next prev parent reply other threads:[~2005-08-11 23:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 20:24 [PATCH] IDE: don't offer IDE_GENERIC on ia64 Bjorn Helgaas
2005-08-11 20:34 ` Christoph Hellwig
2005-08-11 20:37 ` Bjorn Helgaas
2005-08-12 19:41 ` Jan Engelhardt
2005-08-16 10:02 ` Bartlomiej Zolnierkiewicz
2005-08-16 13:42 ` Alan Cox
2005-08-11 20:36 ` Jeff Garzik
2005-08-11 20:45 ` Bjorn Helgaas
2005-08-11 20:56 ` Jeff Garzik
2005-08-11 21:42 ` Bjorn Helgaas
2005-08-11 21:48 ` Jeff Garzik
2005-08-11 21:56 ` Jeff Garzik
2005-08-11 23:07 ` Bjorn Helgaas [this message]
2005-08-11 23:49 ` Jeff Garzik
2005-08-12 8:35 ` Alan Cox
2005-08-12 10:33 ` Maciej W. Rozycki
2005-08-11 23:01 ` Jack Steiner
2005-08-11 21:58 ` Luck, Tony
2005-08-11 22:03 ` Jeff Garzik
2005-08-11 23:08 ` Jack Steiner
2005-08-12 8:40 ` Alan Cox
2005-08-15 21:07 ` Bjorn Helgaas
2005-08-16 9:38 ` Bartlomiej Zolnierkiewicz
2005-08-16 9:54 ` Bartlomiej Zolnierkiewicz
2005-08-16 12:55 ` Alan Cox
2005-08-16 12:59 ` Bartlomiej Zolnierkiewicz
2005-08-16 13:40 ` Matthew Wilcox
2005-08-16 13:49 ` Bartlomiej Zolnierkiewicz
2005-08-16 19:16 ` Bjorn Helgaas
2005-08-16 19:59 ` Alan Cox
2005-08-16 20:42 ` Bartlomiej Zolnierkiewicz
2005-08-16 21:48 ` Alan Cox
2005-08-16 20:16 ` Bartlomiej Zolnierkiewicz
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=200508111707.30861.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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