From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Defconfig support
Date: Mon, 19 Jan 2009 23:21:36 -0500 [thread overview]
Message-ID: <20090119232136.717eddf3@lappy.seanm.ca> (raw)
Since the list seems quiet right now, thought I would ask a question.
Up till now I haven't really worried about the warp defconfig being up
to date since, realistically, the stock kernel was not usable on the
warp. Since it usually boots from NAND, the lack of an ndfc driver
made it unbootable in a production system.
However, the 2.6.29 kernel will boot, so the defconfig problem becomes
more acute. The problem is keeping the changes that are required for
the warp while also handling the normal changes that happen every
release.
For example, the current git diff shows CONFIG_SIMPLE_GPIO which is
just a new feature and can be safely left unset. But the watchdog made
it into the kernel, so CONFIG_PIKA_WDT should be set for a warp.
Any ideas for a good way of handling this?
Cheers,
Sean
next reply other threads:[~2009-01-20 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 4:21 Sean MacLennan [this message]
2009-01-20 11:29 ` Defconfig support Josh Boyer
2009-01-21 1:09 ` Sean MacLennan
2009-01-21 1:15 ` Josh Boyer
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=20090119232136.717eddf3@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).