public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Intel Centrino and Linux
Date: Thu, 08 May 2003 12:46:15 -0700	[thread overview]
Message-ID: <m2bryd8bnc.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <01f301c3148f$63f16870$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org> (Derek Broughton's message of "Wed, 07 May 2003 08:54:18 -0300")

>>>>> "Derek" == Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>:
 Derek> From: "Jan Rychter" <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
 >> I've already ruled out all Compaq notebooks thanks to the multiple
 >> problem reports seen on this list (hi HP/Compaq! congratulations on
 >> the market strategy),

 Derek> I think that's awfully short-sighted.  Compaqs appear, from my
 Derek> reading of this list, to be some of the better supported
 Derek> laptops.  Sure there are lots of niggling little problems, but
 Derek> most of them can be fixed - thanks to the support available here
 Derek> from both users and HP.  Now, if Dell would only provide some
 Derek> support....

Is it? From what I see, people have to fix and patch their DSDTs in
order to get their notebooks working. I didn't have to do that with my
Sharp and I'm not looking forward to the experience. I would like to buy
a notebook that I can boot Linux on without going through the hassle of
ironing out the details.

But I guess everyone's taste is different. The level of "acceptable
annoyance" is also different for each one of us.

But I didn't see any comments from Andy or Bob in this thread -- about
Linux and Centrino, which is what this thread is really about?

--J.


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

  parent reply	other threads:[~2003-05-08 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 16:48 Samsung X10 XTC 1300 Nicolas Bellm
     [not found] ` <200305031848.04583.nbellm-Mmb7MZpHnFY@public.gmane.org>
2003-05-03 16:23   ` Alan Cox
     [not found]     ` <1051979022.24562.24.camel-2MMpYkNvuYAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-05-03 17:07       ` Owen Cliffe
2003-05-07  5:27       ` Intel Centrino and Linux Jan Rychter
2003-05-07 11:54         ` Derek Broughton
     [not found]           ` <01f301c3148f$63f16870$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2003-05-08 19:46             ` Jan Rychter [this message]
     [not found]               ` <m2bryd8bnc.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-05-09 14:32                 ` Ducrot Bruno
     [not found]         ` <m21xzb9vig.fsf_-_-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-05-07  6:46           ` Karol Kozimor
2003-05-07 12:02           ` Alan Cox
     [not found]             ` <1052308970.3061.4.camel-2MMpYkNvuYAXoXS6vNje7nviChZXdy279dF7HbQ/qKg@public.gmane.org>
2003-05-08  6:33               ` Alexander Hoogerhuis

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=m2bryd8bnc.fsf@tnuctip.rychter.com \
    --to=jan-jaspcfd0eodbdgjk7y7tuq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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