From: Francois Tigeot <ftigeot@wolfpond.org>
To: Daniel Vetter <daniel@ffwll.ch>,
Alexey Orishko <alexey.orishko@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
stable@vger.kernel.org, Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Unlock panel even when LVDS is disabled
Date: Tue, 02 Dec 2014 14:12:01 +0100 [thread overview]
Message-ID: <547DBAA1.4000206@wolfpond.org> (raw)
In-Reply-To: <20141202130002.GR32117@phenom.ffwll.local>
Daniel Vetter wrote:
> On Tue, Dec 02, 2014 at 01:43:59PM +0100, Alexey Orishko wrote:
>>
>> One more question slightly out off topic:
>> - could I use i915 driver with other Intel Atom CPUs, such as D2550
>> and Avoton C2550?
>
> Anything newer than what you have right now likely means gma500 (which is
> horrible), unless it's a baytrail. Buyer beware, please triple-check that
> it works before placing an order. Since I have no clue about marketing
> names I'll refrain from a recommendation (too many ppl burned already).
You should also be aware than server Atoms such as the C2550 generally
(always ?) don't have integrated graphics.
These processors are typically sold with a Matrox G200 or some similar
sort of special-purpose VGA/IPMI solution.
--
Francois Tigeot
next prev parent reply other threads:[~2014-12-02 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 22:14 i915 driver failure Alexey Orishko
2014-12-01 9:10 ` Daniel Vetter
2014-12-01 10:56 ` Alexey Orishko
2014-12-01 16:56 ` [PATCH] drm/i915: Unlock panel even when LVDS is disabled Daniel Vetter
2014-12-01 18:38 ` Alexey Orishko
2014-12-02 12:43 ` Alexey Orishko
2014-12-02 13:00 ` Daniel Vetter
2014-12-02 13:12 ` Francois Tigeot [this message]
2014-12-02 13:21 ` Jani Nikula
2014-12-03 0:53 ` shuang.he
2014-12-29 8:00 ` Jani Nikula
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=547DBAA1.4000206@wolfpond.org \
--to=ftigeot@wolfpond.org \
--cc=alexey.orishko@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=stable@vger.kernel.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