From: Eugene Surovegin <ebs@ebshome.net>
To: John Otken <jotken@softadvances.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Support for AMCC Yosemite 440EP Eval Board
Date: Wed, 27 Jul 2005 08:59:51 -0700 [thread overview]
Message-ID: <20050727155950.GA28681@gate.ebshome.net> (raw)
In-Reply-To: <42E776DD.9080307@softadvances.com>
On Wed, Jul 27, 2005 at 06:58:21AM -0500, John Otken wrote:
> This patch adds support for the new AMCC Yosemite 440EP Eval
> Board. I tested it on the both Bamboo and Yosemite boards
> using the 2.6.12 kernel.
>
> This patch has three dependencies:
> 2005-04-07 Wade Farnsworth's PPC440EP SoC and Bamboo board support
Why this old one? Updated patch was posted yesterday.
> 2005-07-20 My fix invalid function name usb_hcd_put in ohci-ppc-soc.c
> 2005-07-27 My Support 440EP On-Chip OHCI USB Host Controller
>
> http://patchwork.ozlabs.org/linuxppc/patch?id=1311
> http://patchwork.ozlabs.org/linuxppc/patch?id=1803
> http://patchwork.ozlabs.org/linuxppc/patch?id=1855
>
> Comments are welcome.
Well, why don't you make separate board port instead if hacking
Bamboo one?
IMHO, direction you are going is creating a lot of mess. If there is
some common parts between Bamboo and Yosemite, the right way is to
factor out this stuff from Bamboo port.
Also, your patch is mangled - some lines are wrapped.
--
Eugene
next prev parent reply other threads:[~2005-07-27 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 11:58 [PATCH] Support for AMCC Yosemite 440EP Eval Board John Otken
2005-07-27 13:47 ` Stefan Roese
2005-07-27 15:59 ` Eugene Surovegin [this message]
2005-07-27 16:29 ` Matt Porter
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=20050727155950.GA28681@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=jotken@softadvances.com \
--cc=linuxppc-embedded@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).