All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pavel Roskin <proski@gnu.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Splitting CONFIG_SND_POWERMAC
Date: Mon, 15 Mar 2004 11:50:36 +0100	[thread overview]
Message-ID: <s5hn06iidtv.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0403141654340.10348@portland.hansa.lan>

At Sun, 14 Mar 2004 23:59:51 -0500 (EST),
Pavel Roskin wrote:
> 
> [1  <text/plain; US-ASCII (7bit)>]
> Hello!
> 
> I was compiling Linux 2.6.x for PowerPC and got compile errors:
> 
> sound/built-in.o(.text+0x28828): In function `daca_init_client':
> : undefined reference to `i2c_smbus_write_byte_data'
> sound/built-in.o(.text+0x28840): In function `daca_init_client':
> : undefined reference to `i2c_smbus_write_byte_data'
> sound/built-in.o(.text+0x2885c): In function `daca_init_client':
> : undefined reference to `i2c_smbus_write_block_data'
> 
> and so on.  It turns out CONFIG_SND_POWERMAC should not be enabled without
> CONFIG_I2C.  My first idea was to add a dependency.
> 
> However, the kernel finds Burgundy sound chip on my PowerPC.  The code for
> Burgundy doesn't use I2C.  I have to enable CONFIG_I2C (without any
> drivers) just to satisfy the linker.
> 
> I think ideally the driver should be split into the base powermac driver
> and 3 specific drivers - AWACS, Burgundy and Keywest, the later being
> dependent on I2C.
> 
> The attached patch implements an interim solution - there is still one
> module, but the user can select what hardware the module supports.  Only
> Keywest devices require I2C.

thanks for the patch.

in fact, i've also thought of splitting this stuff (as you can see it
in the code).  the major drawback by split is that you have to detect
what chip is used on your machine.  and on powermac, it's not easy to
guess like PCI soundcards...


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

      reply	other threads:[~2004-03-15 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15  4:59 [PATCH] Splitting CONFIG_SND_POWERMAC Pavel Roskin
2004-03-15 10:50 ` Takashi Iwai [this message]

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=s5hn06iidtv.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=proski@gnu.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 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.