All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL RESEND] arm-soc: vt8500: Convert mach-vt8500 to devicetree
Date: Fri, 21 Sep 2012 09:17:41 +0000	[thread overview]
Message-ID: <201209210917.42388.arnd@arndb.de> (raw)
In-Reply-To: <1348212797.13689.3.camel@gitbox>

On Friday 21 September 2012, Tony Prisk wrote:
> > I plan to submit a new framebuffer driver for 3.8 which could be
> > modified to use the helper when its in 3.8 (assuming it doesn't make
> > 3.7) - or the existing framebuffer driver could be patched to use the
> > of_helper. I realise this creates a bit of churn on the framebuffer
> > code, but more than likely its going to occur anyway if the new driver
> > is accepted.

Slightly unrelated, but what is the state of this driver? I believe
"modern" drivers are supposed to register as a kernel modesetting
driver to the drivers/gpu/drm framwork rather than the traditional
drivers/video infrastructure.

> To clarify, I have made the following changes to try bringing the code
> in line with the videomode_helper patch. I guess this is really a
> question for Rob - Does this help??

>From all I can tell, the vt8500 platform code in the current (v3.6)
version is rather broken due to bitrot, and I think we should take
your code in the fixed version unless Rob has any serious objections.

You have done a great job on cleaning it up and I'd love to see this
all working again in 3.7, even if we have to adapt the bindings
in 3.8.

	Arnd

      reply	other threads:[~2012-09-21  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  5:45 [GIT PULL RESEND] arm-soc: vt8500: Convert mach-vt8500 to devicetree Tony Prisk
2012-09-20 23:28 ` Olof Johansson
2012-09-21  6:07   ` Tony Prisk
2012-09-21  6:42     ` Tony Prisk
2012-09-21  7:30       ` Tony Prisk
2012-09-21  9:17         ` Arnd Bergmann [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=201209210917.42388.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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.