From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Lee Revell <rlrevell@joe-job.com>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Adding a new architecture to alsa-driver
Date: Fri, 14 Apr 2006 18:56:36 +0100 [thread overview]
Message-ID: <1145037396.9434.1.camel@localhost.localdomain> (raw)
In-Reply-To: <s5hu0902zyr.wl%tiwai@suse.de>
On Tue, 2006-04-11 at 12:01 +0200, Takashi Iwai wrote:
> At Mon, 10 Apr 2006 21:13:36 -0400,
> Lee Revell wrote:
> >
> > On Mon, 2006-04-10 at 23:06 +0100, Adrian McMenamin wrote:
> > > On Sat, 2006-04-08 at 21:16 -0400, Lee Revell wrote:
> > > > c_opts="-mno-space-regs -mfast-indirect-calls -mschedule=7200
> > > > -mdisable-fpregs"
> > >
> > >
> > > I have tried this patch and it doesn't work. Essentially the aica card
> > > isn't picked up. I think this has something to do with aclocal.m4 or
> > > something similar.
> > >
> > > To be honest I've hit a brick wall and any help at all would be welcome.
> > >
> > >
> >
> > Adrian,
> >
> > OK, here's the working (I think) patch against ALSA CVS.
> >
> > I could not figure out how to add a new arch while leaving the driver in
> > alsa-driver, so this adds it to alsa-kernel.
>
> As I wrote in another post, it's not possible cleanly right now.
> You can include sh/Kconfig from acore/Kconfig, for example, but better
> to fix alsa-driver/utils/mod-deps.c, which generates acinclude.m4 and
> toplevel config.
>
> > diff -Nru alsa-kernel/Makefile alsa-kernel2/Makefile
> > --- alsa-kernel/Makefile 2005-03-22 03:50:46.000000000 -0500
> > +++ alsa-kernel2/Makefile 2006-04-10 19:08:32.000000000 -0400
> > @@ -4,7 +4,7 @@
> > obj-$(CONFIG_SOUND) += soundcore.o
> > obj-$(CONFIG_SOUND_PRIME) += oss/
> > obj-$(CONFIG_DMASOUND) += oss/
> > -obj-$(CONFIG_SND) += core/ i2c/ drivers/ isa/ pci/ ppc/ arm/ synth/ usb/ sparc/ parisc/ pcmcia/ mips/
> > +obj-$(CONFIG_SND) += core/ i2c/ drivers/ isa/ pci/ ppc/ arm/ synth/ usb/ sparc/ parisc/ pcmcia/ mips/ sh/
> >
> > ifeq ($(CONFIG_SND),y)
> > obj-y += last.o
>
> This change is not necessary. Only the changes to Kconfigs are
> required in alsa-kernel tree. Others can be gracefully put solely in
> alsa-driver tree.
>
>
> > diff -Nru alsa-kernel/sh/Makefile alsa-kernel2/sh/Makefile
> > --- alsa-kernel/sh/Makefile 1969-12-31 19:00:00.000000000 -0500
> > +++ alsa-kernel2/sh/Makefile 2006-04-10 18:59:59.000000000 -0400
> > @@ -0,0 +1,2 @@
> > + snd-aica-objs := aica.o
> > + obj-$(CONFIG_SND_AICA) += snd-aica.o
>
> This should go to alsa-driver/sh/Makefile.
>
>
> > diff -Nru alsa-kernel/sh/aica.c alsa-kernel2/sh/aica.c
> > --- alsa-kernel/sh/aica.c 1969-12-31 19:00:00.000000000 -0500
> > +++ alsa-kernel2/sh/aica.c 2006-04-10 18:59:59.000000000 -0400
>
> I don't comment on driver code here.
> Many things I pointed are not fixed yet...
>
>
> > diff -Nru alsa-driver/sh/Makefile alsa-driver2/sh/Makefile
> > --- alsa-driver/sh/Makefile 1969-12-31 19:00:00.000000000 -0500
> > +++ alsa-driver2/sh/Makefile 2006-04-10 19:01:28.000000000 -0400
> > @@ -0,0 +1,10 @@
> > +ifndef SND_TOPDIR
> > +SND_TOPDIR=..
> > +endif
> > +
> > +include $(SND_TOPDIR)/toplevel.config
> > +include $(SND_TOPDIR)/Makefile.conf
> > +
> > +include $(SND_TOPDIR)/alsa-kernel/sh/Makefile
> > +
> > +include $(SND_TOPDIR)/Rules.make
>
> The following should be in this file in replace of
> include $(SND_TOPDIR)/alsa-kernel/sh/Makefile
> snd-aica-objs := aica.o
> obj-$(CONFIG_SND_AICA) += snd-aica.o
>
>
> > diff -Nru alsa-driver/sh/aica.c alsa-driver2/sh/aica.c
> > --- alsa-driver/sh/aica.c 1969-12-31 19:00:00.000000000 -0500
> > +++ alsa-driver2/sh/aica.c 2006-04-10 19:02:31.000000000 -0400
> > @@ -0,0 +1,3 @@
> > +#include "../alsa-kernel/sh/aica.c"
> > +EXPORT_NO_SYMBOLS;
> > +
>
> Also, aica.c and aica.h should be directly here.
>
This worked - in the sense that the alsa setup now tries to compile the
driver. Yes, lots of things weren't fixed, but that was because I
couldn't compile the driver against the alsa sources - I can now do that
so will get on with fixing the driver.
However, I note the alsa anon cvs still seems to be shipping out code
that was meant to be fixed 10 days ago.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-14 17:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 15:35 Adding a new architecture to alsa-driver Adrian McMenamin
2006-04-08 16:03 ` Lee Revell
2006-04-09 0:23 ` Adrian McMenamin
2006-04-09 0:56 ` Lee Revell
2006-04-09 1:04 ` Lee Revell
2006-04-09 10:50 ` Adrian McMenamin
2006-04-09 11:24 ` Jaroslav Kysela
2006-04-09 12:26 ` Adrian McMenamin
2006-04-10 10:19 ` Takashi Iwai
2006-04-09 1:16 ` Lee Revell
2006-04-09 10:52 ` Adrian McMenamin
2006-04-10 22:06 ` Adrian McMenamin
2006-04-10 22:40 ` Lee Revell
2006-04-11 1:13 ` Lee Revell
2006-04-11 10:01 ` Takashi Iwai
2006-04-14 17:56 ` Adrian McMenamin [this message]
2006-04-11 21:37 ` Adrian McMenamin
2006-04-11 21:57 ` Lee Revell
2006-04-11 22:05 ` Adrian McMenamin
2006-04-12 9:38 ` Takashi Iwai
2006-04-08 16:04 ` Lee Revell
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=1145037396.9434.1.camel@localhost.localdomain \
--to=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.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.