From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/1] ARM: print MHz in /proc/cpuinfo
Date: Mon, 18 Jul 2016 12:02:37 +0200 [thread overview]
Message-ID: <20160718100236.GA12427@amd> (raw)
In-Reply-To: <20160703165431.GL1041@n2100.armlinux.org.uk>
On Sun 2016-07-03 17:54:31, Russell King - ARM Linux wrote:
> On Sat, Jul 02, 2016 at 07:58:00PM -0400, Jon Masters wrote:
> > Agreed. But we'll still be coming back to ensure this information is
> > presented to users. I pointed out to ARM about 3-4 years ago that this
> > was going to bite us. It is now biting us, and we will ensure that
> > useless data is provided where it is on x86 for identical experience by
> > users. That is unless or until x86 users do something else always. Our
> > (separate) case will use DMI or ACPI for the same kind of data.
>
> Right, so having read all your email, there's no reason why we couldn't
> just print:
>
> cpu MHz : 99999999.999
You apparenly did not read the email. Because bogus number will not
help people detecting underclocked configurations, as email was
explaining.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Jon Masters <jcm@jonmasters.org>,
Jon Mason <jon.mason@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/1] ARM: print MHz in /proc/cpuinfo
Date: Mon, 18 Jul 2016 12:02:37 +0200 [thread overview]
Message-ID: <20160718100236.GA12427@amd> (raw)
In-Reply-To: <20160703165431.GL1041@n2100.armlinux.org.uk>
On Sun 2016-07-03 17:54:31, Russell King - ARM Linux wrote:
> On Sat, Jul 02, 2016 at 07:58:00PM -0400, Jon Masters wrote:
> > Agreed. But we'll still be coming back to ensure this information is
> > presented to users. I pointed out to ARM about 3-4 years ago that this
> > was going to bite us. It is now biting us, and we will ensure that
> > useless data is provided where it is on x86 for identical experience by
> > users. That is unless or until x86 users do something else always. Our
> > (separate) case will use DMI or ACPI for the same kind of data.
>
> Right, so having read all your email, there's no reason why we couldn't
> just print:
>
> cpu MHz : 99999999.999
You apparenly did not read the email. Because bogus number will not
help people detecting underclocked configurations, as email was
explaining.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-07-18 10:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 21:08 [RFC 0/1] ARM: print MHz in /proc/cpuinfo Jon Mason
2016-06-07 21:08 ` Jon Mason
2016-06-07 21:08 ` [RFC 1/1] " Jon Mason
2016-06-07 21:08 ` Jon Mason
2016-06-08 8:34 ` Sudeep Holla
2016-06-08 8:34 ` Sudeep Holla
2016-06-08 19:31 ` Jon Mason
2016-06-08 19:31 ` Jon Mason
2016-06-09 9:09 ` Sudeep Holla
2016-06-09 9:09 ` Sudeep Holla
2016-06-09 17:36 ` Jon Mason
2016-06-09 17:36 ` Jon Mason
2016-06-07 22:18 ` [RFC 0/1] " Russell King - ARM Linux
2016-06-07 22:18 ` Russell King - ARM Linux
2016-06-07 22:58 ` Jon Mason
2016-06-07 22:58 ` Jon Mason
2016-07-02 23:58 ` Jon Masters
2016-07-02 23:58 ` Jon Masters
2016-07-03 16:54 ` Russell King - ARM Linux
2016-07-03 16:54 ` Russell King - ARM Linux
2016-07-03 18:49 ` Andrew Lunn
2016-07-03 18:49 ` Andrew Lunn
2016-07-03 19:10 ` Russell King - ARM Linux
2016-07-03 19:10 ` Russell King - ARM Linux
2016-07-18 10:02 ` Pavel Machek [this message]
2016-07-18 10:02 ` Pavel Machek
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=20160718100236.GA12427@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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 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.