Hi Matthew,
I think the problem with the manual is not so much in its content,
but its organization. I found may way through using the manual,
but it could use some structure. This is particularly true regarding
the web pages which discuss the various JTAG communication
tools. A Linked list of package names with brief descriptions (and
available longer descriptions) instead of paragraphs interspersed
with "this is available _here_" will make finding the tools much
simpler.
here are my brief suggestions, and I'll post my own notes today,
after which everyone can tear them apart and make fun of my
inefficiency.
1) All required packages should be listed together on one page
along with the latest version numbers that work together
1.5) A consolidated list of where each package is available (CVS, FTP,
etc.)
2) recommended configure options to make everything end up
in reasonable places (since various packages require different options)
3) known building quirks
4) A dependancy list/build order
5) A consolidated summary of which capabilities each package provides.
That's my $.02
-E
On Feb 26, 2004, at 8:31 AM, Steve Underwood wrote:
Hi Matthew,
Matthew Peters wrote:
Well, i think the best sugestion is to make all the different
documentation point to that document, and maybe put a copy of that
section
in an 'INSTALL' file found in the packages.
A good example of the problem is that i had never read that gcc-3.3
in the
cvs tree was supposed to go with gcc-3.2.3. I tried a gcc-3.3 source
with the
cvs files and it didn't work.
gcc compiled, awsome. Thanks for the link, btw, i doubt i would've
figured
this out without it.
Matthew Peters
You didn't read the manual. It tells you about this, and that it is a
historical accident. People complain there is no documentation, but
most times they just don't read it. I'd still like to know where the
manual is inadequate, and what we need to add to improve it.
Regards,
Steve
