public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conke Hu <conke.hu@amd.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Luugi Marsan <luugi.marsan@amd.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Workaround for SB600 SATA ODD issue
Date: Sun, 05 Nov 2006 20:45:14 +0800	[thread overview]
Message-ID: <1162730714.8525.60.camel@localhost.localdomain> (raw)
In-Reply-To: <1162661809.3160.53.camel@laptopd505.fenrus.org>

On Sat, 2006-11-04 at 18:36 +0100, Arjan van de Ven wrote:
> On Fri, 2006-11-03 at 14:00 -0500, Luugi Marsan wrote:
> > From: conke.hu@amd.com
> > 
> > There was an ASIC bug in the SB600 SATA controller of low revision (<=13) and CD burning may hang (only SATA ODD has this issue, and SATA HDD works well). The patch provides a workaround for this issue.
> > 
> > Signed-off-by:  Luugi Marsan <luugi.marsan@amd.com>
> > 
> > --- linux-2.6.19-rc4-git5/drivers/ata/ahci.c.orig       2006-11-04 03:56:22.000000000 +0800
> > +++ linux-2.6.19-rc4-git5/drivers/ata/ahci.c    2006-11-04 04:20:36.000000000 +0800
> > @@ -189,6 +189,7 @@ struct ahci_host_priv {
> >         unsigned long           flags;
> >         u32                     cap;    /* cache of HOST_CAP register */
> >         u32                     port_map; /* cache of HOST_PORTS_IMPL reg */
> > +       u8                      rev;    /* PCI Revision ID */
> >  };
> >  
> 
> why put this into the ahci struct rather than in the pci device struct?
> In the place you use it you already have the pci device struct already..
> and it's really a pci device property so putting it in that struct makes
> a whole lot of sense conceptually anyway...
> 
> 

Hi Arjan,
    Yes, I also thought it's more reasonable to add "u8 rev;" to pci_dev
than to ahci_host_priv, but that will effect source code in large scope,
so I added it here :(
    Maybe I should resend a patch both for pci_dev and SB600 SATA at the
same time.


Best regards,
Conke Hu


  parent reply	other threads:[~2006-11-05 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 19:00 [PATCH 2/2] Workaround for SB600 SATA ODD issue Luugi Marsan
2006-11-04 12:52 ` Christoph Hellwig
2006-11-04 17:36 ` Arjan van de Ven
2006-11-04 18:35   ` Christoph Hellwig
2006-11-05 12:45   ` Conke Hu [this message]
2006-11-06 12:14 ` Tejun Heo
2006-11-08 13:30 ` 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=1162730714.8525.60.camel@localhost.localdomain \
    --to=conke.hu@amd.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luugi.marsan@amd.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