From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: i915 with valleyview
Date: Mon, 09 May 2016 11:19:16 +0300 [thread overview]
Message-ID: <87y47jiqyj.fsf@intel.com> (raw)
In-Reply-To: <20160506191331.GA14649@sudip-tp>
On Fri, 06 May 2016, Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
> On Fri, May 06, 2016 at 12:21:04PM +0100, Sudip Mukherjee wrote:
>> Hi Daniel,
>> I am trying to use i915 in one of our board which has Intel ATOM E3840.
>> I know Intel has released emgd driver for this cpu to use i915 but emgd
>> is not supported on v4.5 (or v4.6). The board is having SFI (simple
>> firmware interface) and maybe for that i915 is not finding the VBIOS and
>> other required information.
>
> I have been looking more into it and looks like it is supposed to use
> dsi but since there is no vbt so has_mipi is never set and dsi is never
> initialized.
> Can you please point me to somewhere or maybe give some idea how i can
> use i915 in a board where there is no vbt.
Hate to say it, but the i915 DSI support heavily relies on the VBT being
present. Basically all the configuration is there. I haven't got a clue
how emgd handles it. Maybe Matt does?
Basically you'd either have to figure out the configuration for the
panel from somewhere and feed it to intel_dsi_panel_vbt.c, or write a
panel specific driver of your own.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-09 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 11:21 i915 with valleyview Sudip Mukherjee
2016-05-06 19:13 ` Sudip Mukherjee
2016-05-09 8:19 ` Jani Nikula [this message]
2016-05-09 11:33 ` Sudip Mukherjee
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=87y47jiqyj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sudipm.mukherjee@gmail.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 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.