From: Tejun Heo <htejun@gmail.com>
To: sam song <sam_song@usish.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru
Date: Fri, 30 Nov 2007 15:47:23 +0900 [thread overview]
Message-ID: <474FB1FB.9050904@gmail.com> (raw)
In-Reply-To: <009901c8331c$30d2c780$6539a8c0@usish.com.cn>
sam song wrote:
>> sam song wrote:
>>>> sam song wrote:
>>>>> Attached pls see the details debug log on SUSE Linux Enterprise 10 I
>>> just
>>>>> did. As for code, I will send to you in private for it is kind of poor
>>> and
>>>>> confidential. Really sorry for that.
>>>> Aieee... SLES10. Is it SLES10SP1 or just SLES10. I'm fairly sure
>>>> passthrough support is broken in SLES10. Can you please try the
> program
>>>> on vanilla kernel (2.6.23.X)?
>>> Well, how to know the distribution is SLES10SP1 or SLES10?
>> On my machine...
>>
>> $ cat /etc/SuSE-release
>> openSUSE 10.3 (X86-64)
>> VERSION = 10.3
>
> Here is mine.
>
> IT-0010737:/ # cat /etc/SuSE-release
> SUSE Linux Enterprise Server 10 (i586)
> VERSION = 10
Yeah, that's SLE10 so no wonder ATA passthrough is broken. Please try
with the vanilla kernel.
--
tejun
next prev parent reply other threads:[~2007-11-30 6:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 10:34 Issuing a vendor specific ATA cmd on SATA Disk via ATA Pass Thru sam song
2007-11-30 1:18 ` Tejun Heo
2007-11-30 3:33 ` sam song
2007-11-30 6:12 ` Tejun Heo
2007-11-30 6:29 ` sam song
2007-11-30 6:33 ` Tejun Heo
2007-11-30 6:42 ` sam song
2007-11-30 6:47 ` Tejun Heo [this message]
2007-11-30 7:01 ` sam song
2007-11-30 8:22 ` Tejun Heo
2007-12-03 10:20 ` sam song
2007-12-04 0:46 ` Tejun Heo
2007-12-04 1:32 ` sam song
2007-12-04 2:21 ` Tejun Heo
2007-12-05 1:43 ` Tejun Heo
2007-12-05 2:39 ` sam song
2007-12-05 3:16 ` Tejun Heo
2008-03-11 3:17 ` sam song
2008-03-11 3:21 ` 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=474FB1FB.9050904@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sam_song@usish.com \
/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).