linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Badaire <mbadaire20@yahoo.fr>
To: Linux-fbdev-devel@lists.sourceforge.net
Subject: FB through DMA
Date: Mon, 09 Feb 2004 23:01:59 +0100	[thread overview]
Message-ID: <868yjb29pk.fsf@debian.baz.net> (raw)

Hi,

I am sorry if it is not the right place to ask this question.

I am currently using an hauppauge PVR-350 with tv-out.
The driver for this card (http://ivtv.sourceforge.net/) expose a framebuffer driver.
We have a direct access to the mem of this card and therefore the fb kernel driver was easy.

Now my problem comes from the fact that I want to avoid to write directly to the 
RAM of the card but I want to send the frame via DMA(via an ioctl).

I suceed to make some ugly modif to fbdev.c by
- define my new ioctl in fbdevhw.c
- using the shadow options
- define my own buffer through a malloc (call it memBuf) 
- change FBDevWindowLinear to give memBuf back (for shadowUpdatePacked to write in it)
- define my own FBshadowUpdatePacked (and pass it for shadowAdd())
- FBshadowUpdatePacked calls shadowUpdatePacked and then calls 
the ioctl with memBuf as a parameter for the card to dma the memBuf.

Now I am quite sure it is not the right way to do it (I hear some laughing already).
Could somebody tell me in a nutshell how I should have implemented this.

I know the way I did this, it is now irrelevant to FrameBuffer, as I am not using 
the mmap of the kernel fb driver, but maybe some people could help me here?

Thx

M


 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

                 reply	other threads:[~2004-02-09 23:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=868yjb29pk.fsf@debian.baz.net \
    --to=mbadaire20@yahoo.fr \
    --cc=Linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).