public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	kernelci@groups.io, info <info@kernelci.org>
Cc: Corentin Labbe <clabbe@baylibre.com>
Subject: Re: Participate in build test (MIPS/Loongson)
Date: Mon, 13 Jul 2020 10:21:15 -0700	[thread overview]
Message-ID: <7himerqqk4.fsf@baylibre.com> (raw)
In-Reply-To: <bf280d0a-9289-1048-a8a4-f3e2972196d4@flygoat.com>

Jiaxun Yang <jiaxun.yang@flygoat.com> writes:

> 在 2020/7/7 8:43, Jiaxun Yang 写道:
>>
>>
>> 在 2020/7/7 2:24, Kevin Hilman 写道:
>>> Hi Jianxun,
>>>
>>> Jiaxun Yang<jiaxun.yang@flygoat.com>  writes:
>>>
>>>> I'm a maintainer of MIPS/LOONGSON64 and MIPS/LOONGSON2EF support in
>>>> kernel, and I would like to enable build test for these platforms in
>>>> KernelCI. Also I will respond to their build failures.
>>>>
>>>> Currently it's hard for me to provide hardware to perform boot test as
>>>> a amateur, but Fuloong2E has already accepted by QEMU and we can
>>>> perform boot test on it for LOONGSON2EF.
>>>>
>>>> Please give me some instructions.
>>>>
>>>> Btw: MIPS/malta is not under my maintenance but I can also respond to
>>>> it's build failure and QEMU boot failure. I'd like to apply for this
>>>> platform too if I'm eligible.
>>> I don't think we're doing any MIPS boots on QEMU currently, but we can
>>> probably add that if you can give us a bit of guidance.  I've also cc'd
>>> Corentin who has been working on QEMU support for more platforms.
>>>
>>> Can you share with us more details on QEMU version that is known to work
>>> well for upstream MIPS kernels, and the qemu cmdline that you use to
>>> boot upstream kernels?  With that, we can guide you on how to add
>>> support.
>>
>> Sure, with QEMU 4.2/5.0:
>
> Forget to mention that I'd also have to select some drivers to get it boot.
> I saw clabbe's work on github. Will discuss here.

Also, can you keep an eye on the MIPS build results?  At least on
stable, mainline and linux-next?

Thanks,

Kevin

  reply	other threads:[~2020-07-13 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 13:11 Participate in build test (MIPS/Loongson) Jiaxun Yang
2020-07-06 18:24 ` Kevin Hilman
2020-07-07  0:43   ` Jiaxun Yang
2020-07-07  2:14     ` Jiaxun Yang
2020-07-13 17:21       ` Kevin Hilman [this message]
2020-07-18  2:18         ` Jiaxun Yang
2020-07-20  7:58           ` Guillaume Tucker
  -- strict thread matches above, loose matches on Subject: below --
2020-04-05  8:44 Jiaxun Yang

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=7himerqqk4.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=clabbe@baylibre.com \
    --cc=info@kernelci.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernelci@groups.io \
    /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