All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: imx53
Date: Thu, 19 Jan 2012 07:09:14 +0100	[thread overview]
Message-ID: <20120119060914.GX22061@pengutronix.de> (raw)
In-Reply-To: <1326925172.3468.300.camel@hp-dhlii>

David,

On Wed, Jan 18, 2012 at 05:19:32PM -0500, 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. 

Which drivers do you need?

> 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.

That's the reason development for the mainline is done here on ALKML,
with the aim to get everything into the mainline if possible.

> Regardless, I am just looking for an appropriate reference/starting
> point. 
> 
> What would be the normal route for i.MX53 work into the kernel ?

Start with Linus' top-of-tree, discuss what you have found here on the
list (before start coding), follow the coding rules and discuss the
patches here. Don't forget to set kernel at pengutronix.de on Cc:.

Robert
-- 
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 |

  reply	other threads:[~2012-01-19  6:09 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     ` Robert Schwebel [this message]
2012-01-19  7:06     ` imx53 Dirk Behme

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=20120119060914.GX22061@pengutronix.de \
    --to=r.schwebel@pengutronix.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.