public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [WISHLIST] IBM HD Shock detection in Linux
Date: Fri, 10 Dec 2004 14:59:49 -0500	[thread overview]
Message-ID: <1102708790.29919.20.camel@krustophenia.net> (raw)
In-Reply-To: <200412100339.46246.shawn.starr@rogers.com>

On Fri, 2004-12-10 at 03:39 -0500, Shawn Starr wrote:
> > Lee Revell <rlrevell <at> joe-job.com> writes:
> > 
> > > 
> > > On Wed, 2004-12-01 at 13:31 -0500, Shawn Starr wrote:
> > > > While I have seen this feature in XP, It would be nice to have such 
> > > > functionality in Linux. Does anyone know if this is being worked on 
> > > > somewhere?
> > > 
> > > What is it?  What does it do?  How does it work?  Got a link?
> > 
> > It's a motion detector on the motherboard.
> > 
> > Here is an IBM whitepaper:
> >   ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/aps2mst.pdf
> > 
> > Kay
> 
> Where can we find it on the motherboard or probe for it safely?
> 

Exactly.  All the IBM people on this list and not one remotely useful
post.  I can contact marketing@ibm.com or something if I want a bunch of
fluff.  That whitepaper is just a user level guide for the Windows
driver ferchrissake.

Obviously it's a motion detector on the motherboard.  How do we freaking
TALK to it?  As in, what bits to we write to what registers to do what.

Anyway, Linux support doesn't look good, if IBM isn't going to help.

Lee


  reply	other threads:[~2004-12-10 19:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  8:39 [WISHLIST] IBM HD Shock detection in Linux Shawn Starr
2004-12-10 19:59 ` Lee Revell [this message]
2004-12-10 20:03 ` Kay Sievers
2004-12-10 20:17   ` Lee Revell
2004-12-10 21:08     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2004-12-12 22:01 Niel Lambrechts
2004-12-12 22:06 ` Jan Engelhardt
2004-12-12 22:11   ` Niel Lambrechts
2004-12-12 22:15     ` Jan Engelhardt
2004-12-12 22:48       ` Jesper Juhl
2004-12-12 22:41         ` Jan Engelhardt
2004-12-14  0:41           ` Kevin Puetz
2004-12-13  8:05       ` Manu Abraham
2004-12-13  9:10     ` Sander
2004-12-12 22:59 ` Bernd Eckenfels
2004-12-01 18:31 Shawn Starr
2004-12-01 18:42 ` Lee Revell
2004-12-01 18:57   ` Robert Love
2004-12-02 13:21     ` Ian Soboroff
2004-12-01 20:51   ` Kay Sievers
2004-12-01 20:13 ` Joseph Pingenot

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=1102708790.29919.20.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.starr@rogers.com \
    /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