From: Richard Hirst <rhirst@linuxcare.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: David Huggins-Daines <dhd@linuxcare.com>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Oops in sim700.c on C360
Date: Fri, 1 Sep 2000 17:26:02 +0100 [thread overview]
Message-ID: <20000901172602.K877@linuxcare.com> (raw)
In-Reply-To: <20000901171233.C1538@parcelfarce.linux.theplanet.co.uk>; from matthew@wil.cx on Fri, Sep 01, 2000 at 05:12:33PM +0100
On Fri, Sep 01, 2000 at 05:12:33PM +0100, Matthew Wilcox wrote:
> And that's clearly hppa_dma_ops being NULL. Before I committed the
> support for PCX-S,T machines, this was initialised to pa11_dma_ops
> but I now leave it uninitialised. If the CPU detection code detects a
> PCX-L or PCX-L2 CPU then hppa_dma_ops gets initialised to pa11_dma_ops.
> If it detects a PCX-S or PCX-T CPU then it initialises it to fail_dma_ops
> (i think richard changed the name recently?). The CCIO support and
> the SBA/LBA support initialise hppa_dma_ops with their respective
> support routines. So I deduce that the CCIO support hasn't recognised
> your machine. Perhaps we should initialise it to a routine which prints
> that the PCI ops haven't been initialised and halts.
switch (boot_cpu_data.cpu_type) {
case pcx:
case pcxs:
case pcxt:
hppa_dma_ops = &pcx_dma_ops;
break;
case pcxl2:
pa7300lc_init();
case pcxl: /* falls through */
hppa_dma_ops = &pcxl_dma_ops;
break;
default:
break;
}
I changed fail_dma_ops to pcx_dma_ops because the only difference between
the two sets of machines is that pci_alloc_consistent fails on pcx. The
other functions referenced by hppa_dma_ops are still valid (pci_map_single,
for example), and are used in sim700 and lasi_82596.
Richard
next prev parent reply other threads:[~2000-09-01 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 15:44 [parisc-linux] Oops in sim700.c on C360 David Huggins-Daines
2000-09-01 16:12 ` Matthew Wilcox
2000-09-01 16:26 ` Richard Hirst [this message]
2000-09-01 16:46 ` 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=20000901172602.K877@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=dhd@linuxcare.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@thepuffingroup.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