All of lore.kernel.org
 help / color / mirror / Atom feed
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: imx53
Date: Thu, 19 Jan 2012 08:06:28 +0100	[thread overview]
Message-ID: <4F17C0F4.3090703@de.bosch.com> (raw)
In-Reply-To: <1326925172.3468.300.camel@hp-dhlii>

On 18.01.2012 23:19, David Lynch Jr. wrote:
> Linus's tree does not yet include numerous imx53 drivers. 
> While I can get it to boot, there is lots of hardware that does not
> work. 
> 
> Freescale and others are doing imx53 driver work and most drivers are
> available somewhere, though I have not found them all in the same place.
> 
> Regardless, I am just looking for an appropriate reference/starting
> point. 

You might want to have a look to Linaro, too. E.g.

http://git.linaro.org/gitweb?p=bsp/freescale/linux-linaro.git;a=shortlog;h=refs/heads/lt-3.2-imx5

If I understood correctly, from Freescale point of view, the Linaro 
Freescale landing team is responsible to mainline the Freescale work.

Best regards

Dirk

> What would be the normal route for i.MX53 work into the kernel ?
> 
> I can pull that, start there, merge what I need and submit patches if no
> one else does.  
> 
> 
> 
> On Wed, 2012-01-18 at 17:57 -0200, Fabio Estevam wrote:
>> On Wed, Jan 18, 2012 at 1:39 PM, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
>>> Where would I look for the appropriate git kernel source tree that is being
>>> used for i.MX53 development feeding the distribution kernel ?
>> You can use Linus' tree directly.
>>
>> Regards,
>>
>> Fabio Estevam

      parent reply	other threads:[~2012-01-19  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 15:39 imx53 David H. Lynch Jr.
2012-01-18 19:57 ` imx53 Fabio Estevam
2012-01-18 22:19   ` imx53 David Lynch Jr.
2012-01-19  6:09     ` imx53 Robert Schwebel
2012-01-19  7:06     ` Dirk Behme [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=4F17C0F4.3090703@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 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.