From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [ANNOUNCE]: VM86 Daemon
Date: Mon, 31 Mar 2003 16:27:11 -0800 [thread overview]
Message-ID: <3E886C5F.28140.1013B3CA@localhost> (raw)
In-Reply-To: <20030401000746.44732.qmail@web14912.mail.yahoo.com>
Jon Smirl <jonsmirl@yahoo.com> 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.
We definitely want some new IOCTL's to allow the apps to find out what
modes are available, if this has not been added.
> Why does it need /dev/vm86, couldn't it just use the fb device and
> add some new IOCTLS?
Yes, it could. However when Tony discussed this with me a week or so ago,
he figured that since vesafb is just using basic vm86() functions from
the kernel, it is a lot more modular and useful to make the daemon just a
vm86() daemon for kernel code. Then it can be used for other stuff that
has a need to make real mode BIOS calls that just the vesafb driver.
> 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.
As I understand it the /dev/vm86 interface is there solely to implement
the vm86() interfacing to the kernel, which is used by the modified
vesafb driver. Userland apps only ever call the /dev/fb functions via the
standard IOCTL's and never need to care that /dev/vm86 exists or not. It
is clean separation, and as you said if the fb driver can drive the
hardware directly without the need to use the vm86d daemon, it is
transparently ignored by any and all fb console apps ;-)
Regards,
---
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: 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 0:27 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 [this message]
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 ` [ANNOUNCE]: VM86 Daemon Antonino Daplas
2003-04-01 4:01 ` 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=3E886C5F.28140.1013B3CA@localhost \
--to=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).