From: Alex Bennee <kernel-hacker@bennee.com>
To: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Userspace DMA
Date: Tue, 18 Nov 2003 15:09:17 +0000 [thread overview]
Message-ID: <1069168156.31133.11.camel@cambridge.braddahead.com> (raw)
Now my mailer is fixed :-)
-----Forwarded Message-----
> From: Alex Bennee <kernel-hacker@bennee.com>
> To: Peter Chubb <peter@chubb.wattle.id.au>
> Cc: public@mikl.as, Linux Mailing List <linux-kernel@vger.kernel.org>
> Subject: Re: Userspace DMA
> Date: Mon, 17 Nov 2003 10:37:40 +0000
>
> On Mon, 2003-11-17 at 04:34, Peter Chubb wrote:
> > >>>>> "Andrew" == Andrew Miklas <public@mikl.as> writes:
> > Andrew> Hi, Is there an accepted way of doing userspace DMA with
> > Andrew> Linux?
> >
> > I'm currently working on a framework for user-space device drivers,
> > that allow suitably privileged user-space programs to set up and tear
> > down dma regions
>
> Hi,
>
> I've also been doing some work on allowing user processes to access the
> DMA hardware facilities of the processor platform. This is not actually
> aimed at pci stuff but used for other devices on the embedded SH board I
> use. It works using a packetised writev interface to send DMA requests
> to kernel space where the mapping of memory is done. It really works
> best with scatter gather dma as user-pages can be spread out all over
> the place.
>
> Whether there is any overlap between my approach, what your doing and
> what Andrew is looking for I have no idea :-) I'm certainly interested
> in seeing any code if only for ideas.
>
> You can find an alpha (but working on my system) copy of the code at:
>
> http://www.bennee.com/~alex/software/kernel/index.php
--
Alex, homepage: http://www.bennee.com/~alex/
I used to get high on life but lately I've built up a resistance.
next reply other threads:[~2003-11-18 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 15:09 Alex Bennee [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-16 23:42 Andrew Miklas
2003-11-17 4:34 ` Peter Chubb
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=1069168156.31133.11.camel@cambridge.braddahead.com \
--to=kernel-hacker@bennee.com \
--cc=linux-kernel@vger.kernel.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®