Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/sys/dev/isa/fdc_isa.c

234 lines
7.2 KiB
C
Raw Normal View History

Fix sizeof and whitespace bug from the script I'm using to do the CFATTACH_DECL conversion. (Grumble.)
2002-10-02 07:10:45 +04:00
/* $NetBSD: fdc_isa.c,v 1.7 2002/10/02 03:10:46 thorpej Exp $ */
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
/*-
* Copyright (c) 1998 The NetBSD Foundation, Inc.
* All rights reserved.
*
* This code is derived from software contributed to The NetBSD Foundation
* by Charles M. Hannum.
*
* 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 the NetBSD
* Foundation, Inc. and its contributors.
* 4. Neither the name of The NetBSD Foundation nor the names of its
* contributors may be used to endorse or promote products derived
* from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
* ``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 FOUNDATION OR CONTRIBUTORS
* 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.
*/
/*-
* Copyright (c) 1990 The Regents of the University of California.
* All rights reserved.
*
* This code is derived from software contributed to Berkeley by
* Don Ahn.
*
* 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 the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``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 REGENTS OR CONTRIBUTORS 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.
*
* @(#)fd.c 7.4 (Berkeley) 5/25/91
*/
add RCSID
2001-11-13 11:01:09 +03:00
#include <sys/cdefs.h>
Fix sizeof and whitespace bug from the script I'm using to do the CFATTACH_DECL conversion. (Grumble.)
2002-10-02 07:10:45 +04:00
__KERNEL_RCSID(0, "$NetBSD: fdc_isa.c,v 1.7 2002/10/02 03:10:46 thorpej Exp $");
add RCSID
2001-11-13 11:01:09 +03:00
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
#include "rnd.h"
#include <sys/param.h>
#include <sys/systm.h>
#include <sys/callout.h>
#include <sys/device.h>
#include <sys/buf.h>
#include <sys/queue.h>
#if NRND > 0
#include <sys/rnd.h>
#endif
#include <machine/bus.h>
#include <machine/intr.h>
#include <dev/isa/isavar.h>
#include <dev/isa/isadmavar.h>
#include <dev/isa/fdreg.h>
#include <dev/isa/fdcvar.h>
int fdc_isa_probe(struct device *, struct cfdata *, void *);
void fdc_isa_attach(struct device *, struct device *, void *);
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
struct fdc_isa_softc {
struct fdc_softc sc_fdc; /* base fdc device */
bus_space_handle_t sc_baseioh; /* base I/O handle */
};
Use CFATTACH_DECL().
2002-10-02 06:00:07 +04:00
CFATTACH_DECL(fdc_isa, sizeof(struct fdc_isa_softc),
Fix sizeof and whitespace bug from the script I'm using to do the CFATTACH_DECL conversion. (Grumble.)
2002-10-02 07:10:45 +04:00
fdc_isa_probe, fdc_isa_attach, NULL, NULL);
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
#ifdef NEWCONFIG
void fdc_isa_forceintr(void *);
#endif
int
fdc_isa_probe(struct device *parent,
struct cfdata *match,
void *aux)
{
struct isa_attach_args *ia = aux;
bus_space_tag_t iot;
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
bus_space_handle_t ioh, ctl_ioh, base_ioh;
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
int rv, iobase;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
iot = ia->ia_iot;
rv = 0;
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
if (ia->ia_nio < 1)
return (0);
if (ia->ia_nirq < 1)
return (0);
if (ia->ia_ndrq < 1)
return (0);
if (ISA_DIRECT_CONFIG(ia))
return (0);
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
/* Disallow wildcarded I/O addresses. */
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
if (ia->ia_io[0].ir_addr == ISACF_PORT_DEFAULT)
return (0);
/* Don't allow wildcarded IRQ/DRQ. */
if (ia->ia_irq[0].ir_irq == ISACF_IRQ_DEFAULT)
return (0);
if (ia->ia_drq[0].ir_drq == ISACF_DRQ_DEFAULT)
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
return (0);
/* Map the I/O space. */
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
iobase = ia->ia_io[0].ir_addr;
if (bus_space_map(iot, iobase, 6 /* FDC_NPORT */, 0, &base_ioh))
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
return (0);
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
if (bus_space_subregion(iot, base_ioh, 2, 4, &ioh)) {
bus_space_unmap(iot, base_ioh, 6);
return (0);
}
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
if (bus_space_map(iot, iobase + fdctl + 2, 1, 0, &ctl_ioh)) {
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
bus_space_unmap(iot, base_ioh, 6);
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
return (0);
}
/* Not needed for the rest of the probe. */
bus_space_unmap(iot, ctl_ioh, 1);
/* reset */
bus_space_write_1(iot, ioh, fdout, 0);
delay(100);
bus_space_write_1(iot, ioh, fdout, FDO_FRST);
/* see if it can handle a command */
if (out_fdc(iot, ioh, NE7CMD_SPECIFY) < 0)
goto out;
out_fdc(iot, ioh, 0xdf);
out_fdc(iot, ioh, 2);
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
rv = 1;
ia->ia_nio = 1;
ia->ia_io[0].ir_size = FDC_NPORT;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
ia->ia_nirq = 1;
ia->ia_ndrq = 1;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
ia->ia_niomem = 0;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
out:
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
bus_space_unmap(iot, base_ioh, 6 /* FDC_NPORT */);
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
return (rv);
}
void
fdc_isa_attach(struct device *parent,
struct device *self,
void *aux)
{
struct fdc_softc *fdc = (void *) self;
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
struct fdc_isa_softc *isc = (void *) self;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
struct isa_attach_args *ia = aux;
printf("\n");
fdc->sc_iot = ia->ia_iot;
fdc->sc_ic = ia->ia_ic;
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
fdc->sc_drq = ia->ia_drq[0].ir_drq;
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
if (bus_space_map(fdc->sc_iot, ia->ia_io[0].ir_addr,
6 /* FDC_NPORT */, 0, &isc->sc_baseioh)) {
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
printf("%s: unable to map I/O space\n", fdc->sc_dev.dv_xname);
return;
}
Traditionally, the floppy controller was configured at 0x3f0 for 8 ports, but the registers actually begin at 0x3f2, and this is what PNPBIOS reports for the floppy controller resources. Adjust the register offsets and the mapping of them for the ISA front-end to compensate, so that the PNPBIOS attachment of the floppy controller actually works.
2000-05-02 07:33:45 +04:00
if (bus_space_subregion(fdc->sc_iot, isc->sc_baseioh, 2, 4,
&fdc->sc_ioh)) {
printf("%s: unable to subregion I/O space\n",
fdc->sc_dev.dv_xname);
return;
}
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
if (bus_space_map(fdc->sc_iot, ia->ia_io[0].ir_addr + fdctl + 2, 1, 0,
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
&fdc->sc_fdctlioh)) {
printf("%s: unable to map CTL I/O space\n",
fdc->sc_dev.dv_xname);
return;
}
Overhaul of the ISA autoconfiguration code to support direct configuration of devices logically attached to the ISA bus: * Change the isa_attach_args to have arrays of io, mem, irq, drq resources. * Add a "pnpnames" and a linked list of "pnpcompatnames" to the isa_attach_args. If either of these members are non-NULL, direct configuration of the bus is being performed. Add an ISA_DIRECT_CONFIG() macro to test for this. * Drivers are not allowed to modify the isa_attach_args unless direct configuration is not being performed and the probe fucntion is returning success. * Adapt device drivers -- currently, all driver probe routines return "no match" if ISA_DIRECT_CONFIG() evaluates to true.
2002-01-08 00:46:56 +03:00
fdc->sc_ih = isa_intr_establish(ia->ia_ic, ia->ia_irq[0].ir_irq,
IST_EDGE, IPL_BIO, fdcintr, fdc);
Carve off the ISA configuration bits from the floppy driver. Driver is still ISA-specific, but we can attach ISA instances with different configuration mechanisms now.
2000-04-23 20:47:45 +04:00
fdcattach(fdc);
}