From: Andrew Morton <akpm@linux-foundation.org>
To: "Anders Grafström" <grfstrm@users.sourceforge.net>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
Jeff Garzik <jeff@garzik.org>,
e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, miltonm@bga.com,
David Acker <dacker@roinet.com>,
stable@kernel.org
Subject: Re: [PATCH] Fix e100 on systems that have cache incoherent DMA
Date: Wed, 2 Jul 2008 10:45:55 -0700 [thread overview]
Message-ID: <20080702104555.b4f0186f.akpm@linux-foundation.org> (raw)
In-Reply-To: <486BBC90.8030708@users.sourceforge.net>
On Wed, 02 Jul 2008 19:36:16 +0200 Anders Grafstr__m <grfstrm@users.sourceforge.net> wrote:
> Andrew Morton wrote:
> > On Tue, 01 Jul 2008 05:49:47 -0400 Jeff Garzik <jeff@garzik.org> wrote:
> >
> >> Andrew Morton wrote:
> >>> On Thu, 19 Jun 2008 14:38:33 +0200 Anders Grafstr__m <grfstrm@users.sourceforge.net> wrote:
> >>>
> >>>> David Acker wrote:
> >>>>> May I ask what actual board you are using and how the e100 is connected
> >>>>> to it? I plan to test with miniPCI based e100 cards. Also, can you say
> >>>>> more about it being broke? Does it crash immediately, fail to move any
> >>>>> data, move some data and stop, etc. ?
> >>>> It's a custom board based on the IXDP425 reference design.
> >>>> IXP420 with 82551ER integrated on the same board.
> >>>> Both RX and TX appears to stop shortly after the driver has been initialized.
> >>>> It never recovers after the "exec cuc_dump_reset failed" messages start to show.
> >>> So.. where are we with this?
> >> It's in net-2.6, davem's 2.6.26-rc queue.
> >>
> >
> > ah, thanks. Is it needed in 2.6.25.x?
>
> I think so.
OK. It's in Jeff's hands now, so I'm out of the loop.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
next prev parent reply other threads:[~2008-07-02 17:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 18:17 [PATCH] Fix e100 on systems that have cache incoherent DMA Auke Kok
2007-11-28 19:12 ` David Acker
2007-11-28 19:21 ` Kok, Auke
2007-11-28 19:26 ` Jeff Garzik
2007-11-28 19:50 ` David Acker
2008-06-18 18:54 ` Anders Grafström
2008-06-18 19:16 ` David Acker
2008-06-19 12:38 ` Anders Grafström
2008-07-01 8:26 ` Andrew Morton
2008-07-01 9:49 ` Jeff Garzik
2008-07-01 18:07 ` Andrew Morton
2008-07-02 17:36 ` Anders Grafström
2008-07-02 17:45 ` Andrew Morton [this message]
2008-07-01 21:35 ` David Acker
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 13:27 David Acker
2007-11-02 16:05 ` Kok, Auke
2007-11-02 16:11 ` Jeff Garzik
2007-11-06 17:01 ` Kok, Auke
2007-08-31 20:54 David Acker
2007-09-04 17:02 ` Kok, Auke
2007-09-07 16:31 ` Kok, Auke
2007-09-07 20:41 ` David Acker
2007-09-07 21:03 ` Kok, Auke
2007-09-07 21:18 ` Kok, Auke
2007-09-07 23:24 ` Jeff Garzik
2007-09-11 20:54 ` David Acker
2007-09-12 11:30 ` James Chapman
2007-09-12 20:11 ` David Acker
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=20080702104555.b4f0186f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=dacker@roinet.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=grfstrm@users.sourceforge.net \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@intel.com \
--cc=miltonm@bga.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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.