linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Li <jon@ngndg.com>
To: linux-ide@vger.kernel.org
Subject: Sata-MV, Intergated Sata Device Support
Date: Sun, 15 Apr 2007 16:51:24 -0500	[thread overview]
Message-ID: <1176673884.5109.30.camel@Desktop> (raw)

Hello,

I am curious as to whether there are plans to add support for integrated
sata devices.  I personally want to add support for a 60x1C0 based
device (pci:id = 0x5182).  I think adding support should be relatively
simple, except for a few issues outlined below.

In the original mvSata.c (ver3.4) that has 0x5182 support, the config
space is as such:

case MV_SATA_DEVICE_ID_5182:
        pAdapter->numberOfChannels = MV_SATA_5182_PORT_NUM;
        pAdapter->numberOfUnits = 1;
        pAdapter->portsPerUnit = 2;
        pAdapter->sataAdapterGeneration = MV_SATA_GEN_IIE;
        /*The integrated sata core chip based on 60x1 C0*/
        pAdapter->chipIs60X1C0 = MV_TRUE;
        pAdapter->hostInterface = MV_HOST_IF_INTEGRATED;
        pAdapter->mainMaskOffset = 0x20024; /*the iobaseaddress is
0x60000*/
        pAdapter->mainCauseOffset = 0x20020;
        break;

I have not yet figured out how all these values are defined in sata-mv.c
(ver 0.8).  Specifically, where do I define "numberOfChannels" which
should equal 2, and "numberOfUnits" which obviously equals 1?

I have a current config space (not completed) for sata-mv.c which is:

	{  /* chip_5182 */
		.sht		= &mv_sht,
		.flags		= (MV_COMMON_FLAGS | MV_6XXX_FLAGS |
				   MV_FLAG_DUAL_HC),
		.pio_mask	= 0x1f,	/* pio0-4 */
		.udma_mask	= 0x7f,	/* udma0-6 */
		.port_ops	= &mv6_ops,
	},

I believe according to the new structure in sata-mv.c,
HC_MAIN_IRQ_CAUSE_OFS should equal 0x20020 and HC_MAIN_IRQ_MASK_OFS
should equal 0x20024 for the 0x5182 device.

My final question is how to implement the MV_HOST_IF_INTEGRATED flag?
Is this already implemented and renamed in sata-mv.c?  Or do I need to
also add the routines?


Thanks in advance.


Regards,
-- 
Jon Li <jon@ngndg.com>
Next Generation NAS Development Group


             reply	other threads:[~2007-04-15 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15 21:51 Jon Li [this message]
2008-02-25 23:40 ` Sata-MV, Intergated Sata Device Support Jeff Garzik
2008-02-26  0:07   ` Mark Lord
2008-02-26  0:17     ` Jeff Garzik
2008-02-26 11:39       ` saeed
2008-02-26 15:55         ` Mark Lord
2008-03-04 18:26           ` Mark Lord
2008-03-04 18:42           ` Byron Bradley
2008-03-04 21:18             ` Mark Lord
2008-03-05 13:07               ` 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=1176673884.5109.30.camel@Desktop \
    --to=jon@ngndg.com \
    --cc=linux-ide@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 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).