From: Stefan Roese <sr@denx.de>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: EMAC: Fix problem with mtu > 4080 on non TAH equipped 4xx PPC's
Date: Wed, 16 Jan 2008 06:34:11 +0100 [thread overview]
Message-ID: <200801160634.11745.sr@denx.de> (raw)
In-Reply-To: <20080115200019.GA2598@gate.ebshome.net>
On Tuesday 15 January 2008, Eugene Surovegin wrote:
> > OK. But how do we detect GigE support? Seems like GigE enabled devices
> > have CONFIG_IBM_EMAC4 defined. If nobody objects I'll fix up another
> > version tomorrow.
>
> Look couple of lines down where I set MTU changing hook. If you cannot
> change MTU you cannot get big frames.
Ahhh, I must have been blind. Thanks for pointing out.
I'll send new patches for ibm_emac and ibm_newemac in a short while.
Best regards,
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Roese <sr@denx.de>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
benh@kernel.crashing.org
Subject: Re: [PATCH] net: EMAC: Fix problem with mtu > 4080 on non TAH equipped 4xx PPC's
Date: Wed, 16 Jan 2008 06:34:11 +0100 [thread overview]
Message-ID: <200801160634.11745.sr@denx.de> (raw)
In-Reply-To: <20080115200019.GA2598@gate.ebshome.net>
On Tuesday 15 January 2008, Eugene Surovegin wrote:
> > OK. But how do we detect GigE support? Seems like GigE enabled devices
> > have CONFIG_IBM_EMAC4 defined. If nobody objects I'll fix up another
> > version tomorrow.
>
> Look couple of lines down where I set MTU changing hook. If you cannot
> change MTU you cannot get big frames.
Ahhh, I must have been blind. Thanks for pointing out.
I'll send new patches for ibm_emac and ibm_newemac in a short while.
Best regards,
Stefan
next prev parent reply other threads:[~2008-01-16 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 12:40 [PATCH] net: EMAC: Fix problem with mtu > 4080 on non TAH equipped 4xx PPC's Stefan Roese
2008-01-15 12:40 ` Stefan Roese
2008-01-15 17:32 ` Eugene Surovegin
2008-01-15 17:32 ` Eugene Surovegin
2008-01-15 19:46 ` Stefan Roese
2008-01-15 19:46 ` Stefan Roese
2008-01-15 20:00 ` Eugene Surovegin
2008-01-15 20:00 ` Eugene Surovegin
2008-01-16 5:34 ` Stefan Roese [this message]
2008-01-16 5:34 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2008-01-16 7:10 Stefan Roese
2008-01-16 7:10 ` Stefan Roese
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=200801160634.11745.sr@denx.de \
--to=sr@denx.de \
--cc=ebs@ebshome.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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.