linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Jerome Forissier <jerome@forissier.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kernel v5.2+ on HiKey960?
Date: Thu, 5 Dec 2019 14:59:12 +0000	[thread overview]
Message-ID: <2e484bec-ca63-03f2-964a-542413e794c1@arm.com> (raw)
In-Reply-To: <40a0e25a-9752-7bca-da1c-51135582907d@forissier.org>

[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]

Hi Jerome,

>> Thank you for the instructions, I managed to successfully boot the latest
>> mainline tree on the Hikey960. Full log in attachment.
>> And even the poweroff sequence looks fine to me.
> 
> Nice.
> 
>> Could you please try to follow the following steps and verify that it works for
>> you as well?
>>
>> 1. Download op-tee version 3.7.0.
>> 2. Enter the linux directory and add the remote
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> 3. Rebase the 3.7.0 branch kernel of linux master.
>> 4. Build and Flash op-tee.
>>
>> It should boot and have no issues on init.
> 
> [Unfortunately, it doesn't work for me. The board still hangs (or
> rather, loops) on /init. I'm puzzled at this point... What could be
> wrong with my setup? Do we have different board revisions maybe?
> 

So my board is an Hikey960 ver.B and I am running the latest UEFI firmware.

Some useful links:

[1] https://snapshots.linaro.org/reference-platform/components/uefi-staging/
[2]
https://github.com/96boards-hikey/tools-images-hikey960/blob/master/README-flash-uefi.md

> ...]
> 
> Now that's embarrassing :-/ I decided to re-build everything once again,
> but *without ccache* this time. Guess what? Kernel v5.4 boots fine :-O
> and master too.
> > I used to trust ccache blindly, until I discovered a bug which has
> caused me some trouble for quite some time [1]. After upgrading I
> thought all would be good again, but apparently not... That is quite
> annoying! :-/
> 
> Would you recommend against using ccache for kernel development?
>

I never use ccache for kernel development.

> Anyway, thank you guys for your valuable help. I feel ashamed for
> wasting your time troubleshooting a non-bug... but at least it wasn't in
> vain.
>

Nothing to be embarrassed of, I am curious as well now to know what is going on
with your setup :)

> [1] https://github.com/ccache/ccache/issues/136
> 
>> What I noticed is that the optee
>> provided kernel is not a 5.1 but a 5.1 plus some patches.
> 
> True, but nothing really important. A vanilla kernel is supposed to work
> fine including most of the OP-TEE stuff (except for some very specific
> "secure data path" code which depends on the presence of a special ION
> heap).
> 

Ok, I thought it was worth mentioning.

> Thanks,
> 

-- 
Regards,
Vincenzo

[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 14291 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-12-05 14:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 15:43 Kernel v5.2+ on HiKey960? Jerome Forissier
2019-12-03 17:47 ` Marc Zyngier
2019-12-04  9:01   ` Jerome Forissier
2019-12-04 10:18     ` Marc Zyngier
2019-12-04 12:22       ` Jerome Forissier
2019-12-04 12:49   ` Vincenzo Frascino
2019-12-04 13:28     ` Jerome Forissier
2019-12-04 10:18 ` Catalin Marinas
2019-12-04 12:55   ` Vincenzo Frascino
2019-12-04 14:03     ` Jerome Forissier
2019-12-05 12:04       ` Vincenzo Frascino
2019-12-05 14:48         ` Jerome Forissier
2019-12-05 14:59           ` Vincenzo Frascino [this message]
2019-12-04 13:15   ` Jerome Forissier
2019-12-04 14:28     ` Catalin Marinas
2019-12-04 14:58       ` Jerome Forissier
2019-12-04 17:57         ` Will Deacon
2019-12-05  7:26           ` Jerome Forissier
2019-12-05  8:57             ` Will Deacon
2019-12-05 14:54               ` Jerome Forissier
2019-12-06 16:09                 ` Will Deacon
2019-12-10 16:20                   ` Jerome Forissier
2019-12-10 16:26                     ` Vincenzo Frascino
2019-12-11  8:57                       ` Jerome Forissier

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=2e484bec-ca63-03f2-964a-542413e794c1@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=jerome@forissier.org \
    --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).