linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: On-going 4xx porting
Date: Fri, 09 Nov 2007 18:17:22 -0600	[thread overview]
Message-ID: <1194653842.3207.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20071110024813.5cada553@kernel.crashing.org>

On Sat, 2007-11-10 at 02:48 +0300, Vitaly Bordug wrote:
> On Fri, 09 Nov 2007 16:01:41 -0600
> Josh Boyer wrote:
> 
> > Hi All,
> > 
> > For those interested, I have a few things I'd like to focus on for
> > 2.6.25 in regards to the current arch/powerpc 4xx porting effort.
> > Below is a brief list of drivers in no particular order:
> > 
> > PCI support
> I'll look at that stuff once again. maybe it worths to head fir compromise solution in favor of replacing 32/64 
> ranges parsing func + a bunch of other things in one single step.

Sure, that's fine.  You and Ben were working on it at one point, so I
figured you would look at it again.

> > USB (440EP(x), etc)
> looks like we have code ready for that...

It's mostly there, yes.  Should be pretty easy to get in :).

> > I2C
> Stefan's approach seems pretty close

Agreed.

> > GPIO
> > NDFC
> I'd rather follow platform device wrapper way.. Big NDFC of_device rework can be done anytime later.

I would seriously consider that too.

josh

      reply	other threads:[~2007-11-10  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 22:01 On-going 4xx porting Josh Boyer
2007-11-09 23:48 ` Vitaly Bordug
2007-11-10  0:17   ` Josh Boyer [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=1194653842.3207.20.camel@localhost.localdomain \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=vitb@kernel.crashing.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).