Date: Fri, 08 Jun 2001 19:50:11 -0400 From: Sergey Babkin <babkin@bellatlantic.net> To: j mckitrick <jcm@FreeBSD-uk.eu.org> Cc: Doug Rabson <dfr@nlsystems.com>, "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: <3B2164B3.84284526@bellatlantic.net> References: <Pine.BSF.4.21.0106070240550.26121-100000@sasami.jurai.net> <Pine.BSF.4.33.0106071238040.18103-100000@herring.nlsystems.com> <20010608040211.A61278@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -SB 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?3B2164B3.84284526>