Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Mandarino <fmandarino@endrelia.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Sedji Gaouaou <sedji.gaouaou@atmel.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>
Subject: Re: [PATCH] ASoC: Remove references to Endrelia ETI-B1 board
Date: Tue, 30 Sep 2008 11:39:09 -0400	[thread overview]
Message-ID: <48E2481D.6030208@endrelia.com> (raw)
In-Reply-To: <bd7b27490809300810n77b82690j4ddedb0a0f7108ac@mail.gmail.com>



Jarkko Nikula wrote:
> 2008/9/30 Frank Mandarino <fmandarino@endrelia.com
> <mailto:fmandarino@endrelia.com>>
> 
>     See attached.
> 
>     --
>     Frank Mandarino                              
>      fmandarino(a)endrelia.com <http://endrelia.com>
>     Endrelia Technologies Inc.
>     Toronto, Ontario, Canada
> 
>     The ASoC machine drivers for this board were only provided as examples
>     for the new AT91 ASoC platform driver.  Since the ETI-B1 board is
>     proprietary and there are other AT91 ASoC machine drivers available,
>     it makes sense to remove these drivers.
> 
>     Signed-off-by: Frank Mandarino <fmandarino@endrelia.com
>     <mailto:fmandarino@endrelia.com>>
>     ---
>      sound/soc/at91/Kconfig           |   27 ---
>      sound/soc/at91/Makefile          |    7 -
>      sound/soc/at91/eti_b1_bluecore.c |  284 -------------------------------
>      sound/soc/at91/eti_b1_wm8731.c   |  350
>     --------------------------------------
>      4 files changed, 0 insertions(+), 668 deletions(-)
> 
> Does it make sense to remove these yet? I didn't check different
> architectures in asoc-dev but are there any other platform and machine
> driver using multiple DAI links with real and "dummy" codec in ASoC v1?
> In that sense these are nice reference implementations :-)
> 
> 
> Jarkko

My reasons for wanting it removed are that 1) it only works on our
proprietary board, and 2) I don't have time to maintain it as changes
are made to ASoC.

If it is still useful for documentation purposes, then perhaps it should
be moved to a file in Documentation/sound/alsa/soc.  But then again,
someone will have maintain the documentation.

Regards,
../fam
-- 
Frank Mandarino                                fmandarino(a)endrelia.com
Endrelia Technologies Inc.
Toronto, Ontario, Canada

  reply	other threads:[~2008-09-30 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 14:42 [PATCH] ASoC: Remove references to Endrelia ETI-B1 board Frank Mandarino
2008-09-30 14:46 ` Mark Brown
2008-09-30 14:55 ` Takashi Iwai
2008-09-30 15:12   ` Frank Mandarino
2008-09-30 18:12     ` Mark Brown
2008-09-30 15:10 ` Jarkko Nikula
2008-09-30 15:39   ` Frank Mandarino [this message]
2008-09-30 18:25     ` Mark Brown
2008-10-01  6:15       ` Jarkko Nikula
2008-09-30 15:11 ` Alan Horstmann
2008-09-30 15:30   ` Frank Mandarino

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=48E2481D.6030208@endrelia.com \
    --to=fmandarino@endrelia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    --cc=jhnikula@gmail.com \
    --cc=sedji.gaouaou@atmel.com \
    /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