From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com,
alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers
Date: Tue, 04 May 2010 10:11:34 -0500 [thread overview]
Message-ID: <4BE03926.4050900@freescale.com> (raw)
In-Reply-To: <20100504145430.GC3651@opensource.wolfsonmicro.com>
Mark Brown wrote:
> On Mon, May 03, 2010 at 04:54:15PM -0500, Timur Tabi wrote:
>
>> { .compatible = "simple-bus", },
>> - { .compatible = "gianfar", },
>> + /* So that the DMA channel nodes can be probed individually: */
>> + { .compatible = "fsl,eloplus-dma", },
>> {}
>
> The removal of gianfar looks a bit surprising here - if it's not a
> mistake a note in the changelog would be useful.
The changelog says this:
Also remove the "gianfar" compatible from mpc8610_ids[], since there is no
gianfar (or any other networking device) on the 8610.
The 8610 is almost unique among our high-end PowerPC chips in that it
literally has no on-board networking. The board provides networking via a
PCI device.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-05-04 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 21:54 [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers Timur Tabi
2010-05-04 14:54 ` Mark Brown
2010-05-04 15:11 ` Timur Tabi [this message]
2010-05-04 19:22 ` [alsa-devel] " Mark Brown
2010-05-04 17:20 ` Kumar Gala
2010-05-05 11:22 ` Mark Brown
2010-05-05 11:39 ` [alsa-devel] " Timur Tabi
2010-05-05 12:35 ` Mark Brown
2010-05-05 15:59 ` Timur Tabi
2010-05-17 15:55 ` Kumar Gala
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=4BE03926.4050900@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=lrg@slimlogic.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).