On Nov 20, 2008, at 1:16 PM, Timur Tabi wrote:
Milton Miller wrote:
Stated differently, if your routine (1) fundamently works one
character
at a time and (2) is not interrupt driven, and (3) only supports one
channel, what avantage is there to an explicit hvc driver?
I think it's because
Milton Miller wrote:
We want the last console= parameter on the command line to win. So if
that implys the last call to add_preferred_console wins, then you have
code overriding the command line.
Hmm, good point. However, how likely is it that we'll have more than one
console driver?
On Nov 21, 2008, at 10:13 AM, Timur Tabi wrote:
Milton Miller wrote:
We want the last console= parameter on the command line to win. So if
that implys the last call to add_preferred_console wins, then you have
code overriding the command line.
Hmm, good point. However, how likely is it that
On Nov 20, 2008, at 6:35 PM, David Gibson wrote:
On Thu, Nov 20, 2008 at 01:07:11PM -0600, Milton Miller wrote:
David Gibson wrote at 2008-11-18 00:28:28:
On Mon, Nov 17, 2008 at 01:41:24PM -0600, Timur Tabi wrote:
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
[EMAIL PROTECTED] wrote:
This
[I'm going to reply to several points in this thread in one reply. I
have restored context that was trimmed in later replys when I wanted to
speak to.]
David Gibson wrote at 2008-11-18 00:28:28:
On Mon, Nov 17, 2008 at 01:41:24PM -0600, Timur Tabi wrote:
On Thu, Oct 23, 2008 at 9:54 PM,
On Thu, Nov 20, 2008 at 01:16:27PM -0600, Timur Tabi wrote:
Milton Miller wrote:
Stated differently, if your routine (1) fundamently works one character
at a time and (2) is not interrupt driven, and (3) only supports one
channel, what avantage is there to an explicit hvc driver?
I
On Thu, Nov 20, 2008 at 01:07:11PM -0600, Milton Miller wrote:
[I'm going to reply to several points in this thread in one reply. I
have restored context that was trimmed in later replys when I wanted to
speak to.]
David Gibson wrote at 2008-11-18 00:28:28:
On Mon, Nov 17, 2008 at
David Gibson wrote:
Um.. yeah.. I'm a bit baffled by this.. all the existing backends
are listed after hvc_console, I just added hvc_udbg to the end. I
didn't really understand the rationale in that commit, but then I
haven't had time to look at it very much yet.
No, some are before:
David Gibson wrote:
Given the variety of strange I/O configurations in prototype and
embedded platforms, I can't imagine this was a unique situation. So
I've pushed my patch out, so anyone else in a similar situation can
immediately turn their little udbg methods for whatever strange I/O
On Tue, Nov 18, 2008 at 09:06:17AM -0600, Timur Tabi wrote:
David Gibson wrote:
Given the variety of strange I/O configurations in prototype and
embedded platforms, I can't imagine this was a unique situation. So
I've pushed my patch out, so anyone else in a similar situation can
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
[EMAIL PROTECTED] 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
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
[EMAIL PROTECTED] wrote:
One other thing ...
--- working-2.6.orig/drivers/char/Makefile 2008-10-22 15:50:59.0
+1100
+++ working-2.6/drivers/char/Makefile 2008-10-24 14:22:59.0 +1100
@@ -50,6 +50,7 @@ obj-$(CONFIG_HVC_BEAT)
On Mon, Nov 17, 2008 at 01:41:24PM -0600, Timur Tabi wrote:
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
[EMAIL PROTECTED] wrote:
This patch adds a new backend for the hvc console based on the
low-level udbg callbacks. This effectively implements a working
runtime console in terms of the
On Mon, Nov 17, 2008 at 02:04:38PM -0600, Timur Tabi wrote:
On Thu, Oct 23, 2008 at 9:54 PM, David Gibson
[EMAIL PROTECTED] 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.
On Mon, Nov 17, 2008 at 6:40 PM, David Gibson
[EMAIL PROTECTED] wrote:
Because the udbg console works for kernel messages, but doesn't
support a full tty interface, so you can't run userspace with only a
udbg console.
I still don't understand the point of your driver. You're just
routing
On Mon, Nov 17, 2008 at 10:42:46PM -0600, Timur Tabi wrote:
On Mon, Nov 17, 2008 at 6:40 PM, David Gibson
[EMAIL PROTECTED] wrote:
Because the udbg console works for kernel messages, but doesn't
support a full tty interface, so you can't run userspace with only a
udbg console.
I still
. Corrected patch below.
powerpc: udbg based backend for hvc_console
This patch adds a new backend for the hvc console based on the
low-level udbg callbacks. This effectively implements a working
runtime console in terms of the simple udbg primitives. This is kind
of a hack - since udbg isn't
David Gibson writes:
This patch adds a new backend for the hvc console based on the
low-level udbg callbacks. This effectively implements a working
runtime console in terms of the simple udbg primitives. This is kind
of a hack - since udbg isn't something you really want to be using
This patch adds a new backend for the hvc console based on the
low-level udbg callbacks. This effectively implements a working
runtime console in terms of the simple udbg primitives. This is kind
of a hack - since udbg isn't something you really want to be using
routinely - but it's really
19 matches
Mail list logo
