As Michael Hennebry wrote: > Let there be hardcoded default section names > and parameters like --hfuse-section-name .
Btw., you wouldn't get AVR-centric options like this one into official GNU binutils. The binutils are fairly generic in their entire idea, and support several dozens of different CPUs and object file formats. My idea is that it simply doesn't matter whether you use objcopy (to get a hex file) or not: avrdude can read both, the ELF file, but could also obtain the very same information from an (*) Intel hex file produced by objcopy. The option to pass hex files as an alternative to full ELF files has been requested by users. Not everybody would be happy to pass along the entire ELF file (it's simply a matter of trust to not give any trade secrets out of house), and companies specialized on pre-programming AVRs are familiar with hex files, but it will take a while until you could convince them to also accept alternate file formats. (*) With "an" meaning *exactly one*, not two, three, or five different hex files, as we are doing now. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-chat mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-chat
