From: Josh Boyer <jwboyer@jdub.homelinux.org>
To: Peter Fercher <peter.fercher@scs.ch>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: emac driver broken in 2.6.12.2 ?
Date: Mon, 19 Sep 2005 08:42:01 -0500 [thread overview]
Message-ID: <1127137322.3211.0.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <004101c5bd1f$3d1b91e0$dbe5fed4@scsad.scs.ch>
On Mon, 2005-09-19 at 15:37 +0200, Peter Fercher wrote:
> hi,
>
> i have problems with the IBM EMAC with 2.6.12.2 (the driver worked
> with 2.4.25)
> running on ppc405EP octobus board. Cross compiled on x86 using the
> eldk-3.1 toolchain
>
> any hints ?
I think you'd need to be more explicit about what "problems" means.
Hard to give hints with what you have here.
josh
next prev parent reply other threads:[~2005-09-19 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 13:37 emac driver broken in 2.6.12.2 ? Peter Fercher
2005-09-19 13:42 ` Josh Boyer [this message]
2005-09-19 13:51 ` Peter Fercher
2005-09-19 14:23 ` Josh Boyer
2005-09-19 14:28 ` Matt Porter
2005-09-19 13:51 ` Stefan Roese
2005-09-19 13:59 ` AW: " David Grab
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=1127137322.3211.0.camel@windu.rchland.ibm.com \
--to=jwboyer@jdub.homelinux.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=peter.fercher@scs.ch \
/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).