Ethan Gold wrote:
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
The first part of the building section in the manual is a shopping list
of the things you need, including versions.
1.5) A consolidated list of where each package is available (CVS, FTP,
etc.)
That is there too.
2) recommended configure options to make everything end up
in reasonable places (since various packages require different options)
That is there too.
3) known building quirks
I'm not sure what you expect here.
4) A dependancy list/build order
Yep, just follow the instructions in the manual.
5) A consolidated summary of which capabilities each package provides.
Now that is a valid point. For example, you need libc to do assembly
language program,ing because libc contains all the headers files used
for both C and assembly language. That isn't obvious, and I don't think
it is documented right now.
Regards,
Steve
