mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Corentin Chary <corentin.chary@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: VT6421 problems with sata_via (VIA data sheets)
Date: Wed, 14 Oct 2009 15:59:31 +0200	[thread overview]
Message-ID: <4AD5D943.9020507@gnumonks.org> (raw)
In-Reply-To: <20091011141638.616084c0@lxorguk.ukuu.org.uk>

Hi Alan,

Alan Cox wrote:

>> I recently needed some more space and bought a Deskstar 7K1000.B for my server.
>> The motherboard is old, and did not have SATA port, so I added a
>> VT6421 PCI SATA controller.
> 
> Lots of 6421 setups do not work on Linux full stop. I've asked VIA
> several times for the relevant data sheet/info to fix this and they've
> never done more than acknowledge receipt of the mail.

Whom did you e-mail?

The document is available from
ftp://ftp.vtbridge.org/Docs/Storage/DS_VT6421A_100_CCPL.PDF
for almost one year now.

If you requested it, maybe it was put there but somebody just forgot to
send follow-up mail to you.

To anyone working on Linux or other Free Software regarding VIA
hardware:  If you need documentation, or if you have any other issues,
please contact me.  I am the Liaison and I can talk with various people
and departments inside VIA.

There are some things where VIA has no documentation, and there are
other parts like video acceleration where documentation cannot be
published due to 3rd party patents and patent licensing schemes.

But for general hardware like storage controller, north/southbridge,
audio codecs, ... the documentation is possible to be released without NDA.

--
  Harald Welte <laforge@gnumonks.org>

      parent reply	other threads:[~2009-10-14 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11  9:54 VT6421 problems with sata_via Corentin Chary
2009-10-11 13:16 ` Alan Cox
2009-10-11 14:57   ` Corentin Chary
2009-10-14  7:26   ` Corentin Chary
2009-10-14 13:59   ` Harald Welte [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=4AD5D943.9020507@gnumonks.org \
    --to=laforge@gnumonks.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=corentin.chary@gmail.com \
    --cc=jgarzik@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®