Date: Sun, 10 Jun 2001 10:57:43 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Sergey Babkin <babkin@bellatlantic.net> Cc: j mckitrick <jcm@FreeBSD-uk.eu.org>, "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: <Pine.BSF.4.33.0106101056090.3242-100000@herring.nlsystems.com> In-Reply-To: <3B2164B3.84284526@bellatlantic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Jun 2001, Sergey Babkin wrote: > j mckitrick wrote: > > > > 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'. > > As Doug Rabson said, write an 'identify' routine. Look at the > ep driver for an example. And my artile in DaemonNews > (www.daemonnews.org) from I think August 2000 or somewhere around > that time gives some description of the newbussified ISA drivers. > It should also be included into the Handbook by now. Actually, the ex driver does have an identify method. The issue is that the identify method uses 'unallocated' ports to do its search. It ought to allocate them, do its tests and release them for the real probe but it gets messy due to the fact that a device instance doesn't exist yet. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 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?Pine.BSF.4.33.0106101056090.3242-100000>