From: Antonino Daplas <adaplas@pol.net>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Kendall Bennett <KendallB@scitechsoft.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
DirectFB-devel <directfb-dev@directfb.org>
Subject: Re: [ANNOUNCE]: VM86 Daemon
Date: 01 Apr 2003 09:04:47 +0800 [thread overview]
Message-ID: <1049158940.1059.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20030401000746.44732.qmail@web14912.mail.yahoo.com>
On Tue, 2003-04-01 at 08:07, Jon Smirl wrote:
> I didn't read through the code yet, is this being
> implemented by adding some new IOCTLs to the fb
> interface? For example an IOCTL to get the legal modes
> or to reset the card.
>
It uses a dedicated device, /dev/vm86, which is unrelated to fb.
> Why does it need /dev/vm86, couldn't it just use the
> fb device and add some new IOCTLS?
A new device seems more powerful and more generic. Generic in a sense
that other subsystems besides fbdev can use it to access the BIOS or
whatever. More powerful because a dedicated device is also provided
with the functionality of the file system. The daemon uses file
read/write to access data, select/poll to wait for device ready, and 1
ioctl call to let /dev/vm86 know that the daemon is loaded or to be
unloaded. If async IO works for regular files, it will also have that
functionality.
>
> I would expect to the end user app to only interact
> with the /dev/fb, it would be unaware of the daemon.
> This would allow these functions to be transparently
> added to the driver if the need hardware info becomes available.
>
Yes. Behavior of /dev/fbX is still the same, except that when vm86d is
loaded, it provides additional functionality to vesafb. The user will
not notice that vm86d is there, except that he/she and applications can
now change the video mode.
Tony
> =====
> Jon Smirl
> jonsmirl@yahoo.com
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb:
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
next prev parent reply other threads:[~2003-04-01 1:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 9:53 [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01 0:07 ` Jon Smirl
2003-04-01 0:27 ` Kendall Bennett
2003-04-01 1:27 ` Antonino Daplas
2003-04-01 8:29 ` Benjamin Herrenschmidt
2003-04-01 9:41 ` Antonino Daplas
2003-04-01 11:34 ` Benjamin Herrenschmidt
2003-04-01 13:38 ` Antonino Daplas
2003-04-01 13:53 ` Benjamin Herrenschmidt
2003-04-01 15:32 ` Antonino Daplas
2003-04-01 15:22 ` Jon Smirl
2003-04-01 16:25 ` Antonino Daplas
2003-04-01 16:44 ` Benjamin Herrenschmidt
2003-04-01 18:30 ` Small API change Benjamin Herrenschmidt
2003-04-01 20:10 ` Geert Uytterhoeven
2003-04-01 22:03 ` Benjamin Herrenschmidt
2003-04-02 22:01 ` James Simmons
2003-04-02 22:11 ` Benjamin Herrenschmidt
2003-04-01 1:04 ` Antonino Daplas [this message]
2003-04-01 4:01 ` [ANNOUNCE]: VM86 Daemon Jon Smirl
2003-04-01 9:41 ` Antonino Daplas
[not found] ` <20030401120835.GA30421@skunk.convergence.de>
2003-04-01 13:38 ` [directfb-dev] " 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=1049158940.1059.21.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=KendallB@scitechsoft.com \
--cc=directfb-dev@directfb.org \
--cc=jonsmirl@yahoo.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).