public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista•com>
To: "Mark A. Greer" <mgreer@mvista•com>
Cc: Brian Waite <waite@skycomputers•com>, linuxppc-dev@lists•linuxppc.org
Subject: Re: 2nd time Annc: Marvell DB64360 platform support patches available
Date: Mon, 29 Sep 2003 18:15:32 -0700	[thread overview]
Message-ID: <3F78D934.50805@mvista.com> (raw)
In-Reply-To: <3F73300F.2050605@mvista.com>


Mark A. Greer wrote:

> Depending on how easy it is to merge the 64260 & 64360 drivers, it may
> be better to just combine them & still use the SDMA method.  But if
> you do keep separte drivers, it would be better to have a 64360 one
> that uses PIO directly on the chip's regs.

BTW, I just 'brute force & ignorance' pushed the gt64260 mpsc into a
64360 kernel and it basically worked so combining the two is probably
the way to go.

Mark


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-09-30  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 13:53 2nd time Annc: Marvell DB64360 platform support patches available Brian Waite
2003-09-25  2:29 ` Mark A. Greer
2003-09-25 13:24   ` Brian Waite
2003-09-25 18:12     ` Mark A. Greer
2003-09-30  1:15       ` Mark A. Greer [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=3F78D934.50805@mvista.com \
    --to=mgreer@mvista$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    --cc=waite@skycomputers$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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