linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Christian Brandt <brandtc@psi5.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Highpoint DC7280
Date: Mon, 18 Jun 2012 21:28:01 -0600	[thread overview]
Message-ID: <4FDFF1C1.4060808@gmail.com> (raw)
In-Reply-To: <4FDEDE3A.7030507@psi5.com>

On 06/18/2012 01:52 AM, Christian Brandt wrote:
> My company got hold of a Highpoint DC7280 for evaluation purposes. As we
> weren't that much impressed - mostly due abysmal propetiary drivers and
> support - I got it as a toy gift to play at home.
>
> Abstract in novella form: it is a dirt cheap 32 Port SATA-Controller. It
> features eight Marvell Chips each with a four port SATA Port Multiplier.
> Highpoint has abandoned all support (as usual) right a week before
> releasing it and the driver - dated 2011-06 - needs even some fiddling
> to compile under 3.0. Then it crashed upon writing. Besides that it is
> not THAT bad... gets around 250MB/s per Controller even with all eight
> controllers under maximum load.
>
> Is anyone else poking it with a stick?
>
> [1] http://www.highpoint-tech.cn/PDF/DC7280/DC7280_DS.pdf
>
> [2]
> http://www.highpoint-tech.com/BIOS_Driver/DC7280/driver/Linux/dc7280-linux-src-v1.0-110621-1313.tar.gz
>   (if KERNELVERSION==2.6 then... ok, so much about that one...)
>

What does lspci -vv show for that board?

It looks like that driver contains a binary blob so who knows what it is 
actually doing internally.

  parent reply	other threads:[~2012-06-19  3:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  7:52 Highpoint DC7280 Christian Brandt
2012-06-18 18:58 ` Mark Lord
2012-06-19  3:28 ` Robert Hancock [this message]
2012-06-27 16:27   ` Christian Brandt
2012-06-28  5:30     ` Robert Hancock

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=4FDFF1C1.4060808@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=brandtc@psi5.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).