linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: how to handle pata_via when controller not in fully-pci-native mode (two irqs?)
Date: Tue, 03 Jul 2007 13:32:12 +0100	[thread overview]
Message-ID: <468A41CC.6030203@genesi-usa.com> (raw)
In-Reply-To: <20070703131736.5ddc0b89@the-village.bc.nu>


Alan Cox wrote:
>> We can't make the controller TRULY legacy since there is not any good way
>> of mapping the IDE/BMDMA registers into the lower kilobyte or so of
>> memory - obviously PPC has no "io address space", it's all memory mapped,
>> so the lower kilobyte of "IO ports" is really the CPU zero page. It's not
>> a good idea to be poking around just there and we never intended that to work.
> 
> The right way to do this IMHO is still to use the PCI quirk side logic.
> Unfortunately to put your legacy ports at different I/O addresses you
> need changes which are still pending to the libata-sff code so that it
> stops using the hardcoded ATA_PRIMARY_FOO bits.

We can't move the IO ports. They're stuck in the PCI BAR.

All we can do is fix the IRQ steering in the "ISA bridge" to report a single
IRQ instead of two.

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

  reply	other threads:[~2007-07-03 12:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-23  0:26 how to handle pata_via when controller not in fully-pci-native mode (two irqs?) Matt Sealey
2007-06-23  4:23 ` Jeff Garzik
2007-06-23  9:33 ` Alan Cox
2007-06-23  9:33   ` Matt Sealey
2007-06-23  9:53     ` Alan Cox
2007-06-23 10:11       ` Matt Sealey
2007-07-03  7:33         ` Tejun Heo
2007-07-03  8:11           ` Matt Sealey
2007-07-03  9:21             ` Tejun Heo
2007-07-03 12:44               ` Matt Sealey
2007-07-03 12:17             ` Alan Cox
2007-07-03 12:32               ` Matt Sealey [this message]
2007-07-03 13:38                 ` Alan Cox
2007-07-03 13:41                   ` Matt Sealey
2007-07-03 13:53                     ` Jeff Garzik
2007-07-03 14:00                       ` Matt Sealey
2007-07-03 15:08                         ` Jeff Garzik
2007-07-03 13:53                     ` Alan Cox
2007-07-03 13:54                       ` Matt Sealey
2007-07-04  8:55                         ` Tejun Heo
2007-07-04 19:08                           ` Matt Sealey
2007-07-05  2:28                             ` Tejun Heo

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=468A41CC.6030203@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).