linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Arnd Bergmann <arnd@arndb.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] MIPS: TXx9: Convert SPI platform data to software nodes
Date: Tue, 18 Jan 2022 21:37:44 +0100	[thread overview]
Message-ID: <CAMuHMdXiLk+b2RtS+9xOfurVF2ajac92i_L48UAF_9B3Let0jQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2201090221150.56863@angie.orcam.me.uk>

Hi Maciej,

On Tue, Jan 18, 2022 at 8:59 PM Maciej W. Rozycki <macro@orcam.me.uk> wrote:
> > Took me a bit to test proper operation, as contemporary cross-toolchains
> > create userland binaries that can no longer run on MIPS-II/III CPUs,
> > and native development is slow and memory-constrained (dpkg OOM)...
>
>  You mean cross-toolchains included with (some) distributions, right?

Yep, the MIPS cross-toolchain that comes with Ubuntu.

>  I do hope so or otherwise I'd be very concerned.  Myself I've been using
> a self-built MIPS cross-compiler, running on POWER9, which builds MIPS I
> binaries just fine, e.g.:
>
> $ file install/usr/sysroot/{lib/ld-2.32.9000.so,usr/bin/gdbserver}
> install/usr/sysroot/lib/ld-2.32.9000.so: ELF 32-bit LSB pie executable, MIPS, MIPS-I version 1 (SYSV), dynamically linked, with debug_info, not stripped
> install/usr/sysroot/usr/bin/gdbserver: ELF 32-bit LSB executable, MIPS, MIPS-I version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld.so.1, for GNU/Linux 3.2.0, not stripped

Debian raised the minimum requirements for MIPS, hence mine are
ELF 32-bit MSB shared object, MIPS, MIPS32 rel2 version 1 (SYSV)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2022-01-18 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 10:23 [PATCH v1 1/1] MIPS: TXx9: Convert SPI platform data to software nodes Andy Shevchenko
2021-11-26 10:58 ` Arnd Bergmann
2021-11-26 12:16   ` Geert Uytterhoeven
2021-11-26 14:41     ` Andy Shevchenko
2021-11-26 17:37       ` Thomas Bogendoerfer
2021-11-29 11:28         ` Andy Shevchenko
2021-11-29 12:02           ` Thomas Bogendoerfer
2021-11-29 12:20     ` Thomas Bogendoerfer
2021-11-29 12:30       ` Geert Uytterhoeven
2021-11-29 13:05         ` Thomas Bogendoerfer
2021-11-29 19:01           ` Geert Uytterhoeven
2022-01-18 19:59             ` Maciej W. Rozycki
2022-01-18 20:37               ` Geert Uytterhoeven [this message]
2021-12-08 17:38         ` Andy Shevchenko
2021-12-08 22:07           ` Thomas Bogendoerfer
2021-12-09 10:12             ` Andy Shevchenko
2021-12-09 10:51               ` Thomas Bogendoerfer

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=CAMuHMdXiLk+b2RtS+9xOfurVF2ajac92i_L48UAF_9B3Let0jQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=tsbogend@alpha.franken.de \
    /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).