From: Timur Tabi <timur@freescale.com>
To: linuxppc-dev@ozlabs.org
Subject: drivers/char/hvc_* and /Documentation/powerpc/hvcs.txt
Date: Fri, 25 Jan 2008 16:39:27 -0600 [thread overview]
Message-ID: <479A651F.2070109@freescale.com> (raw)
Hi,
I'm working on a console driver for the Freescale hypervisor. I notice a bunch
of hvc_* files in the drivers/char directory. I also noticed
/Documentation/powerpc/hvcs.txt.
My guess is that hvcs.txt talks about drivers/char/hvcs.c, which is a console
driver specific to some IBM hypervisor. The hvc_*.c files are based on that
code but they're more generic and allow people to write console drivers for
other hypervisors easliy. Am I right?
If so, does this mean that I can take hvc_beat.c, modify it to make Freescale
hypervisor calls instead, and presto, I'm done?
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2008-01-25 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:39 Timur Tabi [this message]
2008-01-26 1:04 ` drivers/char/hvc_* and /Documentation/powerpc/hvcs.txt Olof Johansson
2008-02-06 23:16 ` Timur Tabi
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=479A651F.2070109@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).