[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] Re: [RFC] Unified ELF file
From: |
Dave Hylands |
Subject: |
Re: [avr-libc-dev] Re: [RFC] Unified ELF file |
Date: |
Wed, 26 Sep 2007 16:42:01 -0700 |
Hi,
On 9/26/07, Colin O'Flynn <address@hidden> wrote:
> Hi,
>
> > I propose a counter-argument: it makes no sense for *the user* to want to
> > program a single fuse byte.
>
> I agree with Eric 100% here. If you are going to be setting the fuse bytes,
> you
> *must* set them all. Otherwise you are assuming the current state of fuse
> bytes. Sure they *should* be default, but if someone else had their hands on
> the chip it might change. That's the sorta scenario where two months down the
> road stuff stops working, and you can't figure out why...
Perhaps, what should be included is a set of fuse bytes and a
corresponding mask. This would allow the program to set just the bits
it was interested in, rather than being required to set all of the
bits.
--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/
- [avr-libc-dev] RE: [RFC] Unified ELF file, Eric Weddington, 2007/09/22
- [avr-libc-dev] Re: [RFC] Unified ELF file, Colin O'Flynn, 2007/09/23
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Eric Weddington, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Colin O'Flynn, 2007/09/26
- Re: [avr-libc-dev] Re: [RFC] Unified ELF file,
Dave Hylands <=
- Re: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/26
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Eric Weddington, 2007/09/27
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/27
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Eric Weddington, 2007/09/27
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/27