From: Tomasz Figa <tomasz.figa@gmail.com>
To: "Stéphane Marchesin" <marcheu@chromium.org>,
"Kevin Hilman" <khilman@linaro.org>
Cc: "linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Sean Paul <seanpaul@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>,
Inki Dae <inki.dae@samsung.com>,
naveenkrishna.ch@gmail.com,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Tushar Behera <tushar.behera@linaro.org>,
Tomasz Figa <t.figa@samsung.com>
Subject: Re: linux-next on Chromebook2: DRM failing to allocate
Date: Tue, 10 Jun 2014 20:56:04 +0200 [thread overview]
Message-ID: <539754C4.60008@gmail.com> (raw)
In-Reply-To: <CADMs+9a-vMpFOUmF5DO6X_OJfLgPP48DtRA9tcquzzt-Uso89A@mail.gmail.com>
On 10.06.2014 20:04, Stéphane Marchesin wrote:
> On Tue, Jun 10, 2014 at 10:56 AM, Kevin Hilman <khilman@linaro.org> wrote:
>> I'm trying to get the latest linux-next working on my Chromebook2
>> (it's booting to a serial console) and am now trying to get the
>> display working (at least for a frambuffer console.)
>>
>> Since the display nodes seem to be present in the exynos5800-peach-pi
>> DTS, I tried enabling DRM and it's failing to allocate memory (log
>> below[1]
>>
>> Is there some additional memory setup/allocations I should be doing?
>> maybe with CMA?
>
> Probably not CMA, but maybe you don't have the iommu enabled?
>
It should work without IOMMU as well. We're using Exynos DRM on Exynos4
without IOMMU and with CMA instead and it works fine.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-06-10 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 17:56 linux-next on Chromebook2: DRM failing to allocate Kevin Hilman
2014-06-10 18:04 ` Stéphane Marchesin
2014-06-10 18:24 ` Kevin Hilman
2014-06-10 18:36 ` Kevin Hilman
2014-06-10 18:56 ` Tomasz Figa [this message]
2014-06-10 19:29 ` Kevin Hilman
2014-06-10 20:51 ` Ajay kumar
2014-06-10 22:18 ` Kevin Hilman
2014-06-11 3:47 ` Rahul Sharma
2014-06-11 21:18 ` Kevin Hilman
2014-06-12 8:44 ` Ajay kumar
2014-06-12 19:50 ` Kevin Hilman
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=539754C4.60008@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=djkurtz@chromium.org \
--cc=inki.dae@samsung.com \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=naveenkrishna.ch@gmail.com \
--cc=seanpaul@chromium.org \
--cc=t.figa@samsung.com \
--cc=tushar.behera@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.