public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: VESA FBconsole driver?
Date: 13 Mar 2003 23:24:35 +0100	[thread overview]
Message-ID: <87adfy7vmk.fsf@bytesex.org> (raw)
In-Reply-To: 3E708815.23768.38089C@localhost

"Kendall Bennett" <KendallB@scitechsoft.com> writes:

> No-one has responded to this email, so either no-one remembers this is 
> people think someone else responded to my email ;-)

I remember, but havn't heard anything for a long time and don't know
the current status.

> at references that will help me figure out how the kernel can make 
> callbacks into a user land daemon?

Look how /sbin/{hotplug|modprobe} is called if needed.

> Is there any reason why the vm86() services in the Linux kernel
> cannot be used by other kernel code?

Unlikely.  To ugly to live with (says Linus, and lot of people agree),
and not really needed.  Doing it in userspace also has the advantage
that you can play alot more tricks.  XFree86 for example has a x86
emulator to execute vga bios code on !x86 platforms.  _That_ you
really don't want to do in kernel mode ...

  Gerd

-- 
/join #zonenkinder

  parent reply	other threads:[~2003-03-13 22:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 16:07 "Cross" compilation for s390x Pete Zaitcev
2003-03-12 19:07 ` VESA FBconsole driver? Kendall Bennett
2003-03-13 21:31   ` Kendall Bennett
2003-03-13 22:11     ` Petr Vandrovec
2003-03-13 23:41       ` Kendall Bennett
2003-03-14 10:14         ` Geert Uytterhoeven
2003-03-14 18:25           ` Kendall Bennett
2003-03-14 10:21         ` Helge Hafting
2003-03-13 22:24     ` Gerd Knorr [this message]
2003-03-13 23:41       ` Kendall Bennett
2003-03-14 10:15         ` Helge Hafting
2003-03-14 18:25           ` Kendall Bennett
2003-03-15 18:04             ` Helge Hafting

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=87adfy7vmk.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox