From: Andres Salomon <dilinger@queued.net>
To: cjb@laptop.org
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
jon.nettleton@gmail.com, devel@driverdev.osuosl.org,
dsd@laptop.org
Subject: Re: [PATCH 06/10] olpc_dcon: add config options for XO_1 and XO_1_5, drop hardcoded XO-1 stuff
Date: Thu, 10 Feb 2011 18:01:38 -0800 [thread overview]
Message-ID: <20110210180138.6c7af1ef@queued.net> (raw)
In-Reply-To: <20110210175324.6d40a5ca@queued.net>
Note one subtlety of this patch that I should've mentioned - due to
the Makefile maneuvering, the module has been renamed from olpc_dcon.ko
to olpc-dcon.ko. For things like modprobe and /etc/modules, this
doesn't make a difference. But, it might affect the OLPC'ers.
On Thu, 10 Feb 2011 17:53:24 -0800
Andres Salomon <dilinger@queued.net> wrote:
>
> This adds CONFIG_FB_OLPC_DCON_1 and CONFIG_FB_OLPC_DCON_1_5 options
> for allowing selection of XO-1 and/or XO-1.5 DCON support. In the
> process, it also forces the xo_1.c and xo_1_5.c files to build as
> separate units, correctly selects between XO-1 and XO-1.5 at runtime,
> and adds some hacks to allow xo_1_5.c to build.
>
> This isn't the cleanest patch, but it'll get better as more global
> variables are dropped.
>
> Signed-off-by: Andres Salomon <dilinger@queued.net>
[...]
> diff --git a/drivers/staging/olpc_dcon/Makefile
> b/drivers/staging/olpc_dcon/Makefile index cd8f289..36c7e67 100644
> --- a/drivers/staging/olpc_dcon/Makefile
> +++ b/drivers/staging/olpc_dcon/Makefile
> @@ -1 +1,6 @@
> -obj-$(CONFIG_FB_OLPC_DCON) += olpc_dcon.o
> +olpc-dcon-objs += olpc_dcon.o
> +olpc-dcon-$(CONFIG_FB_OLPC_DCON_1) += olpc_dcon_xo_1.o
> +olpc-dcon-$(CONFIG_FB_OLPC_DCON_1_5) += olpc_dcon_xo_1_5.o
> +obj-$(CONFIG_FB_OLPC_DCON) += olpc-dcon.o
[...]
prev parent reply other threads:[~2011-02-11 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 1:53 [PATCH 06/10] olpc_dcon: add config options for XO_1 and XO_1_5, drop hardcoded XO-1 stuff Andres Salomon
2011-02-11 2:01 ` Andres Salomon [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=20110210180138.6c7af1ef@queued.net \
--to=dilinger@queued.net \
--cc=cjb@laptop.org \
--cc=devel@driverdev.osuosl.org \
--cc=dsd@laptop.org \
--cc=gregkh@suse.de \
--cc=jon.nettleton@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox