[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avrdude-dev] avrdude on Windows
From: |
E. Weddington |
Subject: |
Re: [avrdude-dev] avrdude on Windows |
Date: |
Wed, 12 Feb 2003 17:27:31 -0700 |
On 12 Feb 2003 at 19:04, Brian Dean wrote:
> I can really go either way on this. In working up a split, I now
> remember why I didn't do it the first time around, and that is that no
> other routines require parallel port access outside of the generic
> parallel port programmer interface. Thus, it doesn't make a lot of
> sense to split these routines off from a modularity perspective. In
> fact, I think all the ppi_* routines could be declared static within
> ppi.c (except for ppi_initpgm(), but I plan to fix that shortly).
What about ppi_open and ppi_close? They get assigned to the pgm
struct.
Eric
- [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/11
- Re: [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/12
- Re: [avrdude-dev] avrdude on Windows, Brian Dean, 2003/02/12
- Re: [avrdude-dev] avrdude on Windows, Joerg Wunsch, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, Brian Dean, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, Joerg Wunsch, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, Brian Dean, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, Theodore A. Roth, 2003/02/13
- Re: [avrdude-dev] avrdude on Windows, E. Weddington, 2003/02/13