From: Brad Boyer <flar@allandria.com>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] dmasound_pmac depends on pmac specific config options
Date: Sat, 22 Oct 2005 16:03:43 -0700 [thread overview]
Message-ID: <20051022230343.GA10060@pants.nu> (raw)
In-Reply-To: <20051022211906.GA5820@suse.de>
On Sat, Oct 22, 2005 at 11:19:06PM +0200, Olaf Hering wrote:
> On Sat, Oct 22, Brad Boyer wrote:
>
> > I disagree. I think a much better solution would be to change the
> > code to be conditionalized internally on PMU support, rather than
> > having #ifdef CONFIG_PM since the functions being called inside
> > that protection are actually out of the PMU code, not the generic
> > power management system. By doing this, you could for example
> > have a kernel compiled for a 1st gen PCI PowerMac without any
> > extra drivers. In this case, you have CUDA and AWACS, but there
> > is no PMU support and no need for sleep notifiers.
>
> May patch would allow that, you need either CUDA or PMU support.
The problem is not that you need CUDA or PMU support. The real
problem is that if you have CONFIG_PM set and do not have
CONFIG_ADB_PMU set, the pmac sound drivers don't compile because
they have calls into the pmu code protected by #ifdef CONFIG_PM,
which isn't enough to ensure that those symbols actually exist.
That code gets into the kernel only if you have CONFIG_PM and
CONFIG_ADB_PMU both set. Your patch will still fail in the
following case:
CONFIG_PM set
CONFIG_CUDA set
CONFIG_ADB_PMU not set
If you enable either of the pmac sound drivers with this setup,
it will fail to compile with exactly the same error.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2005-10-22 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 19:46 [PATCH] dmasound_pmac depends on pmac specific config options Olaf Hering
2005-10-22 19:55 ` [PATCH] snd_powermac " Olaf Hering
2005-10-22 21:01 ` [PATCH] dmasound_pmac " Brad Boyer
2005-10-22 21:19 ` Olaf Hering
2005-10-22 23:03 ` Brad Boyer [this message]
2005-10-22 23:00 ` Benjamin Herrenschmidt
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=20051022230343.GA10060@pants.nu \
--to=flar@allandria.com \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@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 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).