All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ognyan Kulev <ogi@fmi.uni-sofia.bg>
To: linux-ide@vger.kernel.org
Subject: Re: [BUG] OPTi 621, chipset revision 18, hangs with enabled DMA
Date: Sun, 01 Aug 2004 08:55:51 +0300	[thread overview]
Message-ID: <410C85E7.1070300@fmi.uni-sofia.bg> (raw)
In-Reply-To: <410BABE7.1040005@fmi.uni-sofia.bg>

Ognyan Kulev wrote:
> Alexander Atanasov replied to me privately and said it seems that 
> OPTi621 doesn't support DMA.  But after searching in Google, it looks 
> that there is some OPTi621 that supports DMA, although not 100% confirmed:

I've found the following code in NetBSD's src/sys/dev/pci/optiide.c:

	aprint_normal("%s: bus-master DMA support present",
	    sc->sc_wdcdev.sc_dev.dv_xname);

	/*
	 * XXXSCW:
	 * There seem to be a couple of buggy revisions/implementations
	 * of the OPTi pciide chipset. This kludge seems to fix one of
	 * the reported problems (PR/11644) but still fails for the
	 * other (PR/13151), although the latter may be due to other
	 * issues too...
	 */
	if (PCI_REVISION(pa->pa_class) <= 0x12) {
		aprint_normal(" but disabled due to chip rev. <= 0x12");
		sc->sc_dma_ok = 0;
	} else
		pciide_mapreg_dma(sc, pa);

The relevant PRs are:

http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=11644
http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=13151

Notice that revision of my OPTi is 18 (0x12, which is <= 0x12).  As 
scw@netbsd says in PR/13151, he developed the driver on revision 0x30, 
so I guess this "revision <= 0x12" check is the best we've got for now.

FreeBSD doesn't have anything special for this IDE: 
http://www.freebsd.org/releases/5.2.1R/hardware-i386.html#AEN65

Regards,
ogi

      reply	other threads:[~2004-08-01  5:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 11:41 [BUG] OPTi 621, chipset revision 18, hangs with enabled DMA Ognyan Kulev
2004-07-31 14:25 ` Ognyan Kulev
2004-08-01  5:55   ` Ognyan Kulev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=410C85E7.1070300@fmi.uni-sofia.bg \
    --to=ogi@fmi.uni-sofia.bg \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.