From owner-freebsd-stable Sun Nov 26 6:17:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.145.166]) by hub.freebsd.org (Postfix) with SMTP id 1B7A537B479 for ; Sun, 26 Nov 2000 06:14:47 -0800 (PST) Received: (qmail 59371 invoked from network); 26 Nov 2000 14:13:29 -0000 Received: from d306-5b.gdorm.yzu.edu.tw (@140.138.34.86) by www.mmlab.cse.yzu.edu.tw with SMTP; 26 Nov 2000 14:13:29 -0000 Date: Sun, 26 Nov 2000 22:13:55 +0800 (CST) From: Tai-hwa Liang To: Soren Schmidt Cc: Subject: Re: 4.2-RELEASE ata0-master probe failed(solved) In-Reply-To: <200011261323.OAA38044@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Nov 2000, Soren Schmidt wrote: [...] > > /* if drive is busy it didn't interrupt */ > > if (inb(scp->altioaddr) & ATA_S_BUSY) > > { > > /* clear interrupt */ > > inb(scp->ioaddr + ATA_STATUS); > > return; > > } > > This effectively disables the whole purpose of using the "alternative > status" register. Using the alt reg does not clear the interrupt > and we do not want to if this drive didn't interrupt. So this hack > breaks the driver on systems with more than one controller on > an interrupt (which is quiet common nowadays). > Your problem might be that the altioaddr is not correct, so we get > bogus status from it... Whoops.... I'm wondering about whether there is any fix to get the correct altioaddr on my laptop? > [...] > -- Regards, Tai-hwa Liang Multimedia Laboratory, Dept. of Computer Science & Engineering Yuan Ze University Taiwan, Republic of China To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message