linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@embeddedalley.com>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix powerpc 44x_mmu build
Date: Sat, 5 Aug 2006 09:11:57 -0400	[thread overview]
Message-ID: <20060805131157.GA1873@matthew-porters-computer.local> (raw)
In-Reply-To: <1154740342.2847.6.camel@vader.jdub.homelinux.org>

On Fri, Aug 04, 2006 at 08:12:22PM -0500, Josh Boyer wrote:
> On Fri, 2006-08-04 at 11:44 -0500, Matt Porter wrote:
> > The PIN_SIZE definition name changed, update 44x_mmu.c accordingly.
> 
> As far as I know, 4xx still builds as ARCH=ppc...  is this patch just
> something you noticed, or is it a hint that you're working on moving 4xx
> to arch/powerpc?

Yes, working on moving 4xx to arch/powerpc.

> Just curious, since I've been poking at this a bit and would rather not
> duplicate effort.

Sounds great. In fact, I talked to BenH and tgall at ols about this
and they mentioned you were doing some work. These patches are
just some obvious basic things to get started.

Since there's a lot of work here, what aspect are you working on?
I haven't seen anything publicly but hear plenty of talk of people
working on dt soc definitions for 4xx i/o blocks.

I'm currently looking at merging ocotea but am using it to focus
on a few fundamental things like merging over a version of the
non-coherent DMA API implementation. The plan here is to get
a serial-only port merged and then sync with whoever is working
on the definitions and driver changes for the essential drivers
(obviously emac first from my POV).

-Matt`

  reply	other threads:[~2006-08-07 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 16:44 [PATCH] Fix powerpc 44x_mmu build Matt Porter
2006-08-05  1:12 ` Josh Boyer
2006-08-05 13:11   ` Matt Porter [this message]
2006-08-05 16:33     ` 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=20060805131157.GA1873@matthew-porters-computer.local \
    --to=mporter@embeddedalley.com \
    --cc=jwboyer@jdub.homelinux.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).