All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean MacLennan <seanm@seanm.ca>
To: <linuxppc-dev@ozlabs.org>
Subject: Warp patches for 2.6.26
Date: Sat, 12 Apr 2008 13:48:31 -0400	[thread overview]
Message-ID: <20080412134831.424480cf@lappy.seanm.ca> (raw)

I was going to hold off until the warp was officially released, but we
might miss the merge window. So here they are. A lot of work has been
done since 2.6.25 and I haven't been submitting patches to keep down on
the churn.

We standardized on a 4M NOR flash and a 256M NAND flash. But there is
still support for the original Rev A boards which where 64M NOR and 64M
NAND. You will see fixups for the Rev A. The Rev A is considered
obsolete and the fixups are only there for me to use good ol' Tigger.

ftp://ftp.seanm.ca/stuff/tigger.jpg

Here is the full list of files that need to be patched for a warp,
basically git diff --name-only origin/for-2.6.26:

arch/powerpc/boot/cuboot-warp.c
arch/powerpc/boot/dts/warp.dts
arch/powerpc/configs/warp_defconfig
arch/powerpc/platforms/44x/warp-nand.c
arch/powerpc/platforms/44x/warp.c

drivers/hwmon/Kconfig
drivers/hwmon/Makefile
drivers/hwmon/ad7414.c

drivers/i2c/busses/Kconfig
drivers/i2c/busses/i2c-ibm_iic.c

drivers/leds/Kconfig
drivers/leds/Makefile
drivers/leds/leds-warp.c

drivers/mmc/core/sd.c
drivers/mmc/host/Kconfig
drivers/mmc/host/Makefile
drivers/mmc/host/pikasd.c

drivers/mtd/nand/Kconfig
drivers/mtd/nand/ndfc.c

drivers/net/ibm_newemac/mal.c
drivers/net/ibm_newemac/zmii.c

drivers/scsi/Kconfig

drivers/watchdog/Kconfig
drivers/watchdog/Makefile
drivers/watchdog/pika_wdt.c

include/linux/mmc/host.h
include/linux/pika.h

I will not include patches for all of them since many haven't changed
and/or are waiting for submission to the kernel. So I have broken it up
into five patches.

I will submit any other patches people are interested in.

Cheers,
   Sean

             reply	other threads:[~2008-04-12 17:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 17:48 Sean MacLennan [this message]
2008-04-12 18:01 ` [PATCH 1/5] Boot code Sean MacLennan
2008-04-13  0:49   ` Josh Boyer
2008-04-13  2:06     ` Sean MacLennan
2008-04-12 18:03 ` PATCH 2/5] Platform code Sean MacLennan
2008-04-13  3:15   ` Sean MacLennan
2008-04-14 16:00   ` David Woodhouse
2008-04-12 18:09 ` [PATCH 3/5] Defconfig Sean MacLennan
2008-04-12 18:10 ` [PATCH 4/5] LED driver Sean MacLennan
2008-04-13  0:41   ` Josh Boyer
2008-04-17 17:32     ` Sean MacLennan
2008-04-13 12:28   ` Peter Korsgaard
2008-04-13 16:51     ` Sean MacLennan
2008-04-13 17:34       ` Peter Korsgaard
2008-04-13 17:51         ` Sean MacLennan
2008-04-12 18:11 ` [PATCH 5/5] WDT driver Sean MacLennan
2008-04-13  0:40   ` Josh Boyer
2008-04-14  8:33   ` Laurent Pinchart
2008-04-14 15:40     ` Sean MacLennan
2008-04-13  0:44 ` Warp patches for 2.6.26 Stephen Rothwell
2008-04-13  0:50   ` Josh Boyer
2008-04-13  1:55   ` Sean MacLennan
2008-04-13  2:09     ` Grant Likely
2008-04-13  2:38       ` Sean MacLennan
2008-04-13  3:13         ` Dale Farnsworth
2008-04-17 15:50           ` Sean MacLennan
2008-04-17 16:08             ` Dale Farnsworth
2008-04-17 17:26               ` Sean MacLennan
2008-04-17 18:11                 ` Dale Farnsworth
2008-04-13  1:11 ` Paul Mackerras
2008-04-13  2:24 ` 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=20080412134831.424480cf@lappy.seanm.ca \
    --to=seanm@seanm.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.