From: JeffyChen <jeffy.chen@rock-chips.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
Shawn Lin <shawn.lin@rock-chips.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
John Garry <john.garry@huawei.com>,
Robin Murphy <robin.murphy@arm.com>,
Linuxarm <linuxarm@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Failed to boot ARM64 boards for recent linux-next
Date: Wed, 21 Mar 2018 17:18:47 +0800 [thread overview]
Message-ID: <5AB22377.1000404@rock-chips.com> (raw)
In-Reply-To: <680aba8d-4117-227b-d5a1-ad7121d2565f@arm.com>
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
and i also test it on my dru(another rk3399 chromebook) (force using
kevin's dtb), it works too(although it dead at the end after i2c probed).
my kernel:
a9be5aeb6a31 irqchip/gic-v3: Check availability of Group0 before
resetting AP0Rn
170b1830a3e7 Add linux-next specific files for 20180320
90385ca35f2f Merge branch 'akpm/master'
0a54b4dd1975 sparc64: NG4 memset 32 bits overflow
my kernel image and config:
https://emailattachment.net/sites/default/files/files/public/kernel.img
https://emailattachment.net/sites/default/files/files/public/config.config
> Thanks,
>
> M.
>
WARNING: multiple messages have this Message-ID (diff)
From: jeffy.chen@rock-chips.com (JeffyChen)
To: linux-arm-kernel@lists.infradead.org
Subject: Failed to boot ARM64 boards for recent linux-next
Date: Wed, 21 Mar 2018 17:18:47 +0800 [thread overview]
Message-ID: <5AB22377.1000404@rock-chips.com> (raw)
In-Reply-To: <680aba8d-4117-227b-d5a1-ad7121d2565f@arm.com>
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
and i also test it on my dru(another rk3399 chromebook) (force using
kevin's dtb), it works too(although it dead at the end after i2c probed).
my kernel:
a9be5aeb6a31 irqchip/gic-v3: Check availability of Group0 before
resetting AP0Rn
170b1830a3e7 Add linux-next specific files for 20180320
90385ca35f2f Merge branch 'akpm/master'
0a54b4dd1975 sparc64: NG4 memset 32 bits overflow
my kernel image and config:
https://emailattachment.net/sites/default/files/files/public/kernel.img
https://emailattachment.net/sites/default/files/files/public/config.config
> Thanks,
>
> M.
>
next prev parent reply other threads:[~2018-03-21 9:18 UTC|newest]
Thread overview: 42+ 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 8:48 ` Shawn Lin
2018-03-20 9:01 ` Marc Zyngier
2018-03-20 9:01 ` Marc Zyngier
[not found] ` <077cecdd-7982-dd33-454f-e38cc571366c-5wv7dgnIgG8@public.gmane.org>
2018-03-20 9:32 ` Shawn Lin
2018-03-20 9:32 ` Shawn Lin
2018-03-20 9:39 ` Shawn Lin
2018-03-20 9:39 ` Shawn Lin
2018-03-20 10:13 ` JeffyChen
2018-03-20 10:13 ` JeffyChen
2018-03-20 13:34 ` Marc Zyngier
2018-03-20 13:34 ` Marc Zyngier
2018-03-20 15:52 ` John Garry
2018-03-20 15:52 ` John Garry
[not found] ` <cbc89d68-ba41-1f6a-4ab2-4c9647b48f75-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-03-20 16:06 ` Marc Zyngier
2018-03-20 16:06 ` Marc Zyngier
2018-03-20 16:52 ` John Garry
2018-03-20 16:52 ` John Garry
2018-03-20 17:00 ` Marc Zyngier
2018-03-20 17:00 ` Marc Zyngier
2018-03-21 0:34 ` Shawn Lin
2018-03-21 0:34 ` Shawn Lin
2018-03-21 6:10 ` JeffyChen
2018-03-21 6:10 ` JeffyChen
2018-03-21 8:52 ` Marc Zyngier
2018-03-21 8:52 ` Marc Zyngier
2018-03-21 9:18 ` JeffyChen [this message]
2018-03-21 9:18 ` JeffyChen
2018-03-21 9:33 ` Marc Zyngier
2018-03-21 9:33 ` Marc Zyngier
2018-03-21 12:04 ` JeffyChen
2018-03-21 12:04 ` JeffyChen
2018-03-21 12:20 ` Marc Zyngier
2018-03-21 12:20 ` Marc Zyngier
2018-03-20 10:33 ` Marc Zyngier
2018-03-20 10:33 ` Marc Zyngier
2018-03-20 9:56 ` Marc Zyngier
2018-03-20 9:56 ` Marc Zyngier
2018-03-20 10:06 ` Shawn Lin
2018-03-20 10:06 ` Shawn Lin
2018-03-20 12:43 ` Marc Zyngier
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=5AB22377.1000404@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=robin.murphy@arm.com \
--cc=shawn.lin@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.