All of lore.kernel.org
 help / color / mirror / Atom feed
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: defconfig'ed v4.13 does not boot on ThunderX
Date: Wed, 4 Oct 2017 15:02:59 +0100	[thread overview]
Message-ID: <db08ee33-5e54-5c9a-d265-14155b72b5ad@arm.com> (raw)
In-Reply-To: <20171004134414.GF23092@leverpostej>

On 04/10/17 14:44, Mark Rutland wrote:
> On Wed, Oct 04, 2017 at 02:38:58PM +0100, Robin Murphy wrote:
>> On 04/10/17 08:25, Itaru Kitayama wrote:
>>> Hi,
>>>
>>> defconfig'ed kernel v4.13 does not boot on ThunderX, leaving only
>>> messages below:
>>>
>>> EFI stub: Booting Linux Kernel...
>>> EFI stub: Using DTB from configuration table
>>> EFI stub: Exiting boot services and installing virtual address map...
>>>
>>> Our HW is by GIGABYTE, the model is R150 T62 rev 100:
>>>
>>> http://b2b.gigabyte.com/ARM-Server/R150-T62-rev-100#ov
>>>
>>> The BIOS we're on is T43. Has anyone testing upstream kernels seen a
>>> similar issue like this?
>>
>> FWIW defconfig does *not* enable most of the ThunderX drivers (most
>> importantly, PCI and networking will be missing).
> 
> .... it's a bit worrying if earlycon doesn't work without those, though.
> It shouldn't be dependendent on either. :/

Well, my earlycon was fine too, but that was an a different board with
different firmware, so who knows...

>> I've just built the v4.13 tag with the appropriate drivers added and
>> booted it on a different ThunderX box - the net core throws some
>> warnings from __dev_xdp_attached() but it gets to userspace OK for me.
> 
> Given these seem to exist out in the field, we should probably enable
> those drivers in defconfig.

True, I think the below ought to suffice - arm-soc take defconfig
patches now, right?

Robin.

----->8-----
From: Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH] arm64: Add ThunderX drivers to defconfig

ThunderX needs its PCI host drivers to do anything useful, and it's
probably helpful to have networking by default too.

Signed-off-by: Robin Murphy <robin.murphy@arm.com>
---
 arch/arm64/configs/defconfig | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 34480e9af2e7..1c8e0d77deee 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -76,6 +76,8 @@ CONFIG_PCIE_RCAR=y
 CONFIG_PCIE_ROCKCHIP=m
 CONFIG_PCI_HOST_GENERIC=y
 CONFIG_PCI_XGENE=y
+CONFIG_PCI_HOST_THUNDER_PEM=y
+CONFIG_PCI_HOST_THUNDER_ECAM=y
 CONFIG_ARM64_VA_BITS_48=y
 CONFIG_SCHED_MC=y
 CONFIG_NUMA=y
@@ -188,6 +190,7 @@ CONFIG_VIRTIO_NET=y
 CONFIG_AMD_XGBE=y
 CONFIG_NET_XGENE=y
 CONFIG_MACB=y
+CONFIG_THUNDER_NIC_PF=y
 CONFIG_HNS_DSAF=y
 CONFIG_HNS_ENET=y
 CONFIG_E1000E=y
-- 
2.13.4.dirty

  reply	other threads:[~2017-10-04 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  7:25 defconfig'ed v4.13 does not boot on ThunderX Itaru Kitayama
2017-10-04 10:08 ` Mark Rutland
2017-10-04 12:49   ` Itaru Kitayama
2017-10-04 12:53     ` Ard Biesheuvel
2017-10-04 13:00       ` Itaru Kitayama
2017-10-04 13:12       ` Itaru Kitayama
2017-10-04 13:38 ` Robin Murphy
2017-10-04 13:40   ` Itaru Kitayama
2017-10-04 13:44   ` Mark Rutland
2017-10-04 14:02     ` Robin Murphy [this message]
2017-10-10 23:13     ` Itaru Kitayama

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=db08ee33-5e54-5c9a-d265-14155b72b5ad@arm.com \
    --to=robin.murphy@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 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.