linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: Kendall Bennett <KendallB@scitechsoft.com>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Finding Aki M Laukkanen's VESAFBD project?
Date: Fri, 14 Mar 2003 15:22:54 -0800 (PST)	[thread overview]
Message-ID: <20030314232254.8987.qmail@web14904.mail.yahoo.com> (raw)
In-Reply-To: <3E71EDDB.915.5AD977E@localhost>

You can do it either way. With blocking IO you would
need one thread per adapter. With the signal method
you can be single threaded and sleep waiting for a
signal. Both styles will work.

With single threaded you make an array of handles for
the framebuffers. When you get a signal you do poll()
on the array. For each active poll you will need to do
the IOCTL. Keep looping on poll/IOCTL until the poll
goes inactive, then sleep waiting for a SIGIO.

--- Kendall Bennett <KendallB@scitechsoft.com> wrote:
> Jon Smirl <jonsmirl@yahoo.com> wrote:
> 
> > I noticed the email but I wasn't sure if you knew
> about the code
> > from the way your mail was worded. 
> 
> ;-)
> 
> > I used fasync and poll to implement user space
> communications in a
> > driver I just finished.  Use kill_fasync(&fasync,
> SIGIO) from the
> > device driver to signal the user app. The signal
> causes the app to
> > poll which the driver replies POLLIN to. Polling
> identifies which
> > device caused the signal. Now the user app knows
> it needs to IOCTL
> > the handle to do whatever the driver needs it to.
> It only takes
> > about 100 lines of code to implement the
> communication. 
> 
> Does the user space daemon block waiting to be woken
> up from the kernel 
> module? I think the way Aki had it done initially
> was to have the user 
> space daemon call into the kernel via an ioctl() or
> something, and the 
> kernel would block on that thread and when something
> needed to be done, 
> it would fill in the return structure for the
> ioctl() and then unblock 
> the thread. The user space daemon would process the
> ioctl() and and then 
> call it agin once the service was completed.
> 
> Does that system make sense at all?
> 
> Thanks!
> 
> ---
> Kendall Bennett
> Chief Executive Officer
> SciTech Software, Inc.
> Phone: (530) 894 8400
> http://www.scitechsoft.com
> 
> ~ SciTech SNAP - The future of device driver
> technology! ~
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge
> is now open! 
> Get cracking and register here for some mind
> boggling fun and 
> the chance of winning an Apple iPod:
>
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel


=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

  reply	other threads:[~2003-03-14 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 18:37 Finding Aki M Laukkanen's VESAFBD project? Kendall Bennett
2003-03-14 18:56 ` Jon Smirl
2003-03-14 19:42   ` Kendall Bennett
2003-03-14 20:11     ` Jon Smirl
2003-03-14 22:57       ` Kendall Bennett
2003-03-14 23:22         ` Jon Smirl [this message]
2003-03-15  9:52 ` Geert Uytterhoeven
2003-03-17 18:22   ` Kendall Bennett
2003-03-16 23:00 ` Antonino Daplas
2003-03-17 18:22   ` Kendall Bennett
2003-03-17 21:39     ` Antonino Daplas

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=20030314232254.8987.qmail@web14904.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=KendallB@scitechsoft.com \
    --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).