From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>,
linux-kernel@vger.kernel.org,
vamos-dev@i4.informatik.uni-erlangen.de,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Missing config option for SFFSDR_FPGA
Date: Wed, 21 Jul 2010 13:55:15 +0100 [thread overview]
Message-ID: <20100721125514.GC15462@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <s5htynt2eum.wl%tiwai@suse.de>
On Wed, Jul 21, 2010 at 02:34:25PM +0200, Takashi Iwai wrote:
> The problem is that the drivers for embedded platforms are often out
> of sync. davinci is one of such platforms. So, as Mark suggested,
> it'd be better to talk with guys responsible for such a system
> beforehand.
> Of course, as upstream, we can clean up things here. But, I'd like to
> see this clean-up rather from the platform side. In that way, it can
> be synchronized better.
More generally nobody who doesn't have the board is going to care about
things in a board-specific file too much, and with a lot of boards
there's substantial code carried out of tree that's not yet made it into
mainline for one reason or another.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
vamos-dev@i4.informatik.uni-erlangen.de
Subject: Re: Missing config option for SFFSDR_FPGA
Date: Wed, 21 Jul 2010 13:55:15 +0100 [thread overview]
Message-ID: <20100721125514.GC15462@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <s5htynt2eum.wl%tiwai@suse.de>
On Wed, Jul 21, 2010 at 02:34:25PM +0200, Takashi Iwai wrote:
> The problem is that the drivers for embedded platforms are often out
> of sync. davinci is one of such platforms. So, as Mark suggested,
> it'd be better to talk with guys responsible for such a system
> beforehand.
> Of course, as upstream, we can clean up things here. But, I'd like to
> see this clean-up rather from the platform side. In that way, it can
> be synchronized better.
More generally nobody who doesn't have the board is going to care about
things in a board-specific file too much, and with a lot of boards
there's substantial code carried out of tree that's not yet made it into
mainline for one reason or another.
next prev parent reply other threads:[~2010-07-21 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 10:58 Missing config option for SFFSDR_FPGA Christian Dietrich
2010-07-21 10:58 ` Christian Dietrich
2010-07-21 12:28 ` Mark Brown
2010-07-21 12:28 ` Mark Brown
2010-07-21 12:34 ` Takashi Iwai
2010-07-21 12:34 ` Takashi Iwai
2010-07-21 12:55 ` Mark Brown [this message]
2010-07-21 12:55 ` Mark Brown
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=20100721125514.GC15462@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=qy03fugy@stud.informatik.uni-erlangen.de \
--cc=tiwai@suse.de \
--cc=vamos-dev@i4.informatik.uni-erlangen.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 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.