From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: benh@kernel.crashing.org
Cc: Ralf Baechle <ralf@linux-mips.org>,
Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: Please revert: PCI: fix IDE legacy mode resources
Date: Sun, 9 Dec 2007 22:23:35 +0000 [thread overview]
Message-ID: <20071209222335.70e52be3@the-village.bc.nu> (raw)
In-Reply-To: <1197230609.6563.6.camel@pasglop>
> Quite possibly, though as I said in practice, what we did so far
> happened to "just work" on pretty much everything we were faced with
> (which iirc is basically winbond and VIA controllers, possibly a few
> others).
>
> Anyway, I'll scrub around. Again, I'm not saying the approach is wrong
> in the generic code.
I think the generic code is right, up to the MIPS stuff. What the MIPS
stuff is doing wants looking at further. If it simply can't address
legacy ports them it should set
CONFIG_NO_ATA_LEGACY
and be robust to such resource mappings. The CONFIG option tells libata
to skip over controllers in legacy mode.
For switching quirks you should be fixing the class code in an early
fixup. The early fixups are run before we do the BAR processing. You must
however remember to update dev->class as well as the PCI register if you
do so.
See quirk_svwkrs_csb5ide() for a correct worked example going in the
other direction. If you follow that for the PPC quirks but going native
then you will get desired results, although you want to check/know the BAR
resources are sane, or clear them as part of the process.
So in summary:
- MIPS resource/bar bit may be wrong - if so lets revert that
- Rest of the logic is just fine, but you may need to move your
quirks to be 'early' ones.
Alan
next prev parent reply other threads:[~2007-12-09 22:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710122305.l9CN5tFI008240@hera.kernel.org>
2007-12-06 0:10 ` Benjamin Herrenschmidt
2007-12-06 4:34 ` Yoichi Yuasa
2007-12-06 5:04 ` Benjamin Herrenschmidt
2007-12-06 5:58 ` Yoichi Yuasa
2007-12-06 6:24 ` Benjamin Herrenschmidt
2007-12-09 2:12 ` Ralf Baechle
2007-12-09 7:24 ` Benjamin Herrenschmidt
2007-12-09 9:49 ` Benjamin Herrenschmidt
2007-12-09 12:46 ` Bartlomiej Zolnierkiewicz
2007-12-09 13:39 ` Alan Cox
2007-12-09 20:11 ` Benjamin Herrenschmidt
2007-12-09 13:38 ` Alan Cox
2007-12-09 20:03 ` Benjamin Herrenschmidt
2007-12-09 22:23 ` Alan Cox [this message]
2007-12-09 22:47 ` Benjamin Herrenschmidt
2007-12-10 4:29 ` Benjamin Herrenschmidt
2007-12-10 11:20 ` Alan Cox
2007-12-10 13:40 ` Ralf Baechle
2007-12-10 15:01 ` Alan Cox
2007-12-10 15:47 ` Ralf Baechle
2007-12-10 20:43 ` Benjamin Herrenschmidt
2007-12-11 0:05 ` Ralf Baechle
2007-12-11 0:27 ` Benjamin Herrenschmidt
2007-12-11 12:13 ` Ralf Baechle
2007-12-10 20:39 ` Benjamin Herrenschmidt
2007-12-10 23:07 ` Alan Cox
2007-12-11 0:10 ` Benjamin Herrenschmidt
2007-12-10 13:38 ` Ralf Baechle
2007-12-10 13:26 ` Ralf Baechle
2007-12-06 12:32 ` Ralf Baechle
2007-12-06 15:24 ` Ralf Baechle
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=20071209222335.70e52be3@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=bzolnier@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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
all inboxes | Powered by JetHome®