From: Ian Molton <spyro@f2s.com>
To: linux-kernel@vger.kernel.org
Cc: david-b@pacbell.net, James.Bottomley@SteelEye.com,
greg@kroah.com, tony@atomide.com, jamey.hicks@hp.com,
joshua@joshuawise.com
Subject: DMA API issues... summary
Date: Sat, 19 Jun 2004 16:11:53 +0100 [thread overview]
Message-ID: <20040619161153.3be26806.spyro@f2s.com> (raw)
In-Reply-To: <1087603453.2135.224.camel@mulgrave>
Ok, heres a summary of the problems we have (feel free to add any more problems).
We have two types of "device": single function devices and 'system on chip' devices which have multiple functions.
Single chip devices may be able to either access system memory directly, or may only be able to access their internal SRAM pool. in the case of the latter the system can either directly access the SRAM or not, depending on the device/bus setup. Its possible the devices may have more than one non-continuous SRAM mapping.
The same goes for SOC devices, however they could come in two 'classes'. In one type, we would essentially have multiple independant devices in a single chip. In another case (which appears to be fairly common) we can have multiple devices sharing a common SRAM pool. its also possible to have some devices sharing the pool and some having their own in the same chip.
Can anyone describe another type of chip we need to accomodate?
next prev parent reply other threads:[~2004-06-19 15:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 18:20 DMA API issues James Bottomley
2004-06-18 18:35 ` Ian Molton
2004-06-18 18:52 ` James Bottomley
2004-06-18 18:57 ` Ian Molton
2004-06-18 19:20 ` David Brownell
2004-06-18 19:44 ` Ian Molton
2004-06-18 19:57 ` James Bottomley
2004-06-18 21:08 ` David Brownell
2004-06-18 21:14 ` James Bottomley
2004-06-18 22:38 ` David Brownell
2004-06-18 23:07 ` James Bottomley
2004-06-18 23:31 ` Ian Molton
2004-06-19 18:23 ` David Brownell
2004-06-19 20:41 ` Russell King
2004-06-19 21:46 ` James Bottomley
2004-06-19 22:49 ` Ian Molton
2004-06-20 13:37 ` James Bottomley
2004-06-20 15:50 ` Ian Molton
2004-06-20 16:26 ` Jeff Garzik
2004-06-20 16:57 ` Ian Molton
2004-06-20 20:15 ` David Brownell
2004-06-20 16:46 ` James Bottomley
2004-06-20 18:02 ` Oliver Neukum
2004-06-20 19:27 ` James Bottomley
2004-06-20 19:34 ` Oliver Neukum
2004-06-20 20:07 ` David Brownell
2004-06-20 20:18 ` David Brownell
2004-06-20 20:02 ` David Brownell
2004-06-18 23:25 ` Ian Molton
2004-06-18 23:29 ` James Bottomley
2004-06-18 23:51 ` Ian Molton
2004-06-19 0:04 ` James Bottomley
2004-06-19 0:14 ` Ian Molton
2004-06-19 3:49 ` James Bottomley
2004-06-20 20:59 ` Jamey Hicks
2004-06-19 15:11 ` Ian Molton [this message]
2004-06-20 20:49 ` DMA API issues... summary Joshua Wise
2004-06-18 19:30 ` DMA API issues James Bottomley
2004-06-18 19:56 ` Ian Molton
2004-06-18 19:22 ` Jamey Hicks
2004-06-18 19:41 ` James Bottomley
2004-06-18 20:02 ` Oliver Neukum
2004-06-18 20:07 ` James Bottomley
2004-06-18 20:14 ` Benjamin Herrenschmidt
2004-06-18 20:24 ` James Bottomley
2004-06-18 21:20 ` Russell King
2004-06-18 23:20 ` Ian Molton
2004-06-20 18:25 ` Deepak Saxena
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=20040619161153.3be26806.spyro@f2s.com \
--to=spyro@f2s.com \
--cc=James.Bottomley@SteelEye.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=jamey.hicks@hp.com \
--cc=joshua@joshuawise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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
Powered by JetHome