From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Subject: On-going 4xx porting
Date: Fri, 09 Nov 2007 16:01:41 -0600 [thread overview]
Message-ID: <1194645701.3207.17.camel@localhost.localdomain> (raw)
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
USB (440EP(x), etc)
I2C
GPIO
NDFC
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.
josh
next reply other threads:[~2007-11-09 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 22:01 Josh Boyer [this message]
2007-11-09 23:48 ` On-going 4xx porting Vitaly Bordug
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=1194645701.3207.17.camel@localhost.localdomain \
--to=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).