From: Vitaly Bordug <vbordug@ru.mvista.com>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/6] Add mpc8560 support to powerpc
Date: Fri, 23 Jun 2006 23:12:34 +0400 [thread overview]
Message-ID: <20060623191234.14374.13540.stgit@localhost.localdomain> (raw)
This is a first preliminary series to move 8560ads to powerpc and hence finish
85xx family in terms of merge. Subsequient fs_enet/PAL patches are required
for the following to work, but submitted here as reference only
(will be updated and sent to netdev shortly).
ATM not all points are adressed, there still may be bugs, but in general it works.
Most of the SoC stuff (UARTs, Gig eth, 100BaseT FCC) as well as the PCI stuff are
functional.
All the comments are greatly appreciated.
--
Sincerely, Vitaly
next reply other threads:[~2006-06-23 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 19:12 Vitaly Bordug [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-23 23:59 [PATCH 0/6] Add mpc8560 support to powerpc Vitaly Bordug
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=20060623191234.14374.13540.stgit@localhost.localdomain \
--to=vbordug@ru.mvista.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).