linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'James Simmons'" <jsimmons@transvirtual.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jason McMullan <jmcmullan@linuxcare.com>, linux-kernel@vger.kernel.org
Subject: RE: Why is Device3Dfx driver (voodoo1/2) not in the kernel?
Date: Thu, 27 Sep 2001 17:24:47 -0700	[thread overview]
Message-ID: <8FB7D6BCE8A2D511B88C00508B68C2081971D5@orsmsx102.jf.intel.com> (raw)

> From: James Simmons [mailto:jsimmons@transvirtual.com]
> > > different VCs. The current system allows it too but it is 
> more of a later
> > > add on hack. I have a much cleaner implementation which 
> does what you ask 
> > > of the above.         
> > 
> > The requirements of ACPI may yet see you get your wish ...
> 
> Let me guess. Insane like the rest of it.

Aww why'd you have to go and say that? Alan for once didn't bash ACPI
(;-)))) and you have to step up and do so?

Knowing ACPI intimately, I can say it deserves several unflattering
adjectives (insane isn't one of them) but also many good qualities that will
be obvious once implementation is complete.

Regards -- Andy
(Insane ACPI maintainer)

             reply	other threads:[~2001-09-28  0:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28  0:24 Grover, Andrew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-19 12:44 Why is Device3Dfx driver (voodoo1/2) not in the kernel? Steven Griffiths
2001-09-19 19:24 ` Alan Cox
2001-09-27  4:28   ` Jason McMullan
2001-09-27 12:00     ` Alan Cox
2001-09-27 15:57       ` Jason McMullan
2001-09-27 17:56         ` James Simmons
2001-09-27 22:49           ` Alan Cox
2001-09-27 23:26             ` James Simmons
2001-09-27 17:36       ` James Simmons

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=8FB7D6BCE8A2D511B88C00508B68C2081971D5@orsmsx102.jf.intel.com \
    --to=andrew.grover@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jmcmullan@linuxcare.com \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).