public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Andrey Smirnov
	<andrey.smirnov-MC3rjLPHZ0ivD/XHwUtZZ+TW4wlIGRCZ@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] tegra_pcm DMA buffers allocation
Date: Thu, 19 Apr 2012 15:37:17 -0600	[thread overview]
Message-ID: <4F90858D.4010206@wwwdotorg.org> (raw)
In-Reply-To: <1334869632.13681.59.camel@marvin>

On 04/19/2012 03:07 PM, Andrey Smirnov wrote:
> On Thu, 2012-04-19 at 16:07 -0400, Stephen Warren wrote:
...
>> BTW, did you try running the mainline code on your board. If it's
>> derived from Harmony, it should be easy to get it going.
> 
> Last time we did there was no support for Tegra's NAND and display
> controllers

What do you need the NAND controllers for? I'm not 100% certain, but I
believe we plan on upstreaming NAND support into U-Boot, but not the
kernel, since we didn't see a need for it there IIRC. (Not that we'd
stop anyone else doing it)

  reply	other threads:[~2012-04-19 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 16:00 [RFC] tegra_pcm DMA buffers allocation Andrey Smirnov
2012-04-19 20:07 ` Stephen Warren
     [not found]   ` <4F90708F.8070504-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-19 21:07     ` Andrey Smirnov
2012-04-19 21:37       ` Stephen Warren [this message]
     [not found]         ` <4F90858D.4010206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-19 23:30           ` Andrey Smirnov
2012-04-20  5:58           ` Thierry Reding

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=4F90858D.4010206@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=andrey.smirnov-MC3rjLPHZ0ivD/XHwUtZZ+TW4wlIGRCZ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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