Re: [avrdude-dev] Release soon?

[Brian Dean]

On Mon, Mar 03, 2003 at 10:53:36AM -0700, E. Weddington wrote:

> 1. I need to try out Ted's latest automagical stuff and build the 
> docs on Windows; and review the docs. This will happen within a day 
> or two.

Yes - I need to figure out this for FreeBSD as well.  I may draw on
Joerg's exppertise with the FreeBSD ports system for this :-)

> 2. What is the status of supporting stk500 versions other than 1.10? 
> I remember some talk on the list, but I don't remember if support for 
> greater versions was added to avrdude. IIRC, there is support in uisp 
> for all versions and it would be great if avrdude was released with 
> this. Ted?

I added the hooks to do this, but not the actual code itself.  I think
I could code this up based on Ted's description of what needs to
happen, but I don't have any way to test it.  My firmware is at 1.10,
but I don't have any way to update it at the moment.  Do any of us
here have the later firmware that can test it?  Can you test it, Ted?

> 3. Users may want to know before actually using avrdude, what devices 
> it supports and what programmers it supports. Currently, one can 
> exec:
> avrdude -c ?
> and it will spit out a list of programmers. But if one tries:
> avrdude -p ?
> it will give an error message saying to specify a programmer first. 
> It would be nice to be able to have both the above command lines work 
> to list programmers or AVR devices in the config file. And then, of 
> course, have this in the docs as well.

Ok, I'll take a look at this.

> 4. Any objection to adding the below to the config file?
> programmer
>   id    = "avrisp";
>   desc  = "Atmel AVR ISP";
>   type  = stk500;
> ;

No objection, good idea - please add it.

> 5. Any thoughts about trying to beef up the database before release 
> (devices / programmers)? I'm ok if not. We can just wait for user 
> submissions.

Haven't really thought about that.  I hadn't planned on it.  I think
support is already present for all the parts I have on hand.  I'd be
reluctant to add entries for parts that I couldn't test, but don't let
that stop other motivated people :-)

> 6. I have a couple of items that I want to do for the Windows port 
> but only *after* this release. Any thoughts to starting a TODO file?

Sounds fine to me.

-Brian