From: Brad House <brad@mainstreetsoftworks.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Brad House <brad@mcve.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] 2.6.0-test9-bk27-netdrvr-exp1 - r8169 update
Date: Mon, 24 Nov 2003 13:21:31 -0500 [thread overview]
Message-ID: <3FC24C2B.1030007@mainstreetsoftworks.com> (raw)
In-Reply-To: <20031124184908.A9566@electric-eye.fr.zoreil.com>
Yes, I can do that. These are the patches I applied:
-ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.0-test9-bk25-netdrvr-exp1.patch.bz2
-r8169-mac-phy-version.patch
I did not apply these patches below because your answer suggested that I
should not as per the e-mail on 11/23:
>> cool. Did those previous patches you posted get merged into the
>> current netdrvr-exp1, or do those need to be applied as well ?
> It is built on top of 2.6.0-test9-bk27 + (latest) netdrvr-exp:
These are the patches _NOT_applied:
From 11/20/03
-r8169-start-xmit-fixes.patch
-r8169-dma-api-tx-buffers.patch
-r8169-rx_copybreak.patch
From 11/19/03
-r8169-dma-api-tx.patch
-r8169-dma-api-data-buffers.patch
Let me know where to begin, and I'll do it.
-Brad
Francois Romieu wrote:
> Brad House <brad@mcve.com> :
> [...]
>
>>>2) vanilla 2.6.0-test9 does not work either.
>>
>>correct, but the system doesn't lock up with vanilla -test9,
>>dhcpcd just hangs, then will eventually return.
>
>
> I have fscked something then. Could you apply the patches in order to
> figure which one triggers the lock-up ?
>
> --
> Ueimor
>
--
-----------------------------
Brad House
Sr. Developer
Main Street Softworks, Inc.
brad@mainstreetsoftworks.com
(386) 462-9522 Ext. 112
-----------------------------
next prev parent reply other threads:[~2003-11-24 18:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 18:30 [BK PATCHES] 2.6.x experimental net driver queue Jeff Garzik
2003-11-23 23:09 ` [PATCH] 2.6.0-test9-bk27-netdrvr-exp1 - r8169 update Francois Romieu
2003-11-23 23:18 ` Brad House
2003-11-23 23:40 ` Francois Romieu
2003-11-24 0:02 ` Brad House
2003-11-24 8:04 ` Francois Romieu
2003-11-24 14:40 ` Brad House
2003-11-24 17:49 ` Francois Romieu
2003-11-24 18:21 ` Brad House [this message]
2003-11-24 21:34 ` Francois Romieu
2003-11-25 23:45 ` [PATCH] 2.6.0-test10-bk27-netdrvr-exp1 " Francois Romieu
2003-11-26 0:45 ` Brad House
2003-11-26 0:55 ` r8169 -- bad patch Brad House
2003-11-26 7:57 ` Francois Romieu
2003-11-27 22:51 ` [PATCH] 2.6.0-test11-bk27-netdrvr-exp1 - r8169 update Francois Romieu
2003-11-28 16:46 ` Brad House
2003-11-30 0:47 ` Francois Romieu
2004-01-04 17:00 ` r8169 in netdev experimental Brad House
2004-01-04 22:38 ` Francois Romieu
2004-01-05 22:17 ` [patch] 2.6.1-rc1-mm1 - typo of death in the r8169 driver Francois Romieu
2004-01-06 7:53 ` Jeff Garzik
2004-01-06 23:27 ` [patch] 2.6.1-rc1-mm1 - erroneous __devinitdata " Francois Romieu
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=3FC24C2B.1030007@mainstreetsoftworks.com \
--to=brad@mainstreetsoftworks.com \
--cc=brad@mcve.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).