From: Alan Cox <alan@redhat.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Alan Cox <alan@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] Re: VIA "Velocity" Gigabit ethernet driver
Date: Mon, 31 May 2004 19:01:34 -0400 [thread overview]
Message-ID: <20040531230134.GC31056@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040601003503.A19358@electric-eye.fr.zoreil.com>
On Tue, Jun 01, 2004 at 12:35:03AM +0200, Francois Romieu wrote:
> Some polish attached. I'll probably do the rx_copybreak thing as well as
> some pci_dma_sync_single_for_{cpu/device} if nobody beats me.
>
> Apparently there's no documentation available for the chipset, right ?
I have some documentation but its not what I would call complete. The docs are
marked NDA etc etc but identical to the ones you'll find included with the
current driver zip (the .exe is also a zip) on viaarena ;)
prev parent reply other threads:[~2004-05-31 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040526174018.GA29119@devserv.devel.redhat.com>
2004-05-31 22:35 ` [PATCH] Re: VIA "Velocity" Gigabit ethernet driver Francois Romieu
2004-05-31 23:01 ` Alan Cox [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=20040531230134.GC31056@devserv.devel.redhat.com \
--to=alan@redhat.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).