From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM Versatile multi-platform support
Date: Thu, 10 Dec 2015 17:30:29 +0000 [thread overview]
Message-ID: <5669B6B5.9030101@arm.com> (raw)
In-Reply-To: <CAL_JsqJXDAopCPLDx=6BAVfZdkwX+VihNKoL5Grs9amJe-HUGA@mail.gmail.com>
On 10/12/15 17:23, Rob Herring wrote:
> On Thu, Dec 10, 2015 at 10:59 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> On 08/12/15 21:11, Peter Maydell wrote:
>>> On 8 December 2015 at 20:44, Rob Herring <robh@kernel.org> wrote:
>>>> Arnd lit a fire under me to dust this off and get it merged. So here it
>>>> is. The main change from prior version is I merged all the code to a
>>>> single file. It's a bigger patch than I'd like, but I don't think trying
>>>> to do it in multiple steps is worth it.
>>>>
>>>> This is dependent on some solution for the default platform choice on
>>>> !MMU builds (allnoconfig) as it can't be Versatile after this series.
>>>> Arnd has some ideas on how to address that.
>>>>
>>>> This is tested under QEMU. Linus previously tested this on actual h/w
>>>> and had a problem with the display identification which needs
>>>> investigation or agreement to worry about it if and when someone
>>>> actually cares.
>>>
>>> I handed my PB hardware and its PCI backplane back to Will
>>> and Marc some time back, so they're in the best position to
>>> do testing of the PCI part on real hardware if needed these days.
>>
>> I don't really have the bandwidth to test that stuff right now, but I
>> recently managed to score a few PCI backplanes (backplane only, without
>> the massive case, so an ATX power supply is required to make use of it).
>> Some documentation is available at [1].
>>
>> I could easily be convinced to part with one of them, and even drop it
>> at a suitably located Linaro office, if that helps...
>
> How about in a canal? That will cut the install base in half. ;)
I believe Will would object to fishing the backplane out of the canal
instead of a trout.
> We'll settle for an ack meaning "I don't have time to test, working
> for qemu is good enough, we should merge this anyway and can pick up
> the pieces later if any of the 2 or 3 people that have a system ever
> really care."
Works for me:
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-12-10 17:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:44 [PATCH 0/4] ARM Versatile multi-platform support Rob Herring
2015-12-08 20:44 ` [PATCH 1/4] ARM: versatile: add DT based PCI detection Rob Herring
2015-12-08 20:44 ` [PATCH 2/4] ARM: versatile: switch to DT only booting and remove legacy code Rob Herring
2015-12-08 20:44 ` [PATCH 3/4] ARM: versatile: merge mach code into a single file Rob Herring
2015-12-08 20:44 ` [PATCH 4/4] ARM: versatile: convert to multi-platform Rob Herring
2015-12-08 21:11 ` [PATCH 0/4] ARM Versatile multi-platform support Peter Maydell
2015-12-10 16:59 ` Marc Zyngier
2015-12-10 17:23 ` Rob Herring
2015-12-10 17:30 ` Marc Zyngier [this message]
2015-12-15 22:57 ` Arnd Bergmann
2015-12-17 14:53 ` Rob Herring
2015-12-17 16:55 ` Arnd Bergmann
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=5669B6B5.9030101@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).