From: James Bottomley <James.Bottomley@SteelEye.com>
To: Greg KH <greg@kroah.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Problems with 2.5.14 PCI reorg and non-PCI architectures
Date: Thu, 09 May 2002 09:00:28 -0400 [thread overview]
Message-ID: <200205091300.g49D0TY01841@localhost.localdomain> (raw)
In-Reply-To: Message from Greg KH <greg@kroah.com> of "Thu, 09 May 2002 01:44:24 PDT." <20020509084424.GC15460@kroah.com>
greg@kroah.com said:
> arch/i386/pci/dma.c now only contains pci_alloc_consistent() and
> pci_free_consistent(). What kind of configuration are you using that
> works without CONFIG_PCI and yet calls those functions? Is it a
> ISA_PNP type configuration? Do you have a .config that this fails on?
The problem is that this is not necessarily PCI related on other platforms.
My cross platform SCSI driver, 53c700.c, uses pci_alloc_consistent because it
has to work on parisc archs as well (which do have consistent memory even
though a few of them don't have PCI busses). It was failing a test compile.
I can manipulate the #ifdefs so that it doesn't use the consistent allocation
functions on x86, but I think, in principle, cross platform drivers should be
able to use these functions.
> I'd be glad to move it back, but I'd like to understand who is using
> those functions outside of the pci and isa_pnp drivers.
Yes, please. If you look at a lot of the non-x86 arch drivers, some of them
also use pci_alloc_consistent. I think the only other x86 example I can come
up with is aic7xxx_old which also supports the 7770 chip which is used for
SCSI in the intel xpress motherboard (pure EISA).
James
next prev parent reply other threads:[~2002-05-09 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 23:11 James Bottomley
2002-05-09 8:44 ` Greg KH
2002-05-09 13:00 ` James Bottomley [this message]
2002-05-09 15:23 ` Greg KH
2002-05-09 16:47 ` James Bottomley
2002-05-09 16:52 ` [BK PATCH] PCI reorg fix Greg KH
2002-05-09 18:06 ` Patrick Mochel
2002-05-09 17:15 ` Greg KH
2002-05-09 18:26 ` James Bottomley
2002-05-09 18:23 ` Kai Germaschewski
2002-05-09 18:26 ` Patrick Mochel
2002-05-09 18:46 ` Kai Germaschewski
2002-05-09 19:45 ` Martin Dalecki
2002-05-09 21:34 ` James Bottomley
2002-05-09 20:51 ` Martin Dalecki
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=200205091300.g49D0TY01841@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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
all inboxes | Powered by JetHome®