From: Denis Orlov <denorl2009@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 3/3] ci: add a job for testing 64BIT MIPS with labgrid
Date: Fri, 9 Jun 2023 10:58:06 +0300 [thread overview]
Message-ID: <CALHb5ujRqJQKYGU1Pivwph0H1UojHW-8sYvPVGqj63Ng9PG2Dw@mail.gmail.com> (raw)
In-Reply-To: <8e0570ef-ea42-b9d7-1ebf-ffd17bd0d97d@pengutronix.de>
On Fri, 9 Jun 2023 at 09:38, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> On 07.06.23 06:59, Denis Orlov wrote:
> > Signed-off-by: Denis Orlov <denorl2009@gmail.com>
>
> https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/13.1.0/
> has a dedicated mips64 toolchain. Given that you don't touch the Containerfile,
> I assume this means that the normal toolchain can compile both 32- and 64-bit?
Well, it seems so, judging by the fact that I had run CI successfully on
my GitHub repo. I guess the main difference between mips and mips64
toolchains is the default compile configuration values. On debian there
are also many different MIPS compilers (mips-linux-gnu-, mipsel-linux-gnu-,
mips64-linux-gnuabi64-, mips64el-linux-gnuabi64-, and others) available,
however I am compiling barebox/Linux successfully with the mips-linux-gnu-
one when the correct target endianness/ABI options are being passed.
Maybe there are other differences, but I don't know of them.
Regards,
Denis
>
> If so,
>
> Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>
> > ---
> > .github/workflows/test-labgrid-pytest.yml | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/.github/workflows/test-labgrid-pytest.yml b/.github/workflows/test-labgrid-pytest.yml
> > index 2c74150066..674e4251d1 100644
> > --- a/.github/workflows/test-labgrid-pytest.yml
> > +++ b/.github/workflows/test-labgrid-pytest.yml
> > @@ -26,6 +26,10 @@ jobs:
> > lgenv: test/mips/qemu-malta_defconfig.yaml
> > defconfig: qemu-malta_defconfig
> >
> > + - ARCH: mips
> > + lgenv: test/mips/qemu-malta64el_defconfig.yaml
> > + defconfig: qemu-malta64el_defconfig
> > +
> > - ARCH: x86
> > lgenv: test/x86/efi_defconfig.yaml
> > defconfig: efi_defconfig
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
next prev parent reply other threads:[~2023-06-09 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 4:59 [PATCH 0/3] Add CI for MIPS64 Denis Orlov
2023-06-07 4:59 ` [PATCH 1/3] MIPS: add qemu-malta64el_defconfig Denis Orlov
2023-06-09 5:09 ` Antony Pavlov
2023-06-09 6:35 ` Ahmad Fatoum
2023-06-07 4:59 ` [PATCH 2/3] test: mips: add QEMU Malta 64le labgrid config Denis Orlov
2023-06-09 6:36 ` Ahmad Fatoum
2023-06-09 7:14 ` Denis Orlov
2023-06-09 7:21 ` Ahmad Fatoum
2023-06-09 9:17 ` Denis Orlov
2023-06-09 9:28 ` Ahmad Fatoum
2023-06-09 9:38 ` Denis Orlov
2023-06-09 9:41 ` Ahmad Fatoum
2023-06-07 4:59 ` [PATCH 3/3] ci: add a job for testing 64BIT MIPS with labgrid Denis Orlov
2023-06-09 6:38 ` Ahmad Fatoum
2023-06-09 7:58 ` Denis Orlov [this message]
2023-06-12 6:39 ` [PATCH 0/3] Add CI for MIPS64 Sascha Hauer
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=CALHb5ujRqJQKYGU1Pivwph0H1UojHW-8sYvPVGqj63Ng9PG2Dw@mail.gmail.com \
--to=denorl2009@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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