linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Holger Hasselmann <hhasselm@web.de>
Cc: linux-ide@vger.kernel.org, Shane.Huang@amd.com
Subject: Re: Gigabyte GA-MA69VM-S2 can't do 64bit DMA
Date: Fri, 18 Sep 2009 09:43:13 +0900	[thread overview]
Message-ID: <4AB2D7A1.8060909@gmail.com> (raw)
In-Reply-To: <4AB2B463.4010408@web.de>

Hello,

Holger Hasselmann wrote:
> I have tried the 2.6.31-git2 and this is  the dmesg output :
> 
> ibata version 3.00
> 
> ahci 0000:00:12.0: version 3.0_
> ahci 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> ahci 0000:00:12.0: Fujitsu-Siemens AMILO Pa 2510: this board can't do 64bit
> DMA, forcing 32bit
> ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
> ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
> ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part
> It's correct now.

Cool, patch posted with the id string shortened.

> By the way, I was wondering, because I am a lucky owner of the
> GA-MA69VM-S2 board.  I have seen it when I was trying out the issue
> with my laptop and read the name of the kernel patch.  You will not
> believe it, on my board with the bios version F8 I do not have any
> issue with the plain 2.6.31 kernel without patch.  Thanks again,
> Holger

I'm confused here.  Gigabyte GA-MA69VM-S2 can't do 64bit DMA either?

Thanks.

-- 
tejun

  reply	other threads:[~2009-09-18  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 17:50 Gigabyte GA-MA69VM-S2 can't do 64bit DMA Holger Hasselmann
2009-09-15 19:09 ` Tejun Heo
2009-09-16  9:19   ` Holger Hasselmann
2009-09-16 10:49     ` Tejun Heo
2009-09-17 22:12       ` Holger Hasselmann
2009-09-18  0:43         ` Tejun Heo [this message]
2009-09-18  1:17           ` Huang, Shane
2009-09-18  8:09             ` 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=4AB2D7A1.8060909@gmail.com \
    --to=htejun@gmail.com \
    --cc=Shane.Huang@amd.com \
    --cc=hhasselm@web.de \
    --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 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).