public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>,
	 Masaki Muranaka <monaka@monami-software.com>
Subject: Re: [patch] target triplet for Microblaze.
Date: Thu, 18 Nov 2010 18:44:00 -0000	[thread overview]
Message-ID: <4CE57418.6010206@eagerm.com> (raw)
In-Reply-To: <201011181813.54314.pedro@codesourcery.com>

Pedro Alves wrote:
> On Thursday 18 November 2010 17:43:50, Michael Eager wrote:
> 
>> MicroBlaze is a proprietary processor developed by Xilinx and, AFAIK,
>> they have not licensed it to other manufacturers.  
> 
> 
> 
>> Xilinx is the only possible specification which meets the definition
>> in Autobook.
> 
> That can't be right.
> 
> " cpu
>      The type of processor used on the system. (...)
> 
>  manufacturer
>      A somewhat freeform field which indicates the manufacturer of the system. (...)"
> 
> It's manufacturer of the system, not of the CPU.
> Note "used on the system", therefore cpu != system.  And "system"
> is really a broad term.  AFAIK, it's really a freeform field in
> practice, so you should be able to put anything there.  For example,
> if one takes xilink's toolchain sources (the gpl bits), fork / patch
> them for some reason, and build / distribute them oneself, one
> might want to legitimately change the manufacturer field to
> avoid confusion.

System, in this case, is the FPGA, manufactured by Xilinx.

If someone did fork the toolchain, how would that change
the manufacturer of the target system?

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

  reply	other threads:[~2010-11-18 18:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  9:23 Masaki Muranaka
2010-11-18 17:10 ` Joel Brobecker
2010-11-18 17:44   ` Michael Eager
2010-11-18 18:14     ` Pedro Alves
2010-11-18 18:44       ` Michael Eager [this message]
2010-11-18 20:45         ` Pedro Alves
2010-11-18 21:35           ` Michael Eager
2010-11-18 21:49             ` Pedro Alves
2010-11-18 22:32     ` Joel Brobecker
2010-11-18 22:53       ` Michael Eager
2010-12-04  2:12         ` Masaki Muranaka

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=4CE57418.6010206@eagerm.com \
    --to=eager@eagerm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.com \
    --cc=pedro@codesourcery.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).