Re: [avrdude-dev] avrdude on Windows

[Brian Dean]

On Thu, Feb 13, 2003 at 09:24:37AM -0700, E. Weddington wrote:

> I suspected as much that this would be the best way to go. I'm 
> currently in the middle of writing a ppiwin.c file that provides the 
> 8 functions previously talked about. Brian, I assume that we would 
> want to have one ppi.h that provides the prototypes?

Yes, here's my current copy of ppi.h:

#ifndef __ppi_h__
#define __ppi_h__

#include "config.h"

/*
 * PPI registers
 */
enum {
  PPIDATA,
  PPICTRL,
  PPISTATUS
};


int ppi_getpinmask(int pin);

#if !defined(ppi_claim)
#  define ppi_claim(pgm)
#endif

#if !defined(ppi_release)
#  define ppi_release(pgm)
#endif

int ppi_setpin    (int fd, int pin, int value);

int ppi_getpin    (int fd, int pin);

int ppi_set       (int fd, int reg, int bit);

int ppi_clr       (int fd, int reg, int bit);

int ppi_getall    (int fd, int reg);

int ppi_setall    (int fd, int reg, int val);

int ppi_pulsepin  (int fd, int pin);

#endif


These represent the functions and enums needed by my new 'par.c' file.
I've got the split done and working.  Shall I go ahead an commit this?
Is it going to cause anyone too much disruption (mostly thinking of
Ted's autoconf work)?  If there are any objections, let me know soon.

-Brian