From: Timur Tabi <timur@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: drivers/char/hvc_* and /Documentation/powerpc/hvcs.txt
Date: Wed, 06 Feb 2008 17:16:16 -0600 [thread overview]
Message-ID: <47AA3FC0.4000602@freescale.com> (raw)
In-Reply-To: <20080126010409.GA25717@lixom.net>
Olof Johansson wrote:
> Yep, pretty much. It's real easy to write a new backend to hvc, I've got
> a couple for various bringup environments here as well.
Could you tell me which kernel options I need to set/unset in order to get my
driver to be called? My driver loads and initializes, but its put_char function
is never called. Trying to debug to the console subsystem is making me dizzy.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-02-06 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:39 drivers/char/hvc_* and /Documentation/powerpc/hvcs.txt Timur Tabi
2008-01-26 1:04 ` Olof Johansson
2008-02-06 23:16 ` Timur Tabi [this message]
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=47AA3FC0.4000602@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.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).