From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: On-going 4xx porting
Date: Sat, 10 Nov 2007 02:48:13 +0300 [thread overview]
Message-ID: <20071110024813.5cada553@kernel.crashing.org> (raw)
In-Reply-To: <1194645701.3207.17.camel@localhost.localdomain>
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.
> USB (440EP(x), etc)
looks like we have code ready for that...
> I2C
Stefan's approach seems pretty close
> GPIO
> NDFC
I'd rather follow platform device wrapper way.. Big NDFC of_device rework can be done anytime later.
> RTC
>
> I'd also like to try and get the larger page size patches ported and
> merged. If another hugetlbfs type patch shows up, that would be good
> too. There is also the HW watchpoint support patch, and of course new
> board ports.
>
> At some point we should really be able to have a single vmlinux be
> wrapped with different zImage wrappers and .dts files and have it boot
> on those various boards just fine. So I'll be looking at
> accomplishing that as well. That should make new board ports fairly
> easy to do.
>
just my $0.02...
> josh
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-11-09 23:49 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 [this message]
2007-11-10 0:17 ` 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=20071110024813.5cada553@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--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).