From: Jason Howard <lists@spectsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Re: DMA from SCSI controller to PCI frame buffer memory.
Date: 14 Dec 2002 12:29:54 -0800 [thread overview]
Message-ID: <1039897793.21189.53.camel@bmagic.spectsoft.com> (raw)
In-Reply-To: <1039837312.25121.115.camel@irongate.swansea.linux.org.uk>
> In theory you can mmap the frame buffer memory, then do O_DIRECT I/O
> into it. In practice it will buffer (I hope it still does). One of the
> problems is that there are huge lists of PCI->AGP DMA errata in
> chipsets.
I am not accessing the AGP bus as my frame buffer is located on the PCI
bus.
00:08.0 Multimedia video controller: Unknown device f1d0:efac
Subsystem: Unknown device f1d0:efac
Flags: bus master, stepping, medium devsel, latency 64, IRQ 10
Memory at f4000000 (32-bit, non-prefetchable) [size=4K]
Memory at f6000000 (32-bit, prefetchable) [size=16M]
(I am working with the second memory address)
Any recommendations on where to start hacking? Would it be a good idea
to add O_DIRECT to a mmaped PCI space? The kernel should not be doing
any buffering whatsoever, as we will be coming close to filling the pci
bus up with transfers from direct disk->fb already. (We are already
doing buffering on the FB card as well)
Jason
--
Jason Howard
Professional:
SpectSoft, LLC
http://www.spectsoft.com jason@spectsoft.com
Phone: +1.209.847.7812 Fax: +1.209.847.7859
Personal:
http://www.psinux.org jason@psinux.org
Cell: +1.209.968.1289
Text Message: jasonsphone@psinux.org
next prev parent reply other threads:[~2002-12-14 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 19:15 DMA from SCSI controller to PCI frame buffer memory Jason Howard
2002-12-14 3:41 ` Alan Cox
2002-12-14 5:24 ` Andrew Morton
2002-12-14 20:29 ` Jason Howard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-15 2:06 Douglas Gilbert
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=1039897793.21189.53.camel@bmagic.spectsoft.com \
--to=lists@spectsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.