Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Clark Williams <williams@redhat.com>,
	Rodolfo Giometti <giometti@linux.it>,
	linux-mips@linux-mips.org
Subject: Re: Battery status
Date: Sat, 23 Jul 2005 00:14:34 +0100	[thread overview]
Message-ID: <1122074074.9478.65.camel@localhost.localdomain> (raw)
In-Reply-To: <20050722221608.GF3770@linux-mips.org>

On Gwe, 2005-07-22 at 18:16 -0400, Ralf Baechle wrote:
> Well, and on Monday Linus said about ACPI BIOS writers in front of 80
> kernel developers and an Intel guy on stage "BIOS writers are morons".
> Nobody did object and 30s later that was /topic on the #kernel irc
> channel ...

That would be because the BIOS writers don't get invited. From some of
the BIOS people I've talked to I'd say that

a) They are not morons they just work in ridiculous situations and
timescales
b) They don't neccessarily like ACPI either
c) Linus attitude is not helpful

What I will say from the non x86 end of things is that ACPI is vastly
inferior IMHO to things like OpenFirmware, but its Intel and Intel don't
seem to like standards they didn't invent.

Alan

  reply	other threads:[~2005-07-22 22:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 14:22 Battery status Rodolfo Giometti
2005-07-22 14:53 ` Clark Williams
2005-07-22 15:14   ` Rodolfo Giometti
2005-07-22 15:25     ` Clark Williams
2005-07-22 15:34       ` Rodolfo Giometti
2005-07-22 19:08         ` Clark Williams
2005-07-23 12:17           ` Rodolfo Giometti
2005-07-22 19:17   ` Ralf Baechle
2005-07-22 21:10     ` Clark Williams
2005-07-22 21:23       ` Ralf Baechle
2005-07-22 22:07         ` Clark Williams
2005-07-22 22:16           ` Ralf Baechle
2005-07-22 23:14             ` Alan Cox [this message]
2005-07-25 12:00           ` Maciej W. Rozycki

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=1122074074.9478.65.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=giometti@linux.it \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=williams@redhat.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