Ted, from my limited experience with FreeBSD & ISA PnP cards (I'm fiddling around with the 3COM Etherlink III driver) I would suggest that you need to write a driver to talk to the card simply because you have to be able to retrieve the card settings. However I found the ISA PnP functionality extremly easy to use considering that I am not a FreeBSD driver guru. That said I would estimate that writing the PnP Init part of the driver shouldn't take more than 100-150 lines of C.
The main problem would be adding all the functionality that your Windows driver already incorporates ... Timo On Thu, Aug 12, 1999 at 05:25:05PM -0400, tbusw...@acadia.net wrote: > > Hi, > > What is the path of least resistance for getting an unsupported ISA > PnP device to the point where you can do I/O to it (inb,outb)? > Do I need a driver, or is there some general purpose way for > getting the device "up" to the point that you can use /dev/io and a user > space application? (on -current) > > If I need to write a driver, would a device driver that just maps the > device be considered useful (feasible to implement?)? > > This specific device is a "winmodem" which I believe I have enough > hardware documentation to fiddle with, once I get past the ISA PnP > interface. > > Thanks, > -Ted > (ISA PnP newbie) > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
