Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Karl Chan <exxxxkc@getgoogleoff.me>
To: linus.walleij@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/5] pinctrl: qcom: ipq5018: allow it to be bulid on arm32
Date: Mon,  7 Oct 2024 23:32:52 +0800	[thread overview]
Message-ID: <20241007153252.31449-1-exxxxkc@getgoogleoff.me> (raw)
In-Reply-To: <CACRpkdZnBBAEgHZ=HShwvaXaN-6icC5hzwHqDNWWy_PKJDh+Fw@mail.gmail.com>

\rCBT U-Boot ver: 3.2.08  ([IPQ5018].[SPF11.3].[CSU2])

\rDRAM:  smem ram ptable found: ver: 1 len: 4
\r512 MiB
\rNAND:  QPIC controller support serial NAND
\rID = 22c822c8
\rVendor = c8
\rDevice = 22
\rSerial Nand Device Found With ID : 0xc8 0x22
\rSerial NAND device Manufacturer:GD5F2GQ5REYIH
\rDevice Size:256 MiB, Page size:2048, Spare Size:64, ECC:4-bit
\rSF: Unsupported flash IDs: manuf 00, jedec 0000, ext_jedec 0000
\ripq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
\r256 MiB
\rMMC:   sdhci: Node Not found, skipping initialization

\rPCI Link Intialized
\rPCI1 is not defined in the device tree
\rIn:    serial@78AF000
\rOut:   serial@78AF000
\rErr:   serial@78AF000
\rmachid: 8040001
\reth0 MAC Address from ART is not valid
\reth1 MAC Address from ART is not valid

\rUpdating boot_count ... done

\rSaving Environment to NAND...
\rErasing NAND...
\r\rErasing at 0x5c0000 --  25% complete.\rErasing at 0x5e0000 --  50% complete.\rErasing at 0x600000 --  75% complete.\rErasing at 0x620000 -- 100% complete.
\rWriting to NAND... OK
\rHit any key to stop autoboot:  3 \b\b\b 2 \b\b\b 1 \b\b\b 0 
\rstarting USB...
\rUSB0:   Register 2000140 NbrPorts 2
\rStarting the controller
\rUSB XHCI 1.10
\rscanning bus 0 for devices... 2 USB Device(s) found
\rreading boot-image.itb
\r16048071 bytes read in 8855 ms (1.7 MiB/s)
\r## Loading kernel from FIT Image at 44000000 ...
\r   Using 'standard' configuration
\r   Trying 'kernel' kernel subimage
\r     Description:  Kernel
\r     Type:         Kernel Image
\r     Compression:  uncompressed
\r     Data Start:   0x440000a8
\r     Data Size:    8249289 Bytes = 7.9 MiB
\r     Architecture: AArch64
\r     OS:           Linux
\r     Load Address: 0x41208000
\r     Entry Point:  0x41208000
\r   Verifying Hash Integrity ... OK
\r## Loading ramdisk from FIT Image at 44000000 ...
\r   Using 'standard' configuration
\r   Trying 'initrd' ramdisk subimage
\r     Description:  Initramfs image
\r     Type:         RAMDisk Image
\r     Compression:  Unknown Compression
\r     Data Start:   0x447ec43c
\r     Data Size:    7738968 Bytes = 7.4 MiB
\r     Architecture: AArch64
\r     OS:           Linux
\r     Load Address: unavailable
\r     Entry Point:  unavailable
\r   Verifying Hash Integrity ... OK
\r## Loading fdt from FIT Image at 44000000 ...
\r   Using 'standard' configuration
\r   Trying 'fdt' fdt subimage
\r     Description:  DTB
\r     Type:         Flat Device Tree
\r     Compression:  uncompressed
\r     Data Start:   0x447de10c
\r     Data Size:    58042 Bytes = 56.7 KiB
\r     Architecture: AArch64
\r   Verifying Hash Integrity ... OK
\r   Booting using the fdt blob at 0x447de10c
\r   Loading Kernel Image ... OK
\r   Loading Ramdisk to 4a0c0000, end 4a821658 ... OK
\r   Loading Device Tree to 4a0ae000, end 4a0bf2b9 ... OK
\rfdt_fixup_qpic: QPIC: unable to find node '/soc/qpic-nand@79b0000'
\rCould not find PCI in device tree
\rUsing machid 0x8040001 from environment

\rStarting kernel ...

\rundefined instruction
\rpc : [<41208004>]	   lr : [<4a921f8f>]
\rreloc pc : [<41208004>]	   lr : [<4a921f8f>]
\rsp : 4a822838  ip : 00000001	 fp : 00000000
\rr10: 4a83b914  r9 : 4a822ea0	 r8 : 00000000
\rr7 : 00000000  r6 : 41208000	 r5 : 4a97d848  r4 : 00000000
\rr3 : 644d5241  r2 : 4a0ae000	 r1 : 08040001  r0 : 00000000
\rFlags: nzCV  IRQs off  FIQs off  Mode SVC_32
\rResetting CPU ...

\rresetting ...


  parent reply	other threads:[~2024-10-07 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 23:27 [PATCH v5 0/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Karl Chan
2024-10-02 23:28 ` [PATCH v5 1/5] dt-bindings: arm: qcom: add Linksys EA9350 V3 Karl Chan
2024-10-03  7:28   ` Krzysztof Kozlowski
2024-10-02 23:28 ` [PATCH v5 2/5] arm64: dts: " Karl Chan
2024-12-30 14:48   ` Konrad Dybcio
2024-10-02 23:28 ` [PATCH v5 3/5] clk: qcom: ipq5018: allow it to be bulid on arm32 Karl Chan
2024-10-02 23:28 ` [PATCH v5 4/5] pinctrl: " Karl Chan
2024-10-04 11:44   ` Linus Walleij
2024-10-04 19:25     ` exxxxkc
2024-10-07 15:32     ` Karl Chan [this message]
2024-10-07 15:36       ` Karl Chan
2024-10-02 23:28 ` [PATCH v5 5/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Karl Chan
2024-10-06 20:14   ` Dmitry Baryshkov
2024-10-26 11:38     ` Konrad Dybcio
2024-10-28  6:33       ` Sricharan Ramabadhran
2024-10-28 10:24         ` Konrad Dybcio

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=20241007153252.31449-1-exxxxkc@getgoogleoff.me \
    --to=exxxxkc@getgoogleoff.me \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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