From: Dave Jones <davej@redhat.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
cpufreq@vger.kernel.org, "Rafał Bilski" <rafalbilski@interia.pl>
Subject: Re: [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig
Date: Sun, 8 Jun 2014 20:02:05 -0400 [thread overview]
Message-ID: <20140609000205.GA15035@redhat.com> (raw)
In-Reply-To: <1402269642.23860.48.camel@deadeye.wl.decadent.org.uk>
On Mon, Jun 09, 2014 at 12:20:42AM +0100, Ben Hutchings wrote:
> longhaul quickly caused hard lockups and possibly killed the memory
> module on my EPIA-PD board. It is commented as:
>
> 'BIG FAT DISCLAIMER: Work in progress code. Possibly *dangerous*'
that last part may have been overly dramatic. When I was originally
writing this driver I was using pre-production cpu's which were
marginal to begin with. Production hw should have been more tolerant.
What didn't help was a lot of the EPIAs were made with *Really*
shitty capacitors that would pop open and ooze over the boards. Might want
to eyeball those, you can usually tell when they've gone bad.
> Let's put another warning where people are more likely to see it.
That said, I'm not against itbeing marked BROKEN (I thought it
already was), and certainly don't recommend distros enabling it.
I'd also not stand in the way of someone throwing it out completely
given the small amount of systems out there likely still running this.
Dave
next prev parent reply other threads:[~2014-06-09 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 23:20 [PATCH 1/2] longhaul: Mark it as dangerous in Kconfig Ben Hutchings
2014-06-09 0:02 ` Dave Jones [this message]
2014-06-09 0:30 ` Ben Hutchings
2014-06-09 18:05 ` Rafał Bilski
2014-06-09 4:41 ` Viresh Kumar
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=20140609000205.GA15035@redhat.com \
--to=davej@redhat.com \
--cc=ben@decadent.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=rafalbilski@interia.pl \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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.