linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Update Warp defconfig
Date: Tue, 16 Jun 2009 22:04:43 -0400	[thread overview]
Message-ID: <20090616220443.6b590baa@lappy.seanm.ca> (raw)
In-Reply-To: <20090616112435.20f7b3d9@lappy.seanm.ca>

On Tue, 16 Jun 2009 11:24:35 -0400
Sean MacLennan <smaclennan@pikatech.com> wrote:

> I forgot to include the defconfig in the last set of patches. So you
> don't get to use the shiny new LEDS driver on the warp unless you turn
> it on.
> 
> Enabling hotplug is also very important since we have moved to udev on
> the warp.
> 
> Like most defconfig patches, most of the changes are just the normal
> kernel changes, not warp specific.
> 
> If it is too early, and we want to hold off until say rc4 with
> defconfigs I have no problem with that. I have tried to outline all
> the changes we specifically made. If anybody sees any bad choices with
> options, let me know!
> 
> Cheers,
>    Sean
> 
> * Enable GPIO LEDS
> * Enable LED triggers
> * Move to slub
> * Enable hotplug
> * Enable timestamps on printks
> * Enable UBIFS

Oops, missed an important option in the list:

* Enable in kernel config

If you use Pika's development environment (PADS), you need this
enabled. We use the config to enable certain features, mainly udev.
Without this config, we will assume you have an old Pika kernel without
new features.

Cheers,
   Sean

      reply	other threads:[~2009-06-17  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 15:24 [PATCH] powerpc: Update Warp defconfig Sean MacLennan
2009-06-17  2:04 ` Sean MacLennan [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=20090616220443.6b590baa@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).