From: "Kevin Hilman" <khilman@baylibre.com>
To: Paul Burton <paul.burton@mips.com>
Cc: kernelci@groups.io
Subject: Re: MIPS test results
Date: Mon, 03 Dec 2018 09:36:01 -0800 [thread overview]
Message-ID: <7hh8fufr7i.fsf@baylibre.com> (raw)
In-Reply-To: <20181130234118.3vntmrbz5vom2sji@pburton-laptop>
[ switching to the kernelci mailing list ]
Paul Burton <paul.burton@mips.com> writes:
[...]
>> In fact, while we're doing builds for MIPS, none of us are that familiar
>> with it, so we still had some basic questions on how to boot the
>> hardware, and which kernel images we should be using to boot the boards.
>
> I'm happy to help with that :)
>
>> For example, we're building all the upstream defconfigs for MIPS, and
>> you can see those here:
>> https://storage.kernelci.org/mainline/master/v4.20-rc4-98-g60b548237fed/mips/
>>
>> Our build scripts are currently setup to save/upload the vmlinux.bin.z
>> file from the build, but we noticed that only some of the defconfigs
>> genrate the .z images. e.g. nlm_xlp_defconfig genreates the .z, whereas
>> ath25_defconfig does not.
>>
>> It looks like all the kernel builds generate a vmlinux.bin
>> (uncompressed) though, but until we have hardware that is using those
>> images, we decided not to upload the uncompressed images due to storage
>> space.
>>
>> Once we have a better idea of how to actually boot the hardware we have,
>> with which kernel images, it might help us figure out what kernel images
>> we should be saving and uploading so any labs with MIPS hardware could
>> use them.
>
> One niggle we'll have is the plethora of boot options that various MIPS
> boards make use of... Gradually we're pushing towards a standard boot
> protocol & a single kernel image (in U-Boot's FIT/.itb format) but we're
> starting from a place very far away from that.
>
> If you could let me know which boards you have I can probably help you
> boot them - I was involved in all the MIPS boards Imagination produced &
> am familiar with a bunch of our customer's boards.
The board we have is a MIPS Creator C120, so let's start with what we
need to get that one working.
Kevin
next parent reply other threads:[~2018-12-03 17:36 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 ` Kevin Hilman [this message]
2018-12-12 20:02 ` MIPS test results 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
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=7hh8fufr7i.fsf@baylibre.com \
--to=khilman@baylibre.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