All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] DME1737 specsheet dead end.
Date: Wed, 20 Sep 2006 20:18:14 +0000	[thread overview]
Message-ID: <20060920221814.5925c7ee.khali@linux-fr.org> (raw)
In-Reply-To: <4503968B.8010703@sandeen.net>

Hi Eric,

> FYI, DME1737 specsheet (a.k.a. Asus A8000) is apparently not available to mere 
> mortals... conversation follows:

I didn't know the SMSC DME1737 and the Asus A8000 were the same chip.
How did you find out?

> ---
> 
> REQUEST INFORMATION
> 
> Hi, I'm looking for programming information on
> the SMSC DME1737 SUPER I/O WITH TEMPERATURE chip.
> 
> I've found overview datasheets but no specific information.  Is such a document
> available?   I'd like to extend the sensor monitoring application used in Linux
> to fully support your chip.
> 
> Thanks!
> 
> -Eric
> 
> RESOLUTION INFORMATION
> 
> 07/25/2006 09:00 AM TWalter:
> 
> Eric,
> 
> Who is the end customer requesting the Linux support?
> 
> Our DME1737 Datasheet requires a NDA (Non Disclosure Agreement) with a major OEM
> to process through our legal department.   I can not send it out without their 
> approval.

This is sad news, and not very smart from SMSC. Hardware monitoring
isn't exactly a bleeding edge area, nothing really exciting is going
on. Without a datasheet we can't support their chip, all they'll get is
a bunch of angry users who will make sure to stay away from SMSC chips
in the future.

I've updated our device information page.

-- 
Jean Delvare


  reply	other threads:[~2006-09-20 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10  4:37 [lm-sensors] DME1737 specsheet dead end Eric Sandeen
2006-09-20 20:18 ` Jean Delvare [this message]
2006-09-20 20:21 ` Eric Sandeen
2006-09-21  6:14 ` Jean Delvare

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=20060920221814.5925c7ee.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.