All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shem Multinymous <multinymous@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>, Rovert Love <rlove@rlove.org>,
	Jens Axboe <axboe@suse.de>,
	linux-ide@vger.kernel.org
Subject: Re: tp_smapi conflict with IDE, hdaps
Date: Wed, 14 Dec 2005 18:32:51 +0200	[thread overview]
Message-ID: <41840b750512140832r2be9317akcc9d661e7810cf0f@mail.gmail.com> (raw)
In-Reply-To: <1134490575.11732.104.camel@localhost.localdomain>

Hi

On 12/13/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> But the ACPI DSDT is OS independant in theory and in practice to a fair
> extent. It can't make assumptions about windows drivers.

The IDE issue is moot in light of SET_STREAMING, but just for the
record: the preinstalled Windows on this ThinkPad uses Microsoft's
default IDE driver and Intel's default 82801FBM driver, so it doesn't
look like it's doing SMAPI-specific synchronization.


> Its probably easier to write than go find one
>
> I mean you need
>
> tp_hw_init() {
[code snipped]

Oh, thanks! That's far less voodoo than I feared.

I'll coordinate things with Robert Love (hdaps maintainer).

  Shem

  reply	other threads:[~2005-12-14 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 14:35 tp_smapi conflict with IDE, hdaps Shem Multinymous
2005-12-13 14:43 ` Shem Multinymous
2005-12-13 15:03 ` Alan Cox
2005-12-13 15:29   ` Shem Multinymous
2005-12-13 15:38     ` Alan Cox
2005-12-13 16:04       ` Shem Multinymous
2005-12-13 16:16         ` Alan Cox
2005-12-14 16:32           ` Shem Multinymous [this message]
2005-12-13 18:41     ` Shem Multinymous
2005-12-13 19:18       ` Alan Cox
2005-12-14 15:03         ` Shem Multinymous
2005-12-15  3:05           ` Mark Lord
2005-12-13 15:14 ` Robert Love
2005-12-13 15:43   ` Shem Multinymous

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=41840b750512140832r2be9317akcc9d661e7810cf0f@mail.gmail.com \
    --to=multinymous@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlove@rlove.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.