From: ajaynumb@gmail.com (Ajay kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Unable to boot mainline on snow chromebook since 3.15
Date: Fri, 5 Sep 2014 19:16:03 +0530 [thread overview]
Message-ID: <CAEC9eQOMd7ME5KiG2QHCf3TMJAwSxLUgGpmFrpw_HQT4me9YWg@mail.gmail.com> (raw)
In-Reply-To: <20140905122232.GP13515@arm.com>
Hi Will,
On Fri, Sep 5, 2014 at 5:52 PM, Will Deacon <will.deacon@arm.com> wrote:
> [Looks like it's not just Rutland that can't spell the address of the
> mailing list today. Fixed here, so please use this post in any replies].
>
> On Fri, Sep 05, 2014 at 12:57:04PM +0100, Will Deacon wrote:
>> Hi all,
>>
>> I'm one of the few, foolish people to try running mainline on my 5250-based
>> Samsung Chromebook (snow). I can live without wireless, usb3 and video
>> acceleration, so actually it makes a reasonable development platform for
>> doing A15-based (micro)-architectural work.
>>
>> However, since 3.15 I've not been able to boot *any* mainline kernels on
>> this board. I did mean to report this earlier, but I have other machines
>> that can run mainline so this has fallen by the wayside.
>>
>> The problems started with 3.16, where simple-fb would fail to initialise
>> and I lost my display. Note that I don't have a serial console on this
>> machine (I looked at the PCB and there's no way I can solder one of those
>> myself :) I bisected the issue at the time, and I could get my display back
>> by removing some of the new regulator and hdmi properties from the DT. At
>> that point, I could boot, but DMA didn't initialise for the MMC controller
>> so I couldn't mount my root filesystem.
>>http://www.spinics.net/lists/dri-devel/msg66740.html
>> With 3.17-rc3, it seems a lot worse -- I don't get any output after nv-uboot
>> (i.e. the nv-uboot screen just remains on the display, with the last line
>> reading "Stashed 20 records").
>>
>> I'd usually try to debug this a bit further, but without a console it's
>> really painful to get anywhere. I've been working with 3.15, but now I'm
>> having to backport patches when I want to test them, which is more effort
>> than I can be bothered with.
>>
>> Is anybody else running mainline on this device and are these known/fixed
>> problems?
AFAIK, ARM chromebooks use DRM based display drivers and the required
patches are still not merged:
http://www.spinics.net/lists/dri-devel/msg66740.html
Corresponding DT patches are also still not merged:
http://www.spinics.net/lists/arm-kernel/msg358324.html
http://www.spinics.net/lists/arm-kernel/msg358325.html
There is a patch for configs as well:
https://www.mail-archive.com/linux-samsung-soc at vger.kernel.org/msg35828.html
Try these patches(I hope they will apply directly on 3.17-rc3) and you should
be able to use display on snow.
Ajay
next prev parent reply other threads:[~2014-09-05 13:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140905115704.GO13515@arm.com>
2014-09-05 12:22 ` Unable to boot mainline on snow chromebook since 3.15 Will Deacon
2014-09-05 13:46 ` Ajay kumar [this message]
2014-09-05 13:56 ` Vivek Gautam
2014-09-08 11:17 ` Will Deacon
2014-09-05 14:12 ` Marc Zyngier
2014-09-05 20:25 ` Doug Anderson
2014-09-07 9:06 ` Javier Martinez Canillas
2014-09-07 15:01 ` Mark Brown
2014-09-07 15:51 ` Javier Martinez Canillas
2014-09-07 15:52 ` Tomasz Figa
2014-09-07 16:12 ` Javier Martinez Canillas
2014-09-07 16:19 ` Tomasz Figa
2014-09-07 16:40 ` Javier Martinez Canillas
2014-09-08 11:21 ` Will Deacon
2014-09-08 11:55 ` Javier Martinez Canillas
2014-09-08 12:46 ` Will Deacon
2014-09-08 12:20 ` Grant Likely
2014-09-08 13:49 ` Mark Brown
2014-09-08 14:05 ` Javier Martinez Canillas
2014-09-10 11:17 ` Will Deacon
2014-09-10 16:03 ` Doug Anderson
2014-09-10 16:23 ` Will Deacon
2014-09-08 15:58 ` Doug Anderson
2014-09-08 19:40 ` Grant Likely
2014-09-10 13:06 ` Olof Johansson
2014-09-10 14:31 ` Mark Brown
2014-09-10 14:56 ` Grant Likely
2014-09-10 15:39 ` Mark Brown
2014-09-10 16:29 ` Grant Likely
2014-09-10 16:45 ` Doug Anderson
2014-09-10 19:45 ` Mark Brown
2014-09-10 19:51 ` Doug Anderson
2014-09-10 16:57 ` Mark Brown
2014-09-11 9:22 ` Grant Likely
2014-09-11 18:03 ` Mark Brown
2014-09-11 22:54 ` Doug Anderson
2014-09-29 12:57 ` Thierry Reding
2014-09-29 13:12 ` Grant Likely
2014-09-29 16:37 ` Mark Brown
2014-09-30 6:12 ` Thierry Reding
2014-09-29 20:46 ` Maxime Ripard
2014-09-10 16:36 ` Olof Johansson
2014-09-10 18:17 ` Mark Brown
2014-09-11 9:06 ` Grant Likely
2014-09-11 16:16 ` Mark Brown
2014-09-08 4:36 ` Doug Anderson
2014-09-08 6:09 ` Javier Martinez Canillas
2014-09-08 15:55 ` Doug Anderson
2014-09-08 16:07 ` Will Deacon
2014-09-08 16:12 ` Doug Anderson
2014-09-08 10:20 ` Mark Brown
2014-09-08 4:43 ` Doug Anderson
2015-01-30 4:56 bruce m beach
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=CAEC9eQOMd7ME5KiG2QHCf3TMJAwSxLUgGpmFrpw_HQT4me9YWg@mail.gmail.com \
--to=ajaynumb@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).