linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@ozlabs.org>
Subject: [RFC/PATCH 0/9] powerpc: 4xx PCI work in progress
Date: Mon, 19 Nov 2007 19:25:00 +1100	[thread overview]
Message-ID: <1195460700.350036.781662541765.qpush@grosgo> (raw)

Because a mailing list is the best of backups and I've get something
working allright on ebony right now, I figured I would post my WIP
pile of patch bringing PCI to the 44x arch/powerpc world.

At this stage, only ebony is hooked up, there's a known problem with
the SCSI layer and non-coherent architecture that causes random
corruption for which I'm trying to find a solution, and e1000 has a
problem with resources > 32 bits for which I have a separate patch.

             reply	other threads:[~2007-11-19  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  8:25 Benjamin Herrenschmidt [this message]
2007-11-19  8:25 ` [RFC/PATCH 1/9] powerpc: Make isa_mem_base common to 32 and 64 bits Benjamin Herrenschmidt
2007-11-19 10:32   ` Christoph Hellwig
2007-11-19 19:49     ` Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 2/9] powerpc: Merge pci_process_bridge_OF_ranges() Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 3/9] powerpc: Fix declaration of pcibios_free_controller Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 4/9] powerpc: Fix powerpc 32 bits resource fixup for 64 bits resources Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 5/9] powerpc: Fix 440/440A machine check handling Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 6/9] powerpc: Add xmon function to dump 44x TLB Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 7/9] powerpc: Fix kmalloc alignmenent on non-coherent DMA Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 8/9] powerpc 4xx PCI support Benjamin Herrenschmidt
2007-11-19  8:25 ` [RFC/PATCH 9/9] powerpc: PCI support for 4xx Ebony board 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=1195460700.350036.781662541765.qpush@grosgo \
    --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).