From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [PATCH] enable built-in networking for Sequoia defconfig
Date: Wed, 9 Jan 2008 15:42:38 +0100 [thread overview]
Message-ID: <200801091542.38914.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20080109060723.06885abd@zod.rchland.ibm.com>
On Wednesday 09 January 2008 13:07, Josh Boyer wrote:
> On Wed, 9 Jan 2008 12:16:25 +0100
> Matthias Fuchs <matthias.fuchs@esd-electronics.com> wrote:
>
> > Josh,
> >
> > Where did you apply this patch to? Couldn't find it in your for-2.6.25 branch.
>
> I applied it there, just haven't pushed it out yet. Will do that today.
>
> > BTW, is it normal to edit the defconfig file by hand?
>
> The defconfig? Not sure. What I normally do is a make foo_defconfig,
> edit the .config, make oldconfig, and copy the resulting .config back
> to foo_defconfig.
Yes, this is what I also do.
But how did Hollis get these lines into .config or sequoia_defconfig:
+CONFIG_IBM_NEW_EMAC=y
+CONFIG_IBM_NEW_EMAC_RXB=128
+CONFIG_IBM_NEW_EMAC_TXB=64
+CONFIG_IBM_NEW_EMAC_POLL_WEIGHT=32
+CONFIG_IBM_NEW_EMAC_RX_COPY_THRESHOLD=256
+CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0
I did not find any Kconfigs where these might come from.
Any hint?
Matthias
next prev parent reply other threads:[~2008-01-09 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 23:26 [PATCH] enable built-in networking for Sequoia defconfig Hollis Blanchard
2008-01-08 16:09 ` Josh Boyer
2008-01-09 11:16 ` Matthias Fuchs
2008-01-09 12:07 ` Josh Boyer
2008-01-09 14:42 ` Matthias Fuchs [this message]
2008-01-09 15:06 ` Stefan Roese
2008-01-09 15:21 ` Josh Boyer
2008-01-09 15:39 ` Matthias Fuchs
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=200801091542.38914.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=hollisb@us.ibm.com \
--cc=jwboyer@linux.vnet.ibm.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).