From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: enable access to HT Host-Bridge on Maple
Date: Mon, 04 Jul 2011 16:46:52 +0400 [thread overview]
Message-ID: <4E11B63C.4090306@gmail.com> (raw)
In-Reply-To: <288B47E0-3869-486D-B753-62EFA1EEF66D@kernel.crashing.org>
Hello,
On 03.07.2011 01:50, Segher Boessenkool wrote:
>>>> +static int u3_ht_root_write_config(struct pci_controller *hose, u8
>>>> offset,
>>>> + int len, u32 val)
>>>> +{
>>>> + volatile void __iomem *addr;
>>>> +
>>>> + addr = hose->cfg_addr + ((offset & ~3) << 2) + (4 - len - (offset
>>>> & 3));
>>>> +
>>>> + if (offset >= PCI_BASE_ADDRESS_0 && offset < PCI_CAPABILITY_LIST)
>>>> + return PCIBIOS_SUCCESSFUL;
>>>
>>> This is a workaround for something; at the very least it needs a
>>> comment,
>>> but probably it shouldn't be here at all.
>>
>> I'll add a comment. Basically these registers are unimplemented on u3/u4
>> bridges and at least some kinds of access to them cause system freeze.
>> I'll try to check what triggers what this night.
>
> I don't think the hardware freezes, but probably Linux isn't happy when it
> tries to write to the non-existent BARs. Or something like that.
I've run several experiments. At least writing to the ROM_ADDRESS (0x30)
causes some kind of strange reboot (I see 'Error: Magic number in
message area NVRAM is not valid.') errors on the service console and
Linux consoles are silent. Writing to other BARs seem to cause no direct
effect (reg remains =0), but causes very strange behaviour during boot.
All PCI access cycles seem to return 0, strange DRAM ECC error pops up,
etc. I'd prefer to leave these register writes disabled, even if it's
the problem of some hardware revision (?).
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-07-04 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 14:17 [PATCH] powerpc: enable access to HT Host-Bridge on Maple Dmitry Eremin-Solenikov
2011-07-01 16:44 ` Segher Boessenkool
2011-07-01 19:11 ` Dmitry Eremin-Solenikov
2011-07-02 21:50 ` Segher Boessenkool
2011-07-03 23:31 ` Dmitry Eremin-Solenikov
2011-07-04 12:46 ` Dmitry Eremin-Solenikov [this message]
2011-07-07 22:48 ` Benjamin Herrenschmidt
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=4E11B63C.4090306@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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).