From: Tejun Heo <htejun@gmail.com>
To: Shane Huang <Shane.Huang@amd.com>
Cc: Andrew Paprocki <andrew@ishiboo.com>,
sriharivijayaraghavan@yahoo.com.au, linux-ide@vger.kernel.org
Subject: Re: About forcing 32bit DMA patch for AMD690G(SB600)
Date: Fri, 01 Feb 2008 17:23:47 +0900 [thread overview]
Message-ID: <47A2D713.1010203@gmail.com> (raw)
In-Reply-To: <B90463BC30D2E446BA423D888DC85E5020F102@sshaexmb1.amd.com>
Shane Huang wrote:
> As Tejun mentioned, the test result on my SB600 engineering board
> (RS690 A12 +SB600 A21) is a little different from the result of Srihari.
> But I do not have other SB600 boards especially ASUS M2A-VM to do
> further debug. So if you can provide us your test result, that's really
> good.
My 5 cents: Just order the board. These stock PC hardware are too cheap
these days, it doesn't make any sense to try to debug somewhat difficult
problem remotely if the hardware is available on the market. Even if
you have to spend your own money, it will be money well spent compared
to the time and effort you'll have to spend in comparison - hardware is
just too cheap.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-02-01 8:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 7:44 About forcing 32bit DMA patch for AMD690G(SB600) Shane Huang
2008-01-24 3:53 ` Shane Huang
2008-01-25 0:21 ` Tejun Heo
2008-01-25 4:19 ` Andrew Paprocki
2008-01-25 5:50 ` Tejun Heo
2008-01-25 20:57 ` Konstantin A. Lepikhov
2008-01-25 23:13 ` Jeff Garzik
2008-01-26 1:24 ` Tejun Heo
2008-01-31 9:14 ` Shane Huang
2008-01-26 1:07 ` Andrew Paprocki
2008-01-31 8:53 ` Shane Huang
2008-02-01 8:23 ` Tejun Heo [this message]
2008-02-02 4:04 ` Shane Huang
2008-02-10 20:55 ` Srihari Vijayaraghavan
-- strict thread matches above, loose matches on Subject: below --
2008-01-29 20:10 Kelly Anderson
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=47A2D713.1010203@gmail.com \
--to=htejun@gmail.com \
--cc=Shane.Huang@amd.com \
--cc=andrew@ishiboo.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).