From: Albert Lee <albertcc@tw.ibm.com>
To: r.brandstaedter@gmx.at
Cc: albertl@mail.com, linux-ide@vger.kernel.org,
Unicorn Chang <uchang@tw.ibm.com>
Subject: Re: ASUS A8V Deluxe, x86_64
Date: Mon, 14 Aug 2006 14:31:00 +0800 [thread overview]
Message-ID: <44E018A4.3000907@tw.ibm.com> (raw)
In-Reply-To: <200608101056.06254.r.brandstaedter@eunet.at>
Reinhard Brandstädter wrote:
> On Thursday 10 August 2006 09:37, Albert Lee wrote:
>
>>Reinhard Brandstädter wrote:
>>
>>>On Tuesday 16 May 2006 14:57, Albert Lee wrote:
>>>
>>>>Reinhard has a Plextor PX-712SA + svia.
>>>>Maybe he can also help to check whether the patch fixes the problem on
>>>>his box.
>>>
>>>What I finally ended up with was solving the problem on the hardware
>>>side:
>>>
>>>The Plextor PX-712SA is a normal ATA device wich a IDE:SATA adapter
>>>plugged in at the back. I openend the DVDR Device (2 srews at the back)
>>>repoved the adapter (1 screw) and then u get the normal IDE Interface
>>>(with master/slave jumpers, audio interface and normal ower plug). You
>>>can use this device on an normal IDE interface then. Works perfect for
>>>me, maybe the 716SA Drive is similar
>>>This was the only solution that fixed the problem for me, any submitted
>>>kernel patches didn't work.
>>
>>I'm curious what's the PATA-to-SATA bridge chip used on the Plextor
>>PX-712SA. (Maybe it is not compatible with the VIA chip.)
>>Could you please check the IC on the IDE-SATA adapter?
>
>
> On the IC it reads:
> 88SA8040-TBC
> AP039208.3
> 0432 B0S
>
> I also attached a picture of the IC.
>
Hi Reinhard,
It's a Marvell 88SA8040. I have a Marvell 88SA8040 bridge at hand and
the bridge has been tested with SiI 3112 and it works ok with SiI 3112
and several CD-ROM drives.
Don't know whether the Marvell 88SA8040 works with SVIA.
Unicorn (on the cc list) has a VIA VT6421 SATA adapter. Will try
connecting the Marvell 88SA8040 with the VIA VT6421 and see if it works.
--
albert
next prev parent reply other threads:[~2006-08-14 6:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 11:45 ASUS A8V Deluxe, x86_64 Fortier,Vincent [Montreal]
2006-05-16 11:45 ` Fortier,Vincent [Montreal]
2006-05-16 12:05 ` Tejun Heo
2006-05-16 12:57 ` Albert Lee
2006-05-16 13:11 ` Tejun Heo
2006-08-10 6:46 ` Reinhard Brandstädter
2006-08-10 7:37 ` Albert Lee
2006-08-10 8:56 ` Reinhard Brandstädter
2006-08-14 6:31 ` Albert Lee [this message]
2006-05-16 14:32 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 14:03 Fortier,Vincent [Montreal]
2006-05-18 10:57 Fortier,Vincent [Montreal]
2006-05-18 10:57 ` Fortier,Vincent [Montreal]
2006-05-18 11:25 ` Albert Lee
2006-05-17 11:02 Fortier,Vincent [Montreal]
2006-05-18 3:29 ` Tejun Heo
2006-05-18 5:28 ` Albert Lee
2006-05-16 14:43 Fortier,Vincent [Montreal]
2006-05-16 14:43 ` Fortier,Vincent [Montreal]
2006-05-16 15:40 ` Tejun Heo
2006-05-16 14:40 Fortier,Vincent [Montreal]
2006-05-16 14:40 ` Fortier,Vincent [Montreal]
2006-05-15 18:23 Fortier,Vincent [Montreal]
2006-05-15 19:08 ` Andi Kleen
2006-05-15 19:23 ` Marko Macek
2006-05-15 19:41 ` Andi Kleen
2006-05-15 17:12 Fortier,Vincent [Montreal]
2006-05-15 12:05 Fortier,Vincent [Montreal]
2006-05-15 17:02 ` Greg KH
2006-05-23 6:10 ` Aaron Gyes
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=44E018A4.3000907@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=albertl@mail.com \
--cc=linux-ide@vger.kernel.org \
--cc=r.brandstaedter@gmx.at \
--cc=uchang@tw.ibm.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 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.