From: Pavel Machek <pavel@suse.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jeremy Katz <katzj@redhat.com>,
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: Thu, 13 Nov 2008 16:37:14 +0100 [thread overview]
Message-ID: <20081113153714.GA1520@ucw.cz> (raw)
In-Reply-To: <s5h63msru7z.wl%tiwai@suse.de>
> > > > > 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.
>
> Not so. Many drivers are very hardware-specific, and they are (must
> be) based on certain architectures and platforms. Look at a bunch of
> drivers based on ARM-variants, for example.
No.
It should be possible to compile kernel for i386 and have it run on
OLPC. This breaks it.
CPU type is optimalization option, only.
> IMO, the basic problem is rather that the platform and the CPU
> selection is mixed up. The geode GPIO stuff shouldn't belong to CPU
> selection.
ACK... and suggested patch makes it worse.
There should be option 'support OLPC' somewhere, and that should
enable the gpio bits. Alsa driver should depend on that one.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-13 15:37 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
2008-11-13 6:54 ` Takashi Iwai
2008-11-13 15:37 ` Pavel Machek [this message]
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=20081113153714.GA1520@ucw.cz \
--to=pavel@suse.cz \
--cc=dilinger@queued.net \
--cc=dsaxena@laptop.org \
--cc=jordan.crouse@amd.com \
--cc=katzj@redhat.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®