Date: Fri, 8 Jun 2001 04:02:11 +0100 From: j mckitrick <jcm@FreeBSD-uk.eu.org> To: Doug Rabson <dfr@nlsystems.com> Cc: "Matthew N. Dodd" <winter@jurai.net>, Warner Losh <imp@village.org>, Mike Smith <msmith@FreeBSD.ORG>, freebsd-hackers@FreeBSD.ORG Subject: Re: newbussifying drivers Message-ID: <20010608040211.A61278@dogma.freebsd-uk.eu.org> In-Reply-To: <Pine.BSF.4.33.0106071238040.18103-100000@herring.nlsystems.com>; from dfr@nlsystems.com on Thu, Jun 07, 2001 at 12:39:29PM %2B0100 References: <Pine.BSF.4.21.0106070240550.26121-100000@sasami.jurai.net> <Pine.BSF.4.33.0106071238040.18103-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
| > > : How would you recommending fixing this, taken from the ex driver? | > > | > > By deleting it. | > | > Uh, what? | > | > Non PnP devices that can be autodetected should be autodetected. | > | > Relying on the user to wire down hints is silly. | | Probably they should provide an identify method to look for and create the | non-PnP devices. The actual probe method should be dumb and just use the | resources given to it (IMHO). Okay, there is something i'm not understanding here. In the ed driver, there are many possible cards, which each have different i/o ports, correct? The driver has a lot of probe routines, and it looks like they are just using different macros with hard-coded (#defined) port addresses. So, how do you CORRECTLY use the newbus calls to probe these ports? I am not running -current, so i do not have 'hints'. jcm -- "I drank WHAT ?!" - Socrates 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?20010608040211.A61278>