From: Jeremy Katz <katzj@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andres Salomon <dilinger@queued.net>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Jordan Crouse <jordan.crouse@amd.com>,
linux-kernel@vger.kernel.org, dsaxena@laptop.org
Subject: Re: [PATCH] x86 - Make CONFIG_OLPC dependent on CONFIG_MGEODE_LX
Date: Wed, 12 Nov 2008 22:44:58 -0500 [thread overview]
Message-ID: <1226547898.13077.83.camel@aglarond.local> (raw)
In-Reply-To: <s5hbpwlj9w1.wl%tiwai@suse.de>
On Wed, 2008-11-12 at 15:29 +0100, Takashi Iwai wrote:
> At Wed, 12 Nov 2008 08:54:10 -0500, Jeremy Katz wrote:
> > It's not about angering, it's about causing regressions in
> > functionality. Doing this will completely break the ability to run
> > generic distros on the OLPC hardware without a special kernel. Which
> > has been something that a lot of work has gone on upstream to avoid for
> > all sorts of cases (VMI, Xen, SMP, ...).
>
> But, it is broken. The asm/olpc includes asm/geode.h and it refers
> geode_gpio*() there.
The geode_gpio() users in asm/olpc.h are for some defines that really
probably don't belong there and which aren't used elsewhere in the main
tree afaict from a quick grep. I'd be glad to send the patch to remove
it :-)
> > > but what we really need to
> > > do is to make geode_gpio* defined even when we're not specifically
> > > building with MGEODE_LX. I'm not sure how best to do that, but the
> > > answer probably includes using the generic x86 gpio api.
> >
> > This probably needs to be done as a precondition for getting the alsa
> > changes merged or the alsa changes need to have the bits which depend on
> > geode_gpio ripped out until it can be done.
>
> Then let's stop inclusion of asm/geode.h from asm/olpc.h at first.
> Any driver codes including asm/geode.h can be broken potentially
> without a proper dependency.
Yes, but having a driver dependent on building for a specific x86
variant is quite wrong. What would people think about a driver which
was dependent on CONFIG_M586? Keep in mind that CONFIG_M686 wouldn't
then apply...
Jeremy
next prev parent reply other threads:[~2008-11-13 3:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 12:23 Takashi Iwai
2008-11-11 12:54 ` Ingo Molnar
2008-11-11 13:45 ` Takashi Iwai
2008-11-11 13:53 ` Ingo Molnar
2008-11-11 13:58 ` Takashi Iwai
2008-11-11 14:04 ` Ingo Molnar
2008-11-10 4:17 ` Andres Salomon
2008-11-12 10:53 ` Takashi Iwai
2008-11-12 17:04 ` Andres Salomon
2008-11-12 13:54 ` Jeremy Katz
2008-11-12 14:29 ` Takashi Iwai
2008-11-13 3:44 ` Jeremy Katz [this message]
2008-11-13 6:54 ` Takashi Iwai
2008-11-13 15:37 ` Pavel Machek
2008-11-13 15:54 ` Takashi Iwai
2008-11-13 16:14 ` [PATCH] ALSA: cs5535audio: only build OLPC support if MGEODE_LX is defined Andres Salomon
2008-11-13 16:31 ` Takashi Iwai
2008-11-13 17:12 ` Takashi Iwai
2008-11-13 16:38 ` Pavel Machek
2008-11-13 16:42 ` Takashi Iwai
2008-11-13 17:01 ` Andres Salomon
2008-11-13 19:03 ` Ingo Molnar
2008-11-13 23:30 ` Takashi Iwai
2008-11-14 2:38 ` Andres Salomon
2008-11-14 6:54 ` Takashi Iwai
2008-11-14 7:52 ` Pavel Machek
2008-11-14 17:34 ` Jordan Crouse
2008-11-14 18:45 ` Jeremy Katz
2008-11-14 19:24 ` Jordan Crouse
2008-11-14 21:10 ` Andres Salomon
2008-12-10 16:49 ` Takashi Iwai
2008-12-10 18:41 ` Andres Salomon
2008-12-11 7:08 ` Takashi Iwai
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=1226547898.13077.83.camel@aglarond.local \
--to=katzj@redhat.com \
--cc=dilinger@queued.net \
--cc=dsaxena@laptop.org \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®