public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [Fwd: Re: imx53]
Date: Thu, 26 Jan 2012 08:09:29 +0100	[thread overview]
Message-ID: <4F20FC29.2060500@de.bosch.com> (raw)
In-Reply-To: <1327517782.21058.49.camel@hp-dhlii>

On 25.01.2012 19:56, David Lynch Jr. wrote:
> I just pulled the most recent copy of linus's tree 3.3 something. 
> It appears that significantly more i.mx53 drivers are getting into that
> source than last time I looked. 
> 
> Now I am trying to build it for the i.MX53 QSB - the development
> platform I am using. 
> 
> Myriads of config options have changed since the 2.6.38.3 that I have
> somewhat working. Just borrowing the .config appears to be
> insufficient. 
> 
> After some mucking arround that included Kconfig changes I was able to
> get CONFIG_FB_IMX set and build a kernel with it, but it does not appear
> to be getting initialized. 
> 
> What do I need to do to get Linux to use this driver ?
> Has ARM 3.3 moved to device trees ?

Yes, I think so.

If you are new to this, one option would be to start with a recent 
Linaro i.MX53 Loco build (binary distribution). This could be a good 
option to get an idea how U-Boot, device tree and the kernel work 
together. In the next step you could replace the parts you are 
interested in by your own versions, then. E.g. the kernel.

Best regards

Dirk

  reply	other threads:[~2012-01-26  7:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 18:56 [Fwd: Re: imx53] David Lynch Jr.
2012-01-26  7:09 ` Dirk Behme [this message]
2012-01-26 14:04   ` David Lynch Jr.

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=4F20FC29.2060500@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox