linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ryan Bourgeois <rgb005@latech.edu>
Cc: Linux IDE Mailing List <linux-ide@vger.kernel.org>
Subject: Re: Promise SX4[-M]
Date: Wed, 19 Oct 2005 22:58:02 -0400	[thread overview]
Message-ID: <435707BA.4050104@pobox.com> (raw)
In-Reply-To: <435703BE.602@latech.edu>

Ryan Bourgeois wrote:
> What's the latest status on the Promise SX4 cards?  Has anyone looked 
> into employing the onboard DRAM for anything yet?  I remember at one 
> point we had a nice little dialog going about this card, but I don't 
> know that it really amounted to anything.
> 
> Jeff, if nobody has done anything with this since back whenever, you 
> could pass to me what documentation you have for it and some of the 
> ideas you had for this card and I can see what I can do.  I think it'd 
> be an interesting project for me to start, time permitting.

NDAs (legal stuff) prevents passing around documentation.

I can certainly summarize what is public in the sata_sx4.c driver:

* one ATA engine per port, for executing ATA commands.
* each ATA engine operates on data in on-board RAM
* one HDMA engine, for copying data between host RAM and board RAM
* since there is only one HDMA engine but four ATA engines, its a bit of 
a bottleneck
* no SATA controls, the board uses PATA chips with a SATA bridge
* driver code uses a static memory layout I designed.  This will need to 
  be changed to a dynamic layout, most likely.

I can certainly answer any questions about the driver, and can answer 
questions about the hardware when it pertains to information necessary 
to develop and maintain the open source driver.

	Jeff



      reply	other threads:[~2005-10-20  2:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20  2:41 Promise SX4[-M] Ryan Bourgeois
2005-10-20  2:58 ` Jeff Garzik [this message]

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=435707BA.4050104@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rgb005@latech.edu \
    /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;
as well as URLs for NNTP newsgroup(s).