> -----Original Message----- > From: Colin O'Flynn [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 20, 2007 12:51 PM > To: Eric Weddington > Cc: 'Erik Christiansen'; [EMAIL PROTECTED]; 'Rick Altherr' > Subject: Re: [RFC] Unified ELF file > > Hello, > > > We cannot declare the fuse variable, assign the default value in > > the header file, and then allow the user to then assign a > different value > > in their .c file outside of a function. > > How would you feel about declaring the fuses in the makefile? > As in have a > line something like > > LFUSE = CKSEL0 & SUT0 > > For example. This Define's the value 'LFUSE', which we just > have in fuse.h: > > unsigned char __lfuse __attribute__((section (".lfuse"))) = LFUSE; > > Then the option is to either error out if the user doesn't do > anything about > fuses in the makefile (aka: using an old Makefile with > updated avr toolchain) > or just define LFUSE to be the default value. Probably > setting it to a > default would be the least hassle for users.
I'd rather not have to also change a Makefile. Doing that would affect users of AVR Studio and its generated Makefile, which I would rather not change at this time. <snip: attachement problems> > Also once you do decide on the layout of the ELF file, let me > know. I still > have all the code for avrdude - so can change that around to > work with your > layout. That's good. We'll need it soon. _______________________________________________ AVR-libc-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
