Date: Fri, 5 Feb 1999 08:30:03 -0500 (EST) From: "Viren R. Shah" <viren@rstcorp.com> To: ONE-MO <onemo@jps.net> Cc: stable@FreeBSD.ORG Subject: Re: Compaq ida driver patch Message-ID: <199902051330.IAA01320@jabberwock.rstcorp.com> In-Reply-To: <36BA899D.C780DF99@jps.net> References: <36B8DA72.F58BB5D1@jps.net> <36B956B7.4299FC0@doc.ic.ac.uk> <199902041438.JAA44908@jabberwock.rstcorp.com> <36B9EECF.DB2F9F08@jps.net> <199902041938.OAA53509@jabberwock.rstcorp.com> <36BA899D.C780DF99@jps.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "MO" == ONE-MO <onemo@jps.net> writes:
MO> OK, here's the latest status.
MO> I used your hacked ida.c, noticing a couple changes in addition
MO> to the port address. I rebuilt my kernel with the ida port
MO> specified as 0x1000. Upon
MO> booting, I did NOT receive the same process lockup upon accessing the
Good. That's a start.
MO> Just for fun, I booted my kernel.old (the last kernel built with
MO> Mark's original ida.c) and I again received the lockup upon
MO> access.
MO> Thanks for the help, now if only I can determine exactly what it was the
MO> corrected it....
In addition to setting the port, I think I also set the slot # for the
Compaq controller (though this is also calculated as a function of
the port address). Finally, in ida_eisa_attach() I set :
dev->id_ointr = idaintr;
These are the only changes, I think. I don't have a virgin copy of
ida.c to diff against.
MO> MO!
Viren
--
Viren R. Shah, {viren @ rstcorp . com}
"SCSI *is* God's bus and it's hardly an old-fashioned (or academic)
attitude to think so, it's simply an informed attitude."
-- Jordan Hubbard
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902051330.IAA01320>