mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aric Cyr <acyr@alumni.uwaterloo.ca>
To: Christian Kroll <christian.kroll@bglug.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_sil 3112 activity LED patch
Date: Fri, 15 Jul 2005 14:57:43 +0900	[thread overview]
Message-ID: <20050715055743.GA8041@alumni.uwaterloo.ca> (raw)
In-Reply-To: <1121393712.4770.6.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]

On Fri, Jul 15, 2005 at 04:15:12AM +0200, Christian Kroll wrote:
> I have tested the patch against my DawiControl DC-150 RAID controller
> which is basically an add-on card with a SiI 3112 ASIC and a flash ROM.
> The activity LED of my case is directly connected to the add-on card.
> 
> Unfortunately your patch doesn't have any effect on the LED. The
> activity LED gets turned on by the card's BIOS at boot time and
> continues to shine until I shut down the computer.
> On the other hand it did not erase my Flash ROM and I haven't spotted
> any data loss so far.

No data loss is a good thing!  That was my biggest worry, as I have no
documentation for the addon card case.  Out of curiosity, did the LED
usage change at all before and after the patch, or was it totally
unaffected.  I would guess the latter.

Unfortunately, what documentation I do have shows (briefly) that add
on cards implement their LED via a different mechanism.  If I knew the
addresses for the flash read and write strobes (FL_RDN and FL_WRN), I
might be able to work something out.  So as it stands, there is not
much hope for the people with addon cards.

> If you require more information, don't hesitate to contact me.

Thanks, I will.  I have emailed Silicon Image in the (slim) chance
that they will provide me with the information I require.  If they
come through then I might be able to whip something up and have you
test it.

If anyone has any data on the 3112a (or 3512 as I believe they are
register compatible) and isn't bound by an NDA, I'd like to hear from
you.

-- 
Aric Cyr <acyr at alumni dot uwaterloo dot ca>    (http://acyr.net)
gpg fingerprint: 943A 1549 47AC D766 B7F8  D551 6703 7142 C282 D542

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-07-15  5:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15  2:15 Christian Kroll
2005-07-15  5:57 ` Aric Cyr [this message]
2005-07-15 10:34   ` Christian Kroll
  -- strict thread matches above, loose matches on Subject: below --
2005-07-06  2:51 Aric Cyr
2005-07-06 15:07 ` Jeff Garzik
2005-07-07 12:47   ` Jens Axboe
2005-07-07 14:23     ` Aric Cyr
2005-07-07 15:11       ` Jens Axboe

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=20050715055743.GA8041@alumni.uwaterloo.ca \
    --to=acyr@alumni.uwaterloo.ca \
    --cc=christian.kroll@bglug.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®