public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Shawn Starr <shawn.starr@rogers.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [WISHLIST] IBM HD Shock detection in Linux
Date: Fri, 10 Dec 2004 21:08:18 +0000	[thread overview]
Message-ID: <1102712897.3264.75.camel@localhost.localdomain> (raw)
In-Reply-To: <1102709841.29919.23.camel@krustophenia.net>

On Gwe, 2004-12-10 at 20:17, Lee Revell wrote:
> So in other words reverse engineer it.  Ugh.  I thought those days were
> behind us, at least with regards to "linux friendly" vendors like IBM.
> 
> Shawn, why don't you just ask IBM for the data sheet?

IBM are still really really bad about external data sheets and the like.
I spent over three years chasing IBM for docking station chip
information.

Alan


  reply	other threads:[~2004-12-10 22:12 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
2004-12-10 20:03 ` Kay Sievers
2004-12-10 20:17   ` Lee Revell
2004-12-10 21:08     ` Alan Cox [this message]
  -- 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=1102712897.3264.75.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --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