From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/32] My current serie of patches for 2.6.20 for review
Date: Sat, 11 Nov 2006 17:24:13 +1100 [thread overview]
Message-ID: <1163226253.732808.924875685103.qpush@butch> (raw)
This should be ready for merge in powerpc tree and 2.6.20 as soon
as the merge window opens.
One prerequisite is Geoff's patch testing ppc_md.init_early for
NULL before calling it as I removed pasemi's init_early (now
empty) with the DMA patch.
[Note: Differences since the last version are the renaming of
dev_sysdata to dev_archdata along with a few more cosmetic
mostly changes to that patch, adapting the others to that change,
a bug fix for iseries, and pasemi was missing from the DMA changes,
this version fixes it]
Note that the first 5 ones require specific comments:
* ibmveth: Remove ibmveth "liobn" field
is already queued with Jeff Garzik and will get in 2.6.20
via his merge tree
* Call platform_notify_remove later
is queued in -mm and Andrew sent it to Greg, I expect greg to
merge it in 2.6.20
* Driver core: add notification of bus events
is queued in Greg's tree and scheduled for merge in 2.6.20
* arch provides generic iomap missing accessors
was written by Linus but is not merged yet. He asked me to
resend it when needed, so I'll include it with the other patches
when the merge window opens.
* Add arch specific dev_archdata to struct device
this seems to be generally accepted and should be merged by Greg
or Andrew in 2.6.20
* Change ACPI to use dev_archdata instead of firmware_data
this is a patch that goes along the previous one (though not actually
necessary). It doesn't actually need to go in powerpc.git nor 2.6.20,
I included it in this serie for completeness
This patch set started its life as the support for the new "Axon"
southbridge for cell (which includes such things as MMIO mapped DCR
and 4xx-type devices). However, as things evolved, I ended up doing
a lot more than just the basic support. Among other highlights of
this patch serie are:
- Generic DCR support for both 4xx-type DCRs and MMIO mapped DCR and
MPIC & EMAC changes to work with that
- Souped up of_platform_driver to make it easier to register entire
trees of devices at once, along with PCI host bridge detection support
for 64 bits architectures. Note that some name changes might break
compile of some platforms. I hope to have fixed everything before I
merge but don't forget to tell me if I missed something.
- Completely reworked 64 bits DMA operations
- Possibility to "hook" on PCI MMIO and PCI operations from the platform
code for use by iSeries, Cell and possibly others who have to deal with
weird hypervisor or PCI host bridge erratas. Currently supported only on
64 bits but would be easy to make it work on 32 bits if ever needed.
- Merged 32 and 64 bits io.h. ARCH=powerpc now uses asm-powerpc/io.h
for both. ARCH=ppc still uses the old one in asm-ppc as I really don't
feel like dealing with some of the cruft in there.
- As a consequence of the 2 above, new accessors are available that match
what is done by other architectures: {read,write}{w,l,q}_be for big endian
PCI MMIO accesses, {read,write}s{b,w,l} for MMIO "repeat" operations, and
a significant cleanup of the EEH stuff.
- Cell IOMMU support (mostly written by Jeremy Kerr)
And more ...
next reply other threads:[~2006-11-11 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 6:24 Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-11 6:24 [PATCH 0/32] My current serie of patches for 2.6.20 for review Benjamin Herrenschmidt
2006-11-11 6:24 Benjamin Herrenschmidt
2006-11-10 7:44 Benjamin Herrenschmidt
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=1163226253.732808.924875685103.qpush@butch \
--to=benh@kernel.crashing.org \
--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).