linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Failed to boot ARM64 boards for recent linux-next
Date: Wed, 21 Mar 2018 09:33:03 +0000	[thread overview]
Message-ID: <de4be2ef-ee2c-60f8-a08e-11e378e55343@arm.com> (raw)
In-Reply-To: <5AB22377.1000404@rock-chips.com>

On 21/03/18 09:18, JeffyChen wrote:
> Hi Marc,
> 
> On 03/21/2018 04:52 PM, Marc Zyngier wrote:
>> Hi Jeffy,
>>
>> On 21/03/18 06:10, JeffyChen wrote:
>>> Hi Shawn,
>>>
>>> On 03/21/2018 08:34 AM, Shawn Lin wrote:
>>>>
>>>> @Jeffy
>>>>
>>>> Could you help test Marc's latest patch on your RK3399 kevin/Gru or
>>>> whatever Chromebook?
>>> tested on my chromebook kevin, it works with that patch.
>>
>> This is very odd. It completely fails on mine, which is aannoying.
>> Do you have any special firmware? Or the stock firmware?
>>
> 
> hmmm, my kevin's firmware is official:
> localhost / # cat /var/log/bios_info.txt
> version              | Google_Kevin.8785.241.0
> ro bios version      | Google_Kevin.8785.241.0

(booting into ChromeOS) Definitely not what I have on mine:
8785.220.0 as the runtime version, and 8785.94.7 as the RO one.

This is a retail machine, bought in November. So what you have cannot be
the stock firmware.

What changes related to the GIC have been applied to this FW?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2018-03-21  9:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  8:48 Failed to boot ARM64 boards for recent linux-next Shawn Lin
2018-03-20  9:01 ` Marc Zyngier
2018-03-20  9:32   ` Shawn Lin
2018-03-20  9:39     ` Shawn Lin
2018-03-20 10:13       ` JeffyChen
2018-03-20 13:34         ` Marc Zyngier
2018-03-20 15:52           ` John Garry
2018-03-20 16:06             ` Marc Zyngier
2018-03-20 16:52               ` John Garry
2018-03-20 17:00                 ` Marc Zyngier
2018-03-21  0:34                   ` Shawn Lin
2018-03-21  6:10                     ` JeffyChen
2018-03-21  8:52                       ` Marc Zyngier
2018-03-21  9:18                         ` JeffyChen
2018-03-21  9:33                           ` Marc Zyngier [this message]
2018-03-21 12:04                             ` JeffyChen
2018-03-21 12:20                               ` Marc Zyngier
2018-03-20 10:33       ` Marc Zyngier
2018-03-20  9:56     ` Marc Zyngier
2018-03-20 10:06       ` Shawn Lin
2018-03-20 12:43         ` Marc Zyngier

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=de4be2ef-ee2c-60f8-a08e-11e378e55343@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).