From: Timur Tabi <timur@freescale.com>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev@ozlabs.org,
Phillips Kim-R1AAHA <Kim.Phillips@freescale.com>
Subject: Re: [PATCH][POWERPC] QE: Make QUICC Engine support a configurableoption
Date: Thu, 15 Mar 2007 08:04:50 -0500 [thread overview]
Message-ID: <45F94472.6010803@freescale.com> (raw)
In-Reply-To: <989B956029373F45A0B8AF02970818902DB124@zch01exm26.fsl.freescale.net>
Li Yang-r58472 wrote:
> QE is so generic that can be used across different sub-archs maybe even
> archs. Why doesn't it deserve a place out of "platform support" menu?
> An option in the top menu is another choice.
Yes, but for now, the QE is marketed as an option for a few SOCs. That
means that when you select the SOC, you expect to see configuration
options for that SOC.
> On another thought, it is very unlikely that user chooses a more
> expensive chip with QE and won't use it. So make it non-configurable
> and be selected automatically is not a bad idea for me.
This was addressed earlier. On some boards, the QE is not wired to
anything, so there's no point in enabling it. Disabling it will prevent
any unused QE code from becoming part of the kernel.
next prev parent reply other threads:[~2007-03-15 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 18:15 [PATCH][POWERPC] QE: Make QUICC Engine support a configurable option Kumar Gala
2007-03-14 18:37 ` Kim Phillips
2007-03-14 19:36 ` Timur Tabi
2007-03-15 3:02 ` [PATCH][POWERPC] QE: Make QUICC Engine support a configurableoption Li Yang-r58472
2007-03-15 3:49 ` Kumar Gala
2007-03-15 5:39 ` Li Yang-r58472
2007-03-15 5:40 ` Kumar Gala
2007-03-15 6:29 ` Li Yang-r58472
2007-03-15 13:04 ` Timur Tabi [this message]
2007-03-15 15:07 ` Kumar Gala
2007-03-15 16:47 ` Scott Wood
2007-03-15 16:51 ` Timur Tabi
2007-03-16 19:21 ` Timur Tabi
2007-03-16 19:44 ` Kumar Gala
2007-03-16 20:16 ` Timur Tabi
2007-03-16 19:47 ` Timur Tabi
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=45F94472.6010803@freescale.com \
--to=timur@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=LeoLi@freescale.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).