Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Grant Grundler <grundler@cup.hp.com>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] CVS linux Vs. -test10
Date: Tue, 21 Nov 2000 22:54:11 -0800	[thread overview]
Message-ID: <3A1B6D93.3B7D2474@uswest.net> (raw)
In-Reply-To: 200011212124.NAA20426@milano.cup.hp.com

Grant Grundler wrote:

> Matthew Wilcox wrote:
> ...
> > Someone (probably me) sends him a patch.  He told me at the Toronto
> > show that he was quite happy to apply anything that only touched those
> > two directories. (oh, and drivers/gsc wouldn't be a problem either).
> > Can I just check that no-one wants to rename drivers/gsc again?  :-)
>
> Hi Mathew,
> I don't and it's a good question.
> I would like a few files moved:
>
> arch/parisc/kernel/ccio-dma.c    -> drivers/gsc/ccio-dma.c
> arch/parisc/kernel/ccio-rm-dma.c -> drivers/gsc/ccio-rm-dma.c

Grant,

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.

I'll double check this in the morning.

- Ryan


>     ccio will *always* be associated with a GSC bus since that's
>     the secondary bus. And ccio supports devices below dino.c which
>     already lives in drivers/gsc.
>
> arch/parisc/kernel/lba_pci.c     -> drivers/ropes/lba_pci.c
> arch/parisc/kernel/sba_iommu.c   -> drivers/ropes/sba_iommu.c
> arch/parisc/kernel/iosapic.c     -> drivers/ropes/iosapic.c
>
>     lba/sba code is equivalent to dino/ccio code for another set
>     of platforms. And long term, I'm certain iosapic.c does not
>     belong under arch/parisc. I can do this move if there are no
>     major objections.
>
> Any reason why we couldn't do these moves *after* you submit a patch?
>
> FWIW, here are issues I see with merging IA64 iosapic code with mine:
> o iosapic "discovery" (I invented register_iosapic() interface for parisc)
> o parisc PDC calls (initialization)
> o interrupt policy decisions (eg EOI generation and picking a CPU)
> o I don't have time to do it in the near future.
>
> Folks working on IA64 stuff inside HP need to think about:
> (a) if they want to do the merge any time soon
> (b) which iosapic.c they want to start with
> (c) where the final version should live
>
> thanks,
> grant
>
> Grant Grundler
> Unix Systems Enablement Lab
> +1.408.447.7253
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

  parent reply	other threads:[~2000-11-22  5:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14 16:35 [parisc-linux] CVS linux Vs. -test10 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 [this message]
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
  -- 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-22  8:11 John Marvin
2000-11-22 19:55 ` Grant Grundler
2000-11-22 20:10   ` Kirk Bresniker

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=3A1B6D93.3B7D2474@uswest.net \
    --to=rbradetich@uswest.net \
    --cc=grundler@cup.hp.com \
    --cc=matthew@wil.cx \
    --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