Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John Marvin <jsm@udlkern.fc.hp.com>
To: parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] CVS linux Vs. -test10
Date: Wed, 22 Nov 2000 01:11:57 -0700 (MST)	[thread overview]
Message-ID: <200011220811.BAA14756@udlkern.fc.hp.com> (raw)

> Ryan Bradetich wrote:
> > Do you really want to merget the ccio-rm-dma.c file into Linus's tree?
> > It is just a reference file used to construct the real ccio-dma.c file ... I
> > don't believe it is referenced anywhere.
>
> Hi Ryan,
> Yes I do. It is supposed to work for ccio+PCX-W platforms (eg C360).
> Keeping it arround will document the pro/con's of that approach and
> give folks who have time (and the right machine) something to experiment
> with instead of writing it from scratch.  If someone finds an application
> it's good for (short transactions with low latency requirements perhaps),
> it's worth having around.
>
> It's not referenced because I didn't add a CONFIG_CCIO_RM_IOMMU flag
> or ccio_rm_init() call to drivers/gsc/gsc.c:gsc_init().  You are welcome
> add this CONFIG flag by hacking arch/parisc/config.in and defconfig.
> If you do, please add rules which only allow one or the other
> CONFIG_CCIO* option to be enabled.
>
Well, personally i'd vote to get rid of it. It works for ONE machine only,
and MAY have an advantage in some small case. But if we keep it, lets make
sure that it is real clear that it should NOT be the default choice.

It should be marked CONFIG_EXPERIMENTAL, and the text associated with it
should clearly show that it works on a C360 only. If possible, it should
also be made clear that ccio-dma.c works for C360, so people who have
C360's don't think they have to choose ccio-rm-dma.c.

Grant, I hope you are prepared to answer the parisc-linux mailing list
questions this is going to generate once parisc-linux starts becoming more
visible.  Another FAQ entry perhaps? :-)

John Marvin
jsm@fc.hp.com

             reply	other threads:[~2000-11-22  8:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  8:11 John Marvin [this message]
2000-11-22 19:55 ` [parisc-linux] CVS linux Vs. -test10 Grant Grundler
2000-11-22 20:10   ` Kirk Bresniker
  -- strict thread matches above, loose matches on Subject: below --
2000-11-22  6:50 John Marvin
2000-11-22  7:56 ` Grant Grundler
2000-11-22 16:02 ` Paul Bame
2000-11-14 16:35 Paul Bame
2000-11-18  7:24 ` Matthew Wilcox
2000-11-20  7:44   ` Grant Grundler
2000-11-20 11:17     ` Matthew Wilcox
2000-11-20 17:34       ` Grant Grundler
2000-11-21 11:34         ` Matthew Wilcox
2000-11-21 21:24           ` Grant Grundler
2000-11-22  0:53             ` Matthew Wilcox
2000-11-22  6:54             ` Ryan Bradetich
2000-11-22  7:18               ` Grant Grundler
2000-11-22 20:11             ` Grant Grundler
2000-11-30  8:09         ` Stephen Zander
2000-11-30 15:44           ` Randolph Chung
2000-11-30 16:16           ` Alan Cox
2000-11-30 16:18           ` Paul Bame
2000-11-20 19:23   ` Grant Grundler

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=200011220811.BAA14756@udlkern.fc.hp.com \
    --to=jsm@udlkern.fc.hp.com \
    --cc=parisc-linux@puffin.external.hp.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