From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Kernel 2.6.7 speedstep-piix4 on vaio
Date: Mon, 2 Aug 2004 23:31:23 +0200 [thread overview]
Message-ID: <20040802213123.GC24329@dominikbrodowski.de> (raw)
In-Reply-To: <20040802204921.GD12724@redhat.com>
On Mon, Aug 02, 2004 at 09:49:21PM +0100, Dave Jones wrote:
> I'd like to live in a utopia where broken hardware doesn't exist too, but
> last time I checked, neither I, nor Linus does 8-)
> I've not had any problems merging such entries with him in the past that
> I can recall.
Excellent. Andrew just pushed the "difficult" patch to Linus again, so I'm
still hopeful :)
> > I don't know what the general consensus on a big (~50? 100?) table is.
>
> I'll bet you can get the more common models in much less entries than that.
> Given its now an end of life'd chipset, its not like we'll ever see
> new entries once we have the more common ones too. Plus we'd only
> need entries from models that deviate from the defaults, and finally
> we'd need input from users, which at times, can be hard to gather anyway.
> So I'm sceptical that we'll see 50-100 entries.
Let's see. Got one affected system here locally...
Dominik
next prev parent reply other threads:[~2004-08-02 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 14:20 Kernel 2.6.7 speedstep-piix4 on vaio Ivor Hewitt
2004-07-29 21:04 ` Dominik Brodowski
2004-07-30 20:20 ` Ivor Hewitt
2004-08-02 19:31 ` Dave Jones
2004-08-02 20:27 ` Dominik Brodowski
2004-08-02 20:49 ` Dave Jones
2004-08-02 21:31 ` Dominik Brodowski [this message]
2004-08-02 20:44 ` Ivor Hewitt
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=20040802213123.GC24329@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.