From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Grant Likely <grant.likely@secretlab.ca>,
"Dezhong Diao (dediao)" <dediao@cisco.com>,
linux-mips@linux-mips.org, devicetree-discuss@lists.ozlabs.org,
David Daney <ddaney@caviumnetworks.com>,
"David VomLehn (dvomlehn)" <dvomlehn@cisco.com>
Subject: Re: [PATCH v2 1/2] MIPS: Add device tree support to MIPS
Date: Wed, 18 Aug 2010 16:36:25 +0100 [thread overview]
Message-ID: <20100818153625.GA29740@linux-mips.org> (raw)
In-Reply-To: <20100819011856.bfef5f65.sfr@canb.auug.org.au>
On Thu, Aug 19, 2010 at 01:18:56AM +1000, Stephen Rothwell wrote:
> > A suggested set of kernel defconfigs to test:
> >
> > bigsur_defconfig
> > cavium-octeon_defconfig
> > ip22_defconfig
> > ip27_defconfig
> > ip32_defconfig
> > malta_defconfig
> > allmodconfig
> >
> > These cover a huge variety of features, UP, SMP & weirdo SMP, flatmem & NUMA,
> > 32-bit, 64-bit, little and big endian.
>
> OK, I will adjust the MIPS builds tomorrow. Thanks for the suggestions.
> Just be clear, I only need to build with one compiler (presumably what
> gcc/binutils produces when I ask for a "mips" toolchain) and can drop the
> other ("mipsel"), correct?
Yes, that's entirely correct.
For the sake of others reading this I should mention that some GCC version
apparently had a bug which resulted in bad code generation for the
non-default ABI. I don't know which versions were affected but for
just doing build tests it really doesn't matter.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
David Daney
<ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
"David VomLehn (dvomlehn)"
<dvomlehn-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 1/2] MIPS: Add device tree support to MIPS
Date: Wed, 18 Aug 2010 16:36:25 +0100 [thread overview]
Message-ID: <20100818153625.GA29740@linux-mips.org> (raw)
In-Reply-To: <20100819011856.bfef5f65.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On Thu, Aug 19, 2010 at 01:18:56AM +1000, Stephen Rothwell wrote:
> > A suggested set of kernel defconfigs to test:
> >
> > bigsur_defconfig
> > cavium-octeon_defconfig
> > ip22_defconfig
> > ip27_defconfig
> > ip32_defconfig
> > malta_defconfig
> > allmodconfig
> >
> > These cover a huge variety of features, UP, SMP & weirdo SMP, flatmem & NUMA,
> > 32-bit, 64-bit, little and big endian.
>
> OK, I will adjust the MIPS builds tomorrow. Thanks for the suggestions.
> Just be clear, I only need to build with one compiler (presumably what
> gcc/binutils produces when I ask for a "mips" toolchain) and can drop the
> other ("mipsel"), correct?
Yes, that's entirely correct.
For the sake of others reading this I should mention that some GCC version
apparently had a bug which resulted in bad code generation for the
non-default ABI. I don't know which versions were affected but for
just doing build tests it really doesn't matter.
Ralf
next prev parent reply other threads:[~2010-08-18 15:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:49 [PATCH v2 1/2] MIPS: Add device tree support to MIPS Dezhong Diao
2010-07-27 21:49 ` Dezhong Diao
2010-07-28 18:54 ` Grant Likely
2010-07-28 18:54 ` Grant Likely
2010-07-28 19:19 ` David Daney
2010-07-28 19:25 ` Grant Likely
2010-07-28 19:25 ` Grant Likely
2010-07-28 20:47 ` Dezhong Diao (dediao)
2010-07-28 20:47 ` Dezhong Diao (dediao)
2010-07-29 19:40 ` Grant Likely
2010-07-29 19:40 ` Grant Likely
2010-08-16 20:42 ` Grant Likely
2010-08-16 20:42 ` Grant Likely
2010-08-17 3:40 ` Stephen Rothwell
2010-08-17 3:40 ` Stephen Rothwell
2010-08-17 3:40 ` Stephen Rothwell
2010-08-18 14:39 ` Ralf Baechle
2010-08-18 14:39 ` Ralf Baechle
2010-08-18 15:18 ` Stephen Rothwell
2010-08-18 15:18 ` Stephen Rothwell
2010-08-18 15:36 ` Ralf Baechle [this message]
2010-08-18 15:36 ` Ralf Baechle
2010-07-28 21:33 ` Ralf Baechle
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=20100818153625.GA29740@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=dediao@cisco.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dvomlehn@cisco.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-mips@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.