From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/fsl-booke: Add e500mc smp defconfig
Date: Tue, 15 Mar 2011 14:23:52 -0500 [thread overview]
Message-ID: <6D420108-4C51-47C0-896F-80C69F2C725F@kernel.crashing.org> (raw)
In-Reply-To: <AANLkTinJq78ZQbW_r0mJqA884-Mt+a_m6pJSLn-PAGuT@mail.gmail.com>
On Oct 14, 2010, at 8:51 AM, Timur Tabi wrote:
> On Thu, Oct 14, 2010 at 8:25 AM, Kumar Gala =
<galak@kernel.crashing.org> wrote:
>=20
>> +CONFIG_MATH_EMULATION=3Dy
>=20
> Don't these chips have hardware FP?
removed.
>=20
>> +CONFIG_E1000=3Dy
>> +CONFIG_E1000E=3Dy
>=20
> Are you sure you want these on by default? We may use the E1000 cards
> in-house, but I don't know if our customers do.
leaving, customers can always disable
>> +CONFIG_MSDOS_FS=3Dm
>> +CONFIG_VFAT_FS=3Dy
>> +CONFIG_NTFS_FS=3Dy
leaving since we deal with USB flashes and MMC cards which could be =
MSDOS, VFAT, etc.
- k=
prev parent reply other threads:[~2011-03-15 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 13:25 [PATCH] powerpc/fsl-booke: Add e500mc smp defconfig Kumar Gala
2010-10-14 13:51 ` Timur Tabi
2011-03-15 19:23 ` Kumar Gala [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=6D420108-4C51-47C0-896F-80C69F2C725F@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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