Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Robert Millan <rmh@gnu.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] Enable AT_PLATFORM for Loongson 2F CPU
Date: Thu, 04 Nov 2010 12:11:13 -0700	[thread overview]
Message-ID: <4CD30551.1000006@caviumnetworks.com> (raw)
In-Reply-To: <AANLkTik3SH8EmhcgY9HNQLLk9Np+E6LGo8jVoGQiQCx4@mail.gmail.com>

On 11/04/2010 11:43 AM, Robert Millan wrote:
> Hi!
>
> David Daney a écrit :
>> You are claiming that all loongson2 are loongson-2f.  Is that really
>> true?  Or are there other types of loongson2 that are not loongson-2f?
>>
>> You need to be very careful here.  This is part of the userspace ABI, so
>> if you get it wrong, you are stuck with it forever.
>
> I'll figure out how to distinguish them and send a new patch.
>
>> One question you didn't address is why userspace would care that it is
>> running on exactly "loongson-2f" instead of just mips4.
>
> I think Aurelien answered this.
>
>> The __elf_platform gets converted to a directory name by ld.so, so you
>> may want to choose a value without '-' in it.
>
> Well I appreciate consistency with GCC flag names, so I'd rather keep
> the dash, but then again it's not my decision to make.  In any case,
> whoever commits this can adjust the name to his/her liking.

I don't like to put words into Ralf's mouth, but it is easier to work 
with patches that have been tested and are ready to go, rather than 
having to re-write everything.


Some of the strings in use are "i686", "x86_64", "octeon", "octeon2", 
"PARISC", "PARISC32", tilegx-m32", "v4l", "v3l", "v4b", and "v3b", these 
last for for ARM and they don't match the GCC -mcpu= values.

So I guess what ever you want.

David Daney

  reply	other threads:[~2010-11-04 19:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 12:18 [PATCH] Enable AT_PLATFORM for Loongson 2F CPU Robert Millan
2010-11-04 16:44 ` David Daney
2010-11-04 17:33   ` Aurelien Jarno
2010-11-04 18:43     ` Robert Millan
2010-11-04 19:11       ` David Daney [this message]
2010-11-04 19:29         ` Ralf Baechle
2010-11-07 12:30       ` Robert Millan
2010-11-08 19:13         ` David Daney
2010-11-08 22:27           ` Robert Millan
2010-11-08 22:50             ` David Daney
2010-11-08 23:02               ` Robert Millan
2010-11-09  9:48                 ` wu zhangjin
2010-11-09 12:24                   ` Robert Millan
2010-11-09 15:40                     ` Ralf Baechle
2010-11-11 14:47                       ` Robert Millan
2010-11-15 23:50                         ` Robert Millan
2010-11-15 23:59                           ` David Daney
2010-11-22 12:44                             ` Robert Millan

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=4CD30551.1000006@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=aurelien@aurel32.net \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=rmh@gnu.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