public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Doug Anderson <dianders@chromium.org>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Will Deacon <will.deacon@arm.com>,
	Vivek Gautam <gautam.vivek@samsung.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
	"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
	David Garbett <David.Garbett@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	"gregory.clement@free-electrons.com" 
	<gregory.clement@free-electrons.com>,
	Olof Johansson <olofj@chromium.org>
Subject: Re: [PATCH] arm: Add Arm Erratum 773769 for Large data RAM latency.
Date: Wed, 29 Jan 2014 13:26:51 +0100	[thread overview]
Message-ID: <20140129122651.GB31980@panda> (raw)
In-Reply-To: <CAD=FV=XqoSGpQ_Yrjj4hvV_0FSMfQGcGEsKkL1Stnm9m5s2Xvw@mail.gmail.com>

Doug Anderson wrote (ao):
> On Wed, Jan 8, 2014 at 1:08 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> > On Wed, 8 Jan 2014, Doug Anderson wrote:
> >> * If Joe Upstream wants to run an upstream kernel on some type of
> >> exynos5250 product (Samsung ARM Chromebook, HP Chromebook 11, Nexus 10
> >> are the ones I know of) then he will deal with the small number of
> >> crashes or figure out a solution.
> >
> > If Joe Upstream wants to run an upstream kernel, doesn't he have to
> > unscrew his write protect switch first, at which point the RO firmware
> > can be updated as well?
> 
> Actually, no.  You can move your device into dev mode and run any
> kernel you want.  You'll get an annoying "you're in dev mode" screen
> at every bootup, but otherwise it works just fine.
> 
> Going into dev mode requires some special keystrokes at bootup and a
> wipe of your hard disk but no screwdrivers.

And there is http://www.arndaleboard.org/ where you just put an upstream
kernel on sd and boot.

	Sander

  reply	other threads:[~2014-01-29 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 13:33 [PATCH] arm: Add Arm Erratum 773769 for Large data RAM latency Vivek Gautam
2014-01-08 14:35 ` Will Deacon
2014-01-08 16:21   ` Doug Anderson
2014-01-08 19:20     ` Russell King - ARM Linux
2014-01-08 19:43       ` Doug Anderson
2014-01-08 20:58         ` Nicolas Pitre
2014-01-08 21:32           ` Doug Anderson
2014-01-08 21:02         ` Russell King - ARM Linux
2014-01-08 21:33           ` Doug Anderson
2014-01-08 21:08         ` Nicolas Pitre
2014-01-08 21:35           ` Doug Anderson
2014-01-29 12:26             ` Sander [this message]
2014-01-10 17:09     ` Tomasz Figa

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=20140129122651.GB31980@panda \
    --to=sander@humilis.net \
    --cc=Catalin.Marinas@arm.com \
    --cc=David.Garbett@arm.com \
    --cc=dianders@chromium.org \
    --cc=gautam.vivek@samsung.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=olofj@chromium.org \
    --cc=sboyd@codeaurora.org \
    --cc=will.deacon@arm.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