linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guo Ren <guoren@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-csky@vger.kernel.org
Subject: Re: [5.2-rc6] GX6605S testing
Date: Tue, 25 Jun 2019 08:53:27 +0800	[thread overview]
Message-ID: <CAJF2gTTQRO1T5OLH_3w9wWUV0W4r-7s6SgVGnYrqciEfUvTfng@mail.gmail.com> (raw)
In-Reply-To: <5cc9c383-3e1c-344f-cff1-8e95797b4b2c@suse.de>

Hi Andreas,

On Tue, Jun 25, 2019 at 5:19 AM Andreas Färber <afaerber@suse.de> wrote:
>
> Hello,
>
> Newbie alert. I've tailored a Kconfig for the GX6605S dev board based on
> defconfig, which required to drop "if COMPILE_TEST" for GX6605S_TIMER
> since nothing was selecting it.
>
> I've forward-ported the board's binary dtb to match the upstream
> bindings (still need to do some cleanups before I can post it here).
> Mainly compatibles and one clock-frequency -> clocks.
It's 27Mhz:
+ dummy_apb: apb-clock {
+ compatible = "fixed-clock";
+ clock-frequency = <27000000>;


>
> Here's how far I've come with the uImage:
>
> ...
> [   60.977460] sd 0:0:0:0: [sda] Attached SCSI removable disk
> [   61.357214] random: crng init done
> [   64.539130] EXT4-fs (sda2): mounted filesystem with ordered data
> mode. Opts: (null)
> [   64.763086] VFS: Mounted root (ext4 filesystem) on device 8:2.
> [   66.946712] devtmpfs: mounted
> [   67.058804] Freeing unused kernel memory: 100k freed
> [   67.205338] This architecture does not have kernel memory protection.
> [   67.386763] Run /sbin/init as init process
> [   77.719086] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b
> [   77.927527] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x0000000b ]---
>
> Note how the time is quite fast with the downstream frequency of 1 MHz.
> Sadly there's no public manual for the GX6605S SoC, only for CK610 CPU.
> 24 MHz matches the wall clock much better, indicating about 3 seconds.
>
> I've also tried using /bin/sh with the equivalent result.
> The rootfs is the one from usb.img from the C-Sky GitHub pages (modified
> to spawn getty for ttyS0), which booted okay with its binary 4.9 kernel.
>
> So, does this mean that syscalls or something changed incompatibly
> between downstream 4.9 and upstream 5.2 that I would need a new rootfs?
> Or does this mean that I'm still missing some Kconfig setting or that
> some fix/feature for CK610 hasn't made it into the mainline kernel yet?
> Did anyone here succeed with mainline on GX6605S yet?
The syscall.h is changed for newest arch version. You need new rootfs
and I recommend you try this buildroot patch:
https://lore.kernel.org/linux-csky/1561376581-19568-1-git-send-email-guoren@kernel.org/T/#u

Use that rootfs.ext2 in output image.

-- 
Best Regards
 Guo Ren

ML: https://lore.kernel.org/linux-csky/

  parent reply	other threads:[~2019-06-25  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 18:12 [5.2-rc6] GX6605S testing Andreas Färber
2019-06-24 18:35 ` Andreas Färber
2019-06-24 23:53 ` Andreas Färber
2019-06-25  0:53 ` Guo Ren [this message]
2019-06-25  1:35   ` Andreas Färber

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=CAJF2gTTQRO1T5OLH_3w9wWUV0W4r-7s6SgVGnYrqciEfUvTfng@mail.gmail.com \
    --to=guoren@kernel.org \
    --cc=afaerber@suse.de \
    --cc=linux-csky@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;
as well as URLs for NNTP newsgroup(s).