From: Ralf Baechle <ralf@linux-mips.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jeff Garzik <jgarzik@pobox.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux/m68k on Mac <linux-mac68k@mac.linux-m68k.org>,
Linux MIPS <linux-mips@vger.kernel.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH] Jazzsonic driver updates
Date: Thu, 16 Jun 2005 10:22:57 +0100 [thread overview]
Message-ID: <20050616092257.GE5202@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0506160336410.24908@loopy.telegraphics.com.au>
On Thu, Jun 16, 2005 at 03:45:54AM +1000, Finn Thain wrote:
> > ... the chip then decides where in that area the recieved packet gets
> > buffered ... and that is why I was asking for an alternative to
> > vdma_log2phys...
>
> But I forgot that it is possible to have the sonic chip store no more than
> one packet in each buffer before moving to the next one in the ring
> (though this isn't the case at present). So, as you say, vdma_log2phys
> isn't really required.
Using that option doesn't really seem a good idea anyway.
Ralf
next prev parent reply other threads:[~2005-06-16 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503070210.j272ARii023023@hera.kernel.org>
2005-03-22 17:13 ` [PATCH] Jazzsonic driver updates Geert Uytterhoeven
2005-03-23 2:30 ` [PATCH] " Finn Thain
2005-03-23 10:01 ` Ralf Baechle
2005-03-23 10:47 ` Finn Thain
2005-06-12 6:05 ` Finn Thain
2005-06-15 11:41 ` Ralf Baechle
2005-06-15 14:02 ` Finn Thain
2005-06-15 14:27 ` Ralf Baechle
2005-06-15 16:53 ` Finn Thain
2005-06-15 17:45 ` Finn Thain
2005-06-16 9:22 ` Ralf Baechle [this message]
2005-06-16 12:14 ` Finn Thain
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=20050616092257.GE5202@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mac68k@mac.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).