All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Clear.Zhang@uli.com.tw
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	andrebalsa@mailingaddress.org, Peer.Chen@uli.com.tw,
	Emily.Jiang@uli.com.tw, Eric.Lo@uli.com.tw
Subject: Re: [patch] scsi/libata: correct bug for ULi M5281
Date: Sat, 11 Dec 2004 14:15:39 -0500	[thread overview]
Message-ID: <41BB475B.1000202@pobox.com> (raw)
In-Reply-To: <OF518056F7.FB1438A8-ON48256F64.0024A22B@uli.com.tw>

Clear.Zhang@uli.com.tw wrote:
> Hi, Jeff
> 
> The sata_uli patch for m5281 looks fine,but some of M5281 chip's PHY
> is not stable sometime, so it need a workaround to correct the bug.
> 
> patch_M5281workaround is just for it.
> 
> The patch is applied to kernel 2.6.9. Pleases apply to new kernels, thanks
> a lot.
> 
> Signed-off-by: Clear Zhang <Clear.Zhang@uli.com.tw>

I'm afraid I must reject this patch.  We do not wish to put
hardware-specific workarounds in libata-core.c or libata-scsi.c.

I would suggest either
(a) finding a way to add the workaround to sata_uli.c, or
(b) finding the "root cause" of the problem, and determine why the
libata code is insufficient.

Two suggestions I have while investigating your problem:
1) Replacing the ->phy_reset() hook may allow you to solve the problem
in sata_uli.c.
2) It is entirely possible that we need to add additional error handling
code to libata, including hooks back into the low-level driver (such as
sata_uli.c).

Regards,

	Jeff



  reply	other threads:[~2004-12-11 19:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  6:45 [patch] scsi/libata: correct bug for ULi M5281 Clear.Zhang
2004-12-11 19:15 ` Jeff Garzik [this message]
     [not found] <OF72031848.8565651F-ON48256F6A.0025361E@uli.com.tw>
2005-02-06  4:43 ` Jeff Garzik
     [not found] <OF934C846F.FCC47C36-ON48256FA0.0024A886@uli.com.tw>
2005-02-06  7:08 ` Jeff Garzik

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=41BB475B.1000202@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=Clear.Zhang@uli.com.tw \
    --cc=Emily.Jiang@uli.com.tw \
    --cc=Eric.Lo@uli.com.tw \
    --cc=Peer.Chen@uli.com.tw \
    --cc=andrebalsa@mailingaddress.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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.