All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: thoughts on requiring multi-arch support for arm drm drivers?
Date: Wed, 23 Jan 2013 08:39:57 +0100	[thread overview]
Message-ID: <20130123073957.GS1906@pengutronix.de> (raw)
In-Reply-To: <3579832.etYhVaEi7B@avalon>

On Wed, Jan 23, 2013 at 02:29:25AM +0100, Laurent Pinchart wrote:
> Hi Rob,
> 
> On Monday 21 January 2013 09:54:01 Rob Clark wrote:
> > On Mon, Jan 21, 2013 at 9:47 AM, Laurent Pinchart wrote:
> > > On Sunday 20 January 2013 09:08:34 Rob Clark wrote:
> > >> One thing I've run into in the past when trying to make changes in drm
> > >> core, and Daniel Vetter has mentioned the same, is that it is a bit of
> > >> a pain to compile test things for the arm drivers that do not support
> > >> CONFIG_ARCH_MULTIPLATFORM.  I went through a while back and fixed up
> > >> the low hanging fruit (basically the drivers that just needed a
> > >> Kconfig change).  But, IIRC some of the backlight related code in
> > >> shmob had some non-trivial plat dependencies.
> > > 
> > > I've just compiled the shmob-drm driver without any error on x86_64. The
> > > CMA GEM helpers don't compile due to missing
> > > dma_(alloc|free)_writecombine though (but that would only be an issue if
> > > we require no arch dependency at all, not with multiarch).
> > 
> > ahh, ok.. maybe I should try again.  I'm pretty sure I was hitting
> > some issues around the backlight code before, but maybe that has been
> > fixed since then.
> > 
> > Anyways, if it builds for multi-platform, maybe you could send a patch
> > for the kconfig?
> 
> Do you prefer a dependency on (ARM || SUPERH) or (ARCH_MULTIPLATFORM || 
> SUPERH) ?

I suggest ARM instead of ARCH_MULTIPLATFORM since the former is the real
requirement for being able to compile it.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      parent reply	other threads:[~2013-01-23  7:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20 15:08 thoughts on requiring multi-arch support for arm drm drivers? Rob Clark
2013-01-20 15:42 ` Daniel Vetter
2013-01-20 15:42   ` Daniel Vetter
2013-01-21  7:28   ` Thierry Reding
2013-01-21  7:17 ` Thierry Reding
2013-01-21 13:57   ` Rob Clark
2013-01-21 15:47 ` Laurent Pinchart
2013-01-21 15:54   ` Rob Clark
2013-01-23  1:29     ` Laurent Pinchart
2013-01-23  1:42       ` Rob Clark
2013-01-23  7:39       ` Sascha Hauer [this message]

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=20130123073957.GS1906@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.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.