public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Prakash Punnoor <prakash@punnoor.de>,
	Jeff Garzik <jeff@garzik.org>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18
Date: Wed, 10 Jan 2007 10:25:52 -0700	[thread overview]
Message-ID: <45A521A0.9050205@wolfmountaingroup.com> (raw)
In-Reply-To: <20070110174710.GL17267@csclub.uwaterloo.ca>

Lennart Sorensen wrote:

>On Wed, Jan 10, 2007 at 06:29:28PM +0100, Prakash Punnoor wrote:
>  
>
>>You can install the Intel Matrix driver after "adjusting" the inf file...
>>    
>>
>
>Hmm, I guess a good question is: Why should I have to edit the inf file?
>Is it an issue of them making it only install if your hardware is
>already set to ahci mode?  But how am I supposed to boot and install the
>driver until I have the driver installed then.  Well I might try that
>next time I go there.  
>

>How stupid of intel.
>  
>

No doubt part of the Wintel (intel + Microsoft) strategy to perpetually 
break non-windows platforms with new incompatible
hardware like the switch over from the e1000 MT adapters to e1000 GT 
which are not backward compatible with the older chipsets.

I still have not seen the GT adapter work correctly off windows.

Jeff

:-)

Jeff

>--
>Len Sorensen
>
>  
>


  reply	other threads:[~2007-01-10 17:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 20:46 SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18 Jeff V. Merkey
2007-01-09 20:51 ` Jeff V. Merkey
2007-01-09 21:39   ` Auke Kok
2007-01-09 22:11     ` Jeff V. Merkey
2007-01-09 22:59 ` Lennart Sorensen
2007-01-09 23:35   ` Jeff V. Merkey
2007-01-09 23:21 ` Jeff Garzik
2007-01-09 23:34   ` Jeff V. Merkey
2007-01-10  0:25     ` Jeff Garzik
2007-01-10  0:13       ` Jeff V. Merkey
2007-01-10 14:39       ` Lennart Sorensen
2007-01-10 14:58         ` Jeff Garzik
2007-01-10 15:15           ` Lennart Sorensen
2007-01-10 17:29         ` Prakash Punnoor
2007-01-10 17:47           ` Lennart Sorensen
2007-01-10 17:25             ` Jeff V. Merkey [this message]
2007-01-10 17:58               ` Lennart Sorensen
2007-01-10 18:17               ` Jeff Garzik
2007-01-10 17:56             ` Prakash Punnoor
2007-01-10 18:00               ` Lennart Sorensen
2007-01-10 18:19               ` Jeff Garzik
2007-01-10 18:33                 ` Prakash Punnoor
     [not found] <fa.w2Xz1pEig0R6ShqpHFJyconmPBo@ifi.uio.no>
     [not found] ` <fa.Dlil7VK33821i8DmcFWlIN2XaQU@ifi.uio.no>
     [not found]   ` <fa.tj/VxhLXoYhj9fN5JWFl+JK12nU@ifi.uio.no>
     [not found]     ` <fa.j4A1taZJ5T85q4EnugrwsVjbq80@ifi.uio.no>
     [not found]       ` <fa.F7iasR6Lz0YMnhzBecxJ2HmeL/Y@ifi.uio.no>
     [not found]         ` <fa.knaXdjvwhsPCFpF5idaEG5sHhcM@ifi.uio.no>
2007-01-10 22:50           ` Robert Hancock

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=45A521A0.9050205@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=prakash@punnoor.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