From: Brad House <brad@mcve.com>
To: Brad House <brad@mcve.com>
Cc: Andre Tomt <andre@tomt.net>,
netdev@oss.sgi.com, Francois Romieu <romieu@fr.zoreil.com>,
Jeff Garzik <jgarzik@pobox.com>,
Brad House <brad_mssw@gentoo.org>
Subject: Re: [patches] 2.6.0-test9 - r8169 DMA API conversion
Date: Wed, 19 Nov 2003 20:36:52 -0500 [thread overview]
Message-ID: <3FBC1AB4.3040900@mcve.com> (raw)
In-Reply-To: <3FBC1A72.9020101@mcve.com>
ok, misunderstood again ...
geez .... now I get it ...
he'll apply the 1.6 patch this weekend ... _sigh_
I really must be brain dead today.
-Brad
Brad House wrote:
> yes, I definately misunderstood then ...
> sorry ;)
> I'll just apply the patches to my version and see what happens ;)
>
> -Brad
>
> Andre Tomt wrote:
>
>> On Thu, 2003-11-20 at 01:59, Brad House wrote:
>>
>>> any reason why it's not against the v1.6 ?
>>
>>
>>
>> I think you misunderstood. If I intepret the list correctly, the 1.6
>> changes are in that list (as "your changes (week-end)".)
>>
>>
>>> the current driver is missing support for the
>>> 8110S chip (or at least it doesn't seem to work at all),
>>> so you're cutting out all the chips on the mobos out there.
>>> Haven't looked to see if it's just a PCI ID or other functionality,
>>> but since the V1.2 is from realtek that's in the official
>>> kernel, it would make sense to use the 1.6 patch....
>>
>>
>>
>> IIRC, the realtek one got cleaned up a great deal before entering
>> mainline, both bug-fixes and coding style cleanups. Your patch may
>> revert a lot of that work (I havn't looked at it closely.) Also the
>> changelog differs for the 1.2 entry between the two versions, indicating
>> just this.
>>
>> Lets take one step at a time ;-)
>>
>>
>>>> It is against the original r8169. Once finished, it should look like:
>>>> - first cut at dma api conversion (today)
>>>> - remaining bits of dma api conversion (tomorrow)
>>>> - rx_copybreak (tomorrow)
>>>> - your changes (week-end)
>>>> - big-endian fixes (week-end)
>>>>
>>>> Each part divided in reasonably small patches to ease the
>>>> test/review process.
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2003-11-20 1:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 4:08 [PATCH 2.6.0-test9-bk6] r8169.c update for 8110S support from RTL 1.6 version Brad House
2003-11-18 4:39 ` r8169 and tg3 Jeff Garzik
2003-11-18 4:51 ` Brad House
2003-11-18 10:00 ` Jan Oravec
2003-11-18 11:01 ` David S. Miller
2003-11-18 12:58 ` Francois Romieu
2003-11-19 17:24 ` Jeff Garzik
2003-11-19 18:44 ` Robert Olsson
2003-11-20 0:00 ` [patches] 2.6.0-test9 - r8169 DMA API conversion Francois Romieu
2003-11-20 0:08 ` Brad House
2003-11-20 0:45 ` Francois Romieu
2003-11-20 0:59 ` Brad House
2003-11-20 1:34 ` Andre Tomt
2003-11-20 1:35 ` Brad House
2003-11-20 1:36 ` Brad House [this message]
2003-11-20 1:36 ` Jeff Garzik
2003-11-21 0:36 ` Francois Romieu
2003-11-21 1:38 ` Jeff Garzik
2003-11-21 23:20 ` 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=3FBC1AB4.3040900@mcve.com \
--to=brad@mcve.com \
--cc=andre@tomt.net \
--cc=brad_mssw@gentoo.org \
--cc=jgarzik@pobox.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).