Date: Wed, 6 Jun 2001 01:04:26 +0200 From: Alexander Langer <alex@big.endian.de> To: j mckitrick <jcm@FreeBSD-uk.eu.org> Cc: Mike Smith <msmith@FreeBSD.ORG>, freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010606010426.C28586@zerogravity.kawo2.rwth-aachen.d> In-Reply-To: <20010605230032.B96188@dogma.freebsd-uk.eu.org>; from jcm@FreeBSD-uk.eu.org on Tue, Jun 05, 2001 at 11:00:32PM %2B0100 References: <20010605182151.A90883@dogma.freebsd-uk.eu.org> <200106052032.f55KWTj01513@mass.dis.org> <20010605230032.B96188@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake j mckitrick (jcm@FreeBSD-uk.eu.org):
> | It's pretty rare to need to bit-bang to find a device these days anyway;
> | you should probably be looking for PnP data or similar. This is what
> | hints are (basically) - manually-supplied PnP data.
> How would you recommending fixing this, taken from the ex driver?
> for (ioport = 0x200; ioport < 0x3a0; ioport += 0x10) {
This is exactly what Mike meant:
You manually set the correct I/O port in the hints file and then you
don't have to check for each port between 0x200 and 0x3a0.
Just bus_alloc_resource once and test for the card.
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010606010426.C28586>