From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] imx: dma: remove SDMA_IS_MERGED
Date: Thu, 25 Nov 2010 10:07:07 +0100 [thread overview]
Message-ID: <20101125090707.GR6017@pengutronix.de> (raw)
In-Reply-To: <20101124201831.GZ4693@pengutronix.de>
On Wed, Nov 24, 2010 at 09:18:31PM +0100, Uwe Kleine-K?nig wrote:
> On Wed, Nov 24, 2010 at 06:07:18PM -0200, Fabio Estevam wrote:
> > Hi Uwe,
> >
> > 2010/11/24 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> > > Hello Fabio,
> > >
> > > On Wed, Nov 24, 2010 at 05:29:31PM -0200, Fabio Estevam wrote:
> > >> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> > >> ---
> > >> This allows imx-for-2.6.38 tree to build again.
> > > The same patch is already in Sascha's imx-for-2.6.37 branch (and so in
> > > for-next, too). ?There are some more fixes in for-.37 so I'd use the
> > > for-next branch for now.
> >
> > Thanks, I haven't noticed this. Will use for-next branch for now.
> >
> > While at the dma topic: is anyone able to boot a kernel on MX51 with
> > IMX_SDMA=y?
> >
> > I enabled early printk support, but no kernel messages appear after:
> > Uncompressing Linux... done, booting the kernel.
> >
> > This also happens on the for-next branch.
> I usually prefer just using DEBUG_LL and put
>
> #ifdef CONFIG_DEBUG_LL
> void printch(char);
> printch(c);
> #endif
>
> into emit_log_char. But I think that's only because I don't know how to
> use early printk properly. (You might need an additional kernel
> parameter?!)
Yes, 'earlyprintk'.
--
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 |
prev parent reply other threads:[~2010-11-25 9:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 19:29 [PATCH] imx: dma: remove SDMA_IS_MERGED Fabio Estevam
2010-11-24 19:44 ` Uwe Kleine-König
2010-11-24 20:07 ` Fabio Estevam
2010-11-24 20:18 ` Uwe Kleine-König
2010-11-24 21:42 ` Fabio Estevam
2010-11-24 21:58 ` Uwe Kleine-König
2010-11-24 22:57 ` Richard Zhao
2010-11-25 9:13 ` Sascha Hauer
2010-11-25 12:09 ` Fabio Estevam
2010-11-25 12:29 ` Arnaud Patard (Rtp)
2010-11-25 12:32 ` Fabio Estevam
2010-11-25 13:58 ` Uwe Kleine-König
2010-11-29 21:24 ` Sascha Hauer
2010-11-29 22:27 ` Fabio Estevam
2010-12-01 11:14 ` Sascha Hauer
2010-12-01 11:35 ` Arnaud Patard (Rtp)
2010-12-01 15:41 ` Sascha Hauer
2010-12-01 23:44 ` Arnaud Patard (Rtp)
2010-12-02 12:14 ` Sascha Hauer
2010-12-02 15:36 ` Fabio Estevam
2010-12-01 15:40 ` Fabio Estevam
2010-12-03 13:00 ` Arnaud Patard (Rtp)
2010-12-03 19:49 ` Fabio Estevam
2010-11-25 9:07 ` 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=20101125090707.GR6017@pengutronix.de \
--to=s.hauer@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.