public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joerg Wunsch <j@uriah.heep.sax.de>
To: Eric Christopher <echristo@apple.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>, binutils@sourceware.org
Subject: Re: maintainer update: add support for more AVR microcontrollers
Date: Fri, 21 Apr 2006 06:55:00 -0000	[thread overview]
Message-ID: <20060420210123.GH49692@uriah.heep.sax.de> (raw)
In-Reply-To: <F610553E-74F0-44C0-AA67-94EC0BD0DD70@apple.com>

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

As Eric Christopher wrote:

> >Documentation for the entire toolchain is mainly maintained as part
> >of the avr-libc project:

> >http://www.nongnu.org/avr-libc/user-manual/index.html

> This is bad. You should consider documenting the binutils options in
> the binutils manual.

Well, seriously, most of our users probably don't know what binutils
actually means.  For them, it's all "the compiler", and they are
already wondering why "the compiler" doesn't come along bundled with
an editor, as all of our "competitors" (i. e. other embedded compiler
vendors) do.

Thus, maintaining a consistent documentation for the entire toolchain
has a much higher priority to me than anything else, as that way, I
can at least point people to a single location where they can get all
the information needed.  Fortunately, we made a lot of progress here
compared to say 5 years ago, when the AVR support in the GNU toolchain
started its life, and many documentation files really only ended up in
.c.

If the original authors had bothered to at least write something like
a gas/doc/c-avr.texi file at all, well, I had no trouble to add each
new device name there as we are adding it.  However, there would be
much more things to document like added assembler operators where I'm
unfortunately don't even know for sure myself what they are doing
exactly. :-(  I'll see to find the people who once started that
project, and try whether we could come up with that doc file
eventually.

For the time being, please accept the patch as it is.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-04-20 21:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20  1:52 Joerg Wunsch
2006-04-20 10:51 ` Jan-Benedict Glaw
2006-04-20 10:53   ` Eric Christopher
2006-04-20 11:05     ` Joerg Wunsch
2006-04-20 14:24       ` Eric Christopher
2006-04-21  6:55         ` Joerg Wunsch [this message]
2006-04-22 14:20 Björn Haase

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=20060420210123.GH49692@uriah.heep.sax.de \
    --to=j@uriah.heep.sax.de \
    --cc=binutils@sourceware.org \
    --cc=echristo@apple.com \
    --cc=jbglaw@lug-owl.de \
    --cc=joerg_wunsch@uriah.heep.sax.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 read-only IMAP folder(s) and NNTP newsgroup(s).