From: NiQingliang <niqingliang@insigma.com.cn>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: the mpc8315's compile option
Date: Thu, 23 Jun 2011 13:29:52 +0800 [thread overview]
Message-ID: <1308806992.28060.24.camel@localhost.localdomain> (raw)
In-Reply-To: <4E02A911.9060701@windriver.com>
done!
http://bugzilla.pokylinux.org/show_bug.cgi?id=1192
but it is the first time for me to use bugzilla, so if some misplay, let
me know, thanks!
On Thu, 2011-06-23 at 10:46 +0800, Bruce Ashfield wrote:
> On 11-06-22 9:55 PM, NiQingliang wrote:
> > mpc8315's core is e300c3, why use "tune-ppc603e.inc"?
>
> The 603e represented a lowest common denominator tune file
> when the BSP was introduced, and it was available in poky at
> the time.
>
> We simply haven't revisited the tuning for the BSP yet, since
> what we have works at the moment.
>
> >
> > I think there should be an file named "tune-ppce300c3.inc"? I can find
> > it in openembedded.
>
> I'd definitely like to see patches that provide better tuning for this
> BSP. So patches are welcome. Although at the moment, I'm not aware
> of any plans to revisit the tuning.
>
> Perhaps you'd like to log this as an enhancement request in the
> yocto bugzilla ? That way we can be sure that it isn't forgotten.
>
> Cheers,
>
> Bruce
>
> >
> >
>
--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@insigma.com.cn
BLOG: http://niqingliang2003.wordpress.com
prev parent reply other threads:[~2011-06-23 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 1:55 the mpc8315's compile option NiQingliang
2011-06-23 2:46 ` Bruce Ashfield
2011-06-23 5:29 ` NiQingliang [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=1308806992.28060.24.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.