From: Eugene Surovegin <ebs@ebshome.net>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: Mark Powell <medp@primagraphics.co.uk>,
linuxppc-embedded@lists.linuxppc.org,
Davey <daveywu@transengines.com>,
stefan.roese@esd-electronics.com
Subject: Re: patch for ibm 405ep emac driver in linux-2.4.22 and 2.4.23
Date: Wed, 24 Dec 2003 21:49:09 -0800 [thread overview]
Message-ID: <20031225054909.GA24915@gate.ebshome.net> (raw)
In-Reply-To: <20031223101022.A23655@home.com>
On Tue, Dec 23, 2003 at 10:10:22AM -0700, Matt Porter wrote:
>
> On Tue, Dec 23, 2003 at 10:12:15AM +0000, Mark Powell wrote:
> >
> > Davey wrote:
> >
> > >Some time ago Stefan and I had reported that both ethernet interfaces
> > >cannot work well together. Sorry I have lost all old mails when I
> > >reinstall my computer. We have find that this problem is caused by
> > >that the base address of eht1 is wrong set. Follow by my patch for
> > >linux-2.4.22 and linux-2.4.23. I have test the patch and it work well.
> >
> > shouldn't that just be:
>
> This is the right way to do it, we can't put that other hack in the
> kernel. If somebody verifies this patch hen we can get it in.
>
Matt, I checked old-OCP version of ibm405ep.c and indeed it had
EMAC1_BASE there. Obviously this is a typo introduced during
conversion to new OCP.
I checked these definitions when Stefan first reported the problem
but failed to notice this :-(.
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-25 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 20:23 Free ppc linux configuation tool? Kerl, John
2003-12-19 23:42 ` listmember
2003-12-22 15:10 ` Jeff Angielski
2003-12-23 7:10 ` patch for ibm 405ep emac driver in linux-2.4.22 and 2.4.23 Davey
2003-12-23 10:12 ` Mark Powell
2003-12-23 17:10 ` Matt Porter
2003-12-24 2:30 ` Davey
2003-12-25 5:49 ` Eugene Surovegin [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=20031225054909.GA24915@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=daveywu@transengines.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=medp@primagraphics.co.uk \
--cc=mporter@kernel.crashing.org \
--cc=stefan.roese@esd-electronics.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;
as well as URLs for NNTP newsgroup(s).