mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: Rockchip: Add DEBUG_LL based on mach-socfpga
Date: Thu, 12 Feb 2015 20:59:23 +0100	[thread overview]
Message-ID: <1423771163.2199.1.camel@lynxeye.de> (raw)
In-Reply-To: <20150212195144.GJ10842@pengutronix.de>

Am Donnerstag, den 12.02.2015, 20:51 +0100 schrieb Uwe Kleine-König:
> Hello,
> 
> On Thu, Feb 12, 2015 at 10:45:19PM +0300, Панов Андрей wrote:
> > 12.02.2015, 22:34, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>:
> > > Better make use of DEBUG_UART_PHYS and DEBUG_UART_BASE.
> > > And there is already DEBUG_RK29_UART[123] and DEBUG_RK3X_UART[0123] and
> > > DEBUG_RK32_UART2. Doesn't one of those fit your needs?
> > >
> > 
> > Which branch contains it? I've checked master and next and there is no such a definitions.
> Then you didn't check correctly. It's available since at least
> v3.12-rc1:
> 
>  $ git show v3.12-rc1:arch/arm/Kconfig.debug | grep DEBUG_RK29_UART1 | wc -l
>  3
> 
> The same happens when using 3.19 instead of 3.12-rc1.
> 
But this is the barebox ML, so your Linux git tree may take you  a bit
into the wrong direction. ;)

Regards,
Lucas


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2015-02-12 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 19:07 Andrey Panov
2015-02-12 19:34 ` Uwe Kleine-König
2015-02-12 19:45   ` Панов Андрей
2015-02-12 19:51     ` Uwe Kleine-König
2015-02-12 19:55       ` Панов Андрей
2015-02-12 19:57       ` Uwe Kleine-König
2015-02-12 20:00         ` Панов Андрей
2015-02-12 19:59       ` Lucas Stach [this message]
2015-02-13  6:22 ` Sascha Hauer

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=1423771163.2199.1.camel@lynxeye.de \
    --to=dev@lynxeye.de \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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