alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Stuart Longland <redhatter@gentoo.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: Hooking a TI CODEC to a i.MX27 MCU
Date: Mon, 24 May 2010 11:49:16 +0100	[thread overview]
Message-ID: <1274698156.3064.93.camel@odin> (raw)
In-Reply-To: <20100524074946.GC16346@www.longlandclan.yi.org>

On Mon, 2010-05-24 at 17:49 +1000, Stuart Longland wrote:
> Now this compiles... but when I go to load it; one of two things
> happens... either practically nothing (at this stage; no modules are
> loaded prior to calling modprobe):
> 

It does sound like you have some memory corruption somewhere. Can you
rule out your new CODEC driver by replacing it with another CODEC driver
(ads117x.c is a very simple example).

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2010-05-24 10:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24  7:49 ASoC: Hooking a TI CODEC to a i.MX27 MCU Stuart Longland
2010-05-24 10:49 ` Liam Girdwood [this message]
2010-05-25  0:41   ` Stuart Longland
2010-05-25  2:26     ` Stuart Longland
2010-05-25  3:26       ` Stuart Longland
2010-05-25 16:46       ` gnutoo
2010-05-26 13:21         ` Stuart Longland
2010-05-27  0:47           ` Mark Brown
2010-05-28  2:06             ` Stuart Longland
2010-05-28  5:55               ` Eric Bénard
2010-05-28 11:08                 ` Mark Brown
2010-05-28 13:10                   ` Eric Bénard
2010-06-01  3:30                 ` Stuart Longland
2010-06-01  5:07                   ` Stuart Longland
2010-06-01 11:32                     ` Stuart Longland
2010-06-03 11:14                       ` Mark Brown
2010-06-03 11:43                         ` Stuart Longland
2010-06-03 11:57                           ` Mark Brown
2010-05-28 12:27               ` Mark Brown
2010-05-29  8:59                 ` Stuart Longland

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=1274698156.3064.93.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=redhatter@gentoo.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;
as well as URLs for NNTP newsgroup(s).