Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/dev/pci/pucvar.h

79 lines
2.7 KiB
C
Raw Normal View History

add code to cope with multiple ports per BAR, as are found, for instance, on the 8 port card Simon Gerraty has. In general, cards which have this lots of ports also have a separate interrupt status register, but this change is just to talk to the various ports independently. It works, but it's not optimal. (XXX still need a good name for the card in the comments, and to update the manual page.)
1999-02-06 09:29:54 +03:00
/* $NetBSD: pucvar.h,v 1.2 1999/02/06 06:29:54 cgd Exp $ */
add a driver for "PCI 'universal' communications" cards, that is, PCI cards which contain 'standard' com- and lpt-type ports. Some of these present as PCI simple-communications/serial or simple-communications/parallel devices, but many do not. (Additionally, there is no document that I can find that describes the "specific well-konwn register-level" description of how the 'standard' devices' config space headers shold work.) Eventually, some of the devices driven by this code should become simple pci attachments for the 'lpt' and 'com' drivers, but that requires solid documentation.
1998-06-26 22:52:41 +04:00
/*
add code to cope with multiple ports per BAR, as are found, for instance, on the 8 port card Simon Gerraty has. In general, cards which have this lots of ports also have a separate interrupt status register, but this change is just to talk to the various ports independently. It works, but it's not optimal. (XXX still need a good name for the card in the comments, and to update the manual page.)
1999-02-06 09:29:54 +03:00
* Copyright (c) 1998, 1999 Christopher G. Demetriou. All rights reserved.
add a driver for "PCI 'universal' communications" cards, that is, PCI cards which contain 'standard' com- and lpt-type ports. Some of these present as PCI simple-communications/serial or simple-communications/parallel devices, but many do not. (Additionally, there is no document that I can find that describes the "specific well-konwn register-level" description of how the 'standard' devices' config space headers shold work.) Eventually, some of the devices driven by this code should become simple pci attachments for the 'lpt' and 'com' drivers, but that requires solid documentation.
1998-06-26 22:52:41 +04:00
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by Christopher G. Demetriou
* for the NetBSD Project.
* 4. The name of the author may not be used to endorse or promote products
* derived from this software without specific prior written permission
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
/*
* Exported (or conveniently located) PCI "universal" communications card
* software structures.
*
* Author: Christopher G. Demetriou, May 14, 1998.
*/
add code to cope with multiple ports per BAR, as are found, for instance, on the 8 port card Simon Gerraty has. In general, cards which have this lots of ports also have a separate interrupt status register, but this change is just to talk to the various ports independently. It works, but it's not optimal. (XXX still need a good name for the card in the comments, and to update the manual page.)
1999-02-06 09:29:54 +03:00
#define PUC_MAX_PORTS 8
add a driver for "PCI 'universal' communications" cards, that is, PCI cards which contain 'standard' com- and lpt-type ports. Some of these present as PCI simple-communications/serial or simple-communications/parallel devices, but many do not. (Additionally, there is no document that I can find that describes the "specific well-konwn register-level" description of how the 'standard' devices' config space headers shold work.) Eventually, some of the devices driven by this code should become simple pci attachments for the 'lpt' and 'com' drivers, but that requires solid documentation.
1998-06-26 22:52:41 +04:00
struct puc_device_description {
const char *name;
pcireg_t rval[4];
pcireg_t rmask[4];
struct {
int type;
int bar;
add code to cope with multiple ports per BAR, as are found, for instance, on the 8 port card Simon Gerraty has. In general, cards which have this lots of ports also have a separate interrupt status register, but this change is just to talk to the various ports independently. It works, but it's not optimal. (XXX still need a good name for the card in the comments, and to update the manual page.)
1999-02-06 09:29:54 +03:00
int offset;
add a driver for "PCI 'universal' communications" cards, that is, PCI cards which contain 'standard' com- and lpt-type ports. Some of these present as PCI simple-communications/serial or simple-communications/parallel devices, but many do not. (Additionally, there is no document that I can find that describes the "specific well-konwn register-level" description of how the 'standard' devices' config space headers shold work.) Eventually, some of the devices driven by this code should become simple pci attachments for the 'lpt' and 'com' drivers, but that requires solid documentation.
1998-06-26 22:52:41 +04:00
} ports[PUC_MAX_PORTS];
};
#define PUC_REG_VEND 0
#define PUC_REG_PROD 1
#define PUC_REG_SVEND 2
#define PUC_REG_SPROD 3
#define PUC_PORT_TYPE_NONE 0
#define PUC_PORT_TYPE_COM 1
#define PUC_PORT_TYPE_LPT 2
#define PUC_PORT_VALID(desc, port) \
((port) < PUC_MAX_PORTS && (desc)->ports[(port)].type != PUC_PORT_TYPE_NONE)
#define PUC_PORT_BAR_INDEX(bar) (((bar) - PCI_MAPREG_START) / 4)
struct puc_attach_args {
int port;
int type;
pci_chipset_tag_t pc;
pci_intr_handle_t intrhandle;
bus_addr_t a;
bus_space_tag_t t;
bus_space_handle_t h;
};
extern const struct puc_device_description puc_devices[];