public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: "Barbalho, Rafael" <rafael.barbalho@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: Provide a config option to select	a target platform
Date: Mon, 14 Jul 2014 11:40:58 +0100	[thread overview]
Message-ID: <20140714104058.GA22110@strange.amr.corp.intel.com> (raw)
In-Reply-To: <4B498744C37F034EA16F6FBC6AB9FAD21AE543A4@IRSMSX103.ger.corp.intel.com>

On Mon, Jul 14, 2014 at 11:18:30AM +0100, Barbalho, Rafael wrote:
> 
> 
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
> > Of Damien Lespiau
> > Sent: Friday, July 11, 2014 6:34 PM
> > To: intel-gfx@lists.freedesktop.org
> > Subject: [Intel-gfx] [PATCH 1/2] drm/i915: Provide a config option to select a
> > target platform
> > 
> > It'd be nice to be able to target a single platform to reduce the size
> > for the i915 driver.
> > 
> > Start low-fi and coarse grained: it's easy to split the (S)DVO code out,
> > the API surface is reduced to two init functions.
> > 
> > Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> 
> Is this the right way to go?
> 
> I think what will happen is that we are just going to have everything
> enabled anyway because you'd want your kernel to boot on any intel
> platform. Certainly on the stuff I'm working on I'll just have to
> enable this stuff all the time because I don't know if the system
> image is going to be installed on a broadwell or a valleyview. The
> same comment applies to patch 2.

The patches are already dropped. I guess it depends what you want to do
really. I can see a specific product, say running on Valleyview, that
could turn that on. It sounds likely that people will at least have a
per-platform config file (if not per-platform kernels), which could have
this tweak.

I still think we could save 300+ Kb if taking this to its limits, but
meh.

-- 
Damien

  reply	other threads:[~2014-07-14 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 17:34 [PATCH 0/2] Low hanging fruit to reduce the driver size Damien Lespiau
2014-07-11 17:34 ` [PATCH 1/2] drm/i915: Provide a config option to select a target platform Damien Lespiau
2014-07-14 10:18   ` Barbalho, Rafael
2014-07-14 10:40     ` Damien Lespiau [this message]
2014-07-11 17:34 ` [PATCH 2/2] drm/i915: Don't compile the MIPI DSI code on HSW/BDW Damien Lespiau
2014-07-11 18:34 ` [PATCH 0/2] Low hanging fruit to reduce the driver size Damien Lespiau
2014-07-12 11:01 ` Daniel Vetter
2014-07-12 11:11   ` Damien Lespiau

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=20140714104058.GA22110@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rafael.barbalho@intel.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