All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: More Promise chipset specs opened
Date: Thu, 02 Nov 2006 00:46:16 -0500	[thread overview]
Message-ID: <45498628.9090105@garzik.org> (raw)
In-Reply-To: <45497E3A.6060103@garzik.org>

Jeff Garzik wrote:
> Promise has given me permission to post hardware programming info for 
> one of their chips (Linux driver: sata_promise), PDC20319.  This also 
> marks the first open chipset for Promise (AFAIK), so let's give them a 
> round of applause.

I missed an email from Promise which supplied even more chipset docs to 
open.  Whoops.  The entire line supported by sata_promise.c should now 
be open:

2037x:
http://gkernel.sourceforge.net/specs/promise/pdc2037x%20series%20development%20guide.pdf.bz2

20319 (updated link, updated doc):
http://gkernel.sourceforge.net/specs/promise/pdc20319%20development%20guide.pdf.bz2

205xx (the newer NCQ chips):
http://gkernel.sourceforge.net/specs/promise/pdc205xx%20development%20guide%201.0.pdf.bz2

Cheers,

	Jeff



  reply	other threads:[~2006-11-02  5:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02  5:12 Promise 20319 chipset specs opened Jeff Garzik
2006-11-02  5:46 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-04 10:11 More Promise " otto Meier
2006-11-04 13:17 ` Jeff Garzik
2006-11-05  8:58   ` otto Meier
2006-11-05  9:41     ` Jeff Garzik
2006-11-05 10:11       ` otto Meier

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=45498628.9090105@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.