public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Paul Burton <paul.burton@mips.com>
Cc: Ezequiel Garcia <ezequiel.garcia@collabora.com>,
	"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: MIPS test results
Date: Fri, 14 Dec 2018 17:28:48 -0800	[thread overview]
Message-ID: <7h36qzmvcf.fsf@baylibre.com> (raw)
In-Reply-To: <20181214185412.3uelhb4ubiyvnf2r@pburton-laptop>

Paul Burton <paul.burton@mips.com> writes:

> Hi Kevin,
>
> On Fri, Dec 14, 2018 at 09:03:43AM -0800, Kevin Hilman wrote:
>> > However... this log you have here is not from the CI20 board,
>> > which is JZ4780 SoC, but from some development board
>> > with a Pistachio SoC!
>> 
>> The board I have is labeled Creator Ci40, and grep'ing in the MIPS DT
>> files, led me to pistachio_marduk.dts.
>
> Right - pistachio is the codename for the cXT200 SoC, and marduk is the
> codename for the Ci40 board.
>
>> > I thought those were dead, but it seems there are some Pistachio
>> > boards around ?
>> 
>> This was given to me by Imagination a couple years ago, but I never had
>> the time to get it into kernelCI, and then the interest from Imagination
>> "went away." ;)
>> 
>> If nobody cares about this particular board, I don't really want to
>> waste any time on it either.  But, if there are other boards that people
>> actually care about we should integrate into kernelCI, and that someone
>> wants to donate, I'd prefer to setup those.
>
> I don't especially care about the Ci40 board per se, but I do care about
> the interAptiv CPU it uses & which still has active customers. So far as
> I'm aware the Ci40 is the only dev board available to the public
> containing interAptiv cores, so that leaves me caring about tests on
> Ci40 :)
>
> In terms of updating its U-Boot, I notice the creatordev.io site that
> documented it is no longer online... But its source is available here:
>
>   https://github.com/CreatorDev/u-boot
>
> You can build it yourself as README.md describes, or I've placed a
> prebuilt binary here:
>
>   https://0x83.org/tmp/u-boot-pistachio_marduk-2015.10-v1.0.5-00001-gc1b568e7ea-dirty.img
>
> It says -dirty in the filename but I believe this is just because the
> .gitignore rules don't ignore some of the files generated by the
> build... I promise I didn't sneak anything malicious in here :)
>
> For reference I built it using the Codescape 2018.09-02 toolchain from
> here:
>
>   https://codescape.mips.com/components/toolchain/2018.09-02/downloads.html

I tried building, but my MIPS complier from debian (gcc version 6.3.0
20170516 (Debian 6.3.0-18)) wouldn't build it, and I got the same errors
from the version of the compiler you link above.

Is anyone working on more recent MIPS compilers?  For all the other
arches we're building with gcc-7 or gcc-8.

Anyways, I tried with you u-boot image, and that can DHCP so I'm on to
the next step.

I was then able to build mainline (pistachio_defconfig) and boot
mainline using the debian ramdisk and rootfs (mipsel) we build for
kernelCI!

In the process I found a couple things to fix in how we build/install
kernels for MIPS, so I've submitted some fixes for kernelCI infra.  Once
those are merged, we'll start getting regular builds and boots on my
Ci40 with kernelCI.

If you have other boards that might be interesting, I'd be happy to add
them as well.

Thanks for all the help getting this bootstrapped,

Kevin

  reply	other threads:[~2018-12-15  1:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181128233013.nymedsx2ukdx2otq@pburton-laptop>
     [not found] ` <7hr2f3afkb.fsf@baylibre.com>
     [not found]   ` <20181130234118.3vntmrbz5vom2sji@pburton-laptop>
2018-12-03 17:36     ` MIPS test results Kevin Hilman
2018-12-12 20:02       ` Paul Burton
2018-12-14  0:51         ` Kevin Hilman
2018-12-14  4:43           ` Ezequiel Garcia
2018-12-14 17:03             ` Kevin Hilman
2018-12-14 17:43               ` Ezequiel Garcia
2018-12-14 18:54               ` Paul Burton
2018-12-15  1:28                 ` Kevin Hilman [this message]
2018-12-15  1:58                   ` Guenter Roeck
2018-12-15  4:26                   ` Paul Burton

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=7h36qzmvcf.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=ezequiel.garcia@collabora.com \
    --cc=kernelci@groups.io \
    --cc=paul.burton@mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox