linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem
Date: Mon, 14 May 2007 11:10:09 +0200	[thread overview]
Message-ID: <46482771.4080602@gmail.com> (raw)
In-Reply-To: <20070513050522.88081.qmail@web52609.mail.re2.yahoo.com>

Srihari Vijayaraghavan wrote:
> --- Tejun Heo <htejun@gmail.com> wrote:
>> Srihari Vijayaraghavan wrote:
>>>> Oh well, that's the price you have to pay when you 1. have a device
>>>> which can't access memory above 4G but 2. don't have IOMMU to do it for
>>>> the device.  If performance becomes problem, you can always get a
>>>> not-so-expensive external controller which can do 64.
> 
> Can the Skymaster S3132, based on Sil3132,
> (http://umart.net/au/product_info.php?cPath=21_211&products_id=106108) do 64
> bit DMA on Linux?

Yeah, sil3124/32 can do 64bit alright.

> If so, I'm happy to buy that to isolate whether the current problem is limited
> to SB600 SATA controller alone on AMD690G chipset.

I'm too.  Please let me know when you find out.  :-P

> It'd be nice if somebody from AMD/ATI could confirm the 64 bit DMA capability
> of SB600 SATA controller. (I observe a few AMD/ATI folks have been submitting
> a few patches on LKML lately, so who knows.)

Maybe you can cc the ATI person here if you know the address.

> PS: FWIW, SB600 with your ahci fix has been working fine for the past week.
> Thank you for that.

Great.

-- 
tejun

  reply	other threads:[~2007-05-14  9:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <754241.548.qm@web52606.mail.re2.yahoo.com>
2007-05-06  9:33 ` ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem Tejun Heo
2007-05-07 20:37   ` Srihari Vijayaraghavan
2007-05-08  8:39     ` Tejun Heo
2007-05-08  9:35       ` Srihari Vijayaraghavan
2007-05-08 11:12         ` Tejun Heo
2007-05-08 11:16           ` Tejun Heo
2007-05-08 12:42             ` Srihari Vijayaraghavan
2007-05-08 12:39           ` Srihari Vijayaraghavan
2007-05-08 13:35             ` Tejun Heo
2007-05-08 15:00               ` Conke Hu
2007-05-08 15:03                 ` Tejun Heo
2007-05-13  5:05               ` Srihari Vijayaraghavan
2007-05-14  9:10                 ` Tejun Heo [this message]
2007-05-18 12:39                   ` Srihari Vijayaraghavan
2007-05-18 12:46                     ` Tejun Heo
2007-05-18 13:18                     ` [PATCH] ahci: disable 64bit dma on sb600 Tejun Heo
2007-05-18 14:19                       ` Srihari Vijayaraghavan
2007-05-18 14:23                       ` Tejun Heo
2007-05-21 23:58                         ` Jeff Garzik
2007-05-08  9:40 ASUS M2A-VM - AMD690G - SB600 Non-Raid-5 SATA - problem Srihari Vijayaraghavan
  -- strict thread matches above, loose matches on Subject: below --
2007-05-02 12:32 Srihari Vijayaraghavan
2007-05-03 14:44 ` Tejun Heo
2007-05-04  1:48   ` Srihari Vijayaraghavan
2007-05-04  6:41     ` Tejun Heo

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=46482771.4080602@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sriharivijayaraghavan@yahoo.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).