All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Andrew Morton <akpm@osdl.org>,
	davem@davemloft.net, htejun@gmail.com, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc6] sata_promise updates
Date: Tue, 21 Nov 2006 16:07:17 -0500	[thread overview]
Message-ID: <45636A85.40700@garzik.org> (raw)
In-Reply-To: <200611212057.kALKvL8n009798@harpo.it.uu.se>

Mikael Pettersson wrote:
> This patch updates the sata_promise driver as follows:
> - Correct typo in definition of PDC_TBG_MODE: it's at 0x41C not 0x41
>   in first-generation chips. This error caused PCI access alignment
>   exceptions on SPARC64, and on all platforms it disabled the expected
>   initialisation of TBG mode.
> - Prevent TBG mode and SLEW rate initialisation in second-generation chips.
>   These two registers have moved, TBG mode has been redefined, and
>   Promise's ulsata2 driver no longer attempts to initialise them.
> - Correct PCI device table so devices 0x3570, 0x3571, and 0x3d73 are
>   marked as 2057x (2nd gen) not 2037x (1st gen).
> - Correct PCI device table so device 0x3d17 is marked as 40518
>   (2nd gen 4 ports) not 20319 (1st gen 4 ports).
> - Correct pdc_ata_init_one() to treat 20771 as a second-generation chip.
>   (The 20771 classification is redundant as it is equivalent to 2057x.)
> 
> Tested on 0x3d75 (2nd gen), 0x3d73 (2nd gen), and 0x3373 (1st gen) chips.
> The information comes from the newly uploaded Promise SATA HW specs,
> Promise's ultra and ulsata2 drivers, and debugging on 3d75/3d73/3373 chips.
> 
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>

Looks pretty decent to me.  Two small nits:

1) no_tbg_slew_init should be a bit flag ("1 << 0") inside a 'flags' 
variable in struct pdc_host_priv.

2) Check pdc_ulsata2 again, I think the flash control register is 
programmed with a different value on SATAI versus SATAII.

	Jeff



  reply	other threads:[~2006-11-21 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 20:57 [PATCH 2.6.19-rc6] sata_promise updates Mikael Pettersson
2006-11-21 21:07 ` Jeff Garzik [this message]
2006-11-21 21:09   ` Jeff Garzik
2006-11-21 21:17 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-11-22 21:00 Mikael Pettersson
2006-11-28  8:25 ` Jeff Garzik
2006-11-22 21:00 Mikael Pettersson

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=45636A85.40700@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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.