linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: Thomas Renninger <trenn@suse.de>, Tejun Heo <tj@kernel.org>,
	Shem Multinymous <multinymous@gmail.com>,
	Elias Oltmanns <eo@nebensachen.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Laptop shock detection and harddisk protection
Date: Tue, 7 Oct 2008 22:40:11 +0200	[thread overview]
Message-ID: <20081007204011.GG6604@elf.ucw.cz> (raw)
In-Reply-To: <20080924051417.GA29993@kroah.com>


> > > > Code created by access to specs that were not allowed to be published in
> > > > GPL form by someone who wants to remain anonymous.
> > >
> > > That anonymous person may have problems if they signed NDA.
> > >
> > > I don't think they did, they even list the sources:
> > >
> > >  *  The embedded controller on ThinkPad laptops has a non-standard
> > > interface, *  where LPC channel 3 of the H8S EC chip is hooked up to IO
> > > ports *  0x1600-0x161F and implements (a special case of) the H8S LPC
> > > protocol. *  The EC LPC interface provides various system management
> > > services (currently *  known: battery information and accelerometer
> > > readouts). This driver *  provides access and mutual exclusion for the EC
> > > interface.
> > > *
> > >  *  The LPC protocol and terminology is documented here:
> > >  *  "H8S/2104B Group Hardware Manual",
> > >  * 
> > > http://documentation.renesas.com/eng/products/mpumcu/rej09b0300_2140bhm.pdf
> > >
> > > H8S chip seems to be documented.
> > Hmm, the EC is not directly used, but ACPI functions of the HP device are 
> > used.
> > For the HP ACPI device: the ACPI functions can *very easily* be re-engineered
> > (which is common for all laptop_acpi.ko drivers):
> > ALRD -> is used by the driver to read out registers of the accelerometer
> > ALWR -> is used by the driver to write a registers of the accelerometer
> > BTW: HP likes to have support for their device.
> > 
> > The acceleromter chip itself is docuemented in detail here:
> > http://www.st.com/stonline/products/literature/ds/12094/lis3lv02dl.pdf
> > 
> > I also do not see any concerns.
> > Greg: Can you please add this one or explain in more detail what else you like 
> > to see to get this integerated.
> 
> If you, or anyone else, writes a new driver from the published
> documents, that driver can be accepted.  It can not be based on the
> existing code written by Shem in any form.

Can you detail what "published" means?

Either I can take his sources on sourceforge.net (quite well known
place, right) as published information, or I could not use other well
known sources such as wikipedia.

Sources on sourceforge.net seem published-enough to me, and if you
insist they can't be used, you should provide some reasons...

[And no, just calling it "tainted" is not enough.]
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-10-07 20:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 16:59 Laptop shock detection and harddisk protection Tejun Heo
2008-09-10 19:43 ` Renato S. Yamane
2008-09-11 10:26 ` Austin Zhang
2008-09-11 11:18   ` Tejun Heo
2008-09-11 16:08 ` Shem Multinymous
2008-09-11 16:34   ` Tejun Heo
2008-08-17 19:48     ` Pavel Machek
2008-09-11 20:00     ` Elias Oltmanns
2008-08-17 19:51       ` Pavel Machek
2008-09-17 15:21         ` Elias Oltmanns
2008-09-17 19:36           ` Shem Multinymous
2008-09-11 20:25     ` Shem Multinymous
2008-08-17 19:30       ` Pavel Machek
2008-09-11 23:35       ` Tejun Heo
2008-09-12 16:59         ` Greg KH
2008-08-17 19:45           ` Pavel Machek
2008-09-17 18:04             ` Greg KH
2008-09-18 11:18               ` Pavel Machek
2008-09-19  9:03                 ` Thomas Renninger
2008-09-24  5:14                   ` Greg KH
2008-10-07 20:40                     ` Pavel Machek [this message]
2008-10-07 21:19                       ` Greg KH
2008-10-07 21:40                         ` Pavel Machek
2008-10-07 22:03                           ` Greg KH
2008-10-07 23:03                             ` Pavel Machek
2008-10-07 22:55                         ` Shem Multinymous
2008-09-15  8:29           ` Tejun Heo
2008-09-15 18:09             ` Shem Multinymous
2008-09-15 20:10               ` Tejun Heo
2008-09-14  4:41       ` Jeremy Fitzhardinge
2008-09-11 23:36     ` Henrique de Moraes Holschuh
     [not found] <baBmH-48R-17@gated-at.bofh.it>
2008-09-12 13:28 ` Bodo Eggert

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=20081007204011.GG6604@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=eo@nebensachen.de \
    --cc=greg@kroah.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=multinymous@gmail.com \
    --cc=tj@kernel.org \
    --cc=trenn@suse.de \
    /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).