From: "Timur Tabi" <timur@freescale.com>
To: david@gibson.dropbear.id.au, "Paul Mackerras" <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: powerpc: udbg based backend for hvc_console
Date: Mon, 17 Nov 2008 14:04:38 -0600 [thread overview]
Message-ID: <ed82fe3e0811171204y4e8de21dy18f5b332b7f05f1f@mail.gmail.com> (raw)
In-Reply-To: <20081024035434.GF4267@yookeroo.seuss>
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
<david@gibson.dropbear.id.au> wrote:
> This can be used to quickly implement a userspace usable console while
> you're working on a proper driver for whatever console I/O device the
> hardware has. Or, it can be used to avoid writing a full blown
> tty/console driver entirely for quick-and-dirty I/O hardware that will
> later be replaced by something else.
Ok, I think I understand this better now.
Your approach seems backwards to me. HVC console client drivers
already have simple put/get functions. You've written an hvc driver
that makes udbg calls. Wouldn't it have been better to make a udbg
driver that makes hvc calls? That way, you effectively give udbg
support to all hvc drivers in one shot.
In order to support udbg in my hvc driver, I have to add udbg calls.
In fact, now that I've thought about it, I don't understand what your
driver does. You take hvc callbacks and route them through udbg, but
this only works on drivers that have udbg callbacks in the first
place. In that case, why would these drivers need an hvc middle-man?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-11-17 20:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 3:54 powerpc: udbg based backend for hvc_console David Gibson
2008-11-05 4:53 ` Paul Mackerras
2008-11-06 0:20 ` David Gibson
2008-11-17 19:41 ` Timur Tabi
2008-11-18 0:28 ` David Gibson
2008-11-17 20:04 ` Timur Tabi [this message]
2008-11-18 0:40 ` David Gibson
2008-11-18 4:42 ` Timur Tabi
2008-11-18 5:14 ` David Gibson
2008-11-18 15:06 ` Timur Tabi
2008-11-19 0:42 ` David Gibson
2008-11-19 15:20 ` Timur Tabi
2008-11-20 19:07 ` Milton Miller
2008-11-20 19:16 ` Timur Tabi
2008-11-21 0:23 ` David Gibson
2008-11-21 15:57 ` Milton Miller
2008-11-21 16:13 ` Timur Tabi
2008-11-21 19:09 ` Milton Miller
2008-11-21 0:35 ` David Gibson
2008-11-21 19:29 ` Milton Miller
2008-11-17 20:18 ` 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=ed82fe3e0811171204y4e8de21dy18f5b332b7f05f1f@mail.gmail.com \
--to=timur@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).