public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Oleg Verych <olecom@flower.upol.cz>,
	Allen Martin <AMartin@nvidia.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: Nvidia cable detection problems & ACPI (beware, slight off-top)
Date: Mon, 05 Feb 2007 16:55:28 -0500	[thread overview]
Message-ID: <45C7A7D0.407@garzik.org> (raw)
In-Reply-To: <20070205220442.6e13a7b6@localhost.localdomain>

Alan wrote:
>> I'm very upset, that hardware nvidia-lego forces system software (and
>> programmers) to know "unfortunately no standard" ways of desinging
>> things... One read-only-for-os, hardware set bit in kind of control
> 
> The hardware doesn't. The BIOS authors do by not setting the cable flags.
> We actually need to use the STM and GTM methods for PC suspend/resume so
> it makes sense to see if they will work out in this case too.


We also need ACPI, where available, because that's the only way to 
obtain a BIOS-set hard drive password.  And BIOS vendors often deliver 
hard drive-specific errata this way, if the problem is serious enough 
(though certainly we would prefer that the OS knows about drive errata, 
when a runtime patch is necessary)

	Jeff



  reply	other threads:[~2007-02-05 21:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070205075836.GG1625@htj.dyndns.org>
     [not found] ` <20070205112410.5a3c3182@localhost.localdomain>
     [not found]   ` <45C72012.7050605@gmail.com>
     [not found]     ` <20070205132247.6f611e3c@localhost.localdomain>
     [not found]       ` <45C73A3E.6080700@gmail.com>
2007-02-05 14:34         ` Nvidia cable detection problems (was [PATCH] amd74xx: don't configure udma mode higher than BIOS did) Alan
2007-02-05 14:50           ` Tejun Heo
2007-02-05 15:49             ` Alan
     [not found]             ` <58cb370e0702050709w1b7682dr5dff9e7ce69465a@mail.gmail.com>
2007-02-05 17:08               ` Allen Martin
2007-02-05 18:12                 ` Alan
2007-02-05 18:36                   ` Tejun Heo
2007-02-05 18:55                     ` Bartlomiej Zolnierkiewicz
2007-02-05 19:15                       ` Tejun Heo
2007-02-05 21:27                       ` Bartlomiej Zolnierkiewicz
2007-02-05 22:02                         ` Alan
2007-02-05 22:00                           ` Bartlomiej Zolnierkiewicz
2007-02-05 19:13                     ` Alan
2007-02-05 21:43                       ` Jeff Garzik
2007-02-05 21:11                 ` Nvidia cable detection problems & ACPI (beware, slight off-top) Oleg Verych
2007-02-05 22:04                   ` Alan
2007-02-05 21:55                     ` Jeff Garzik [this message]
2007-02-05 22:42                       ` Oleg Verych
2007-02-05 22:51                         ` Jeff Garzik

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=45C7A7D0.407@garzik.org \
    --to=jeff@garzik.org \
    --cc=AMartin@nvidia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    /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