<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.console">
    <title>gmane.linux.console</title>
    <link>http://blog.gmane.org/gmane.linux.console</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/250"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/248"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/247"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/242"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/240"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/221"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/209"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/199"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/181"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/166"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/161"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/136"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/90"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/77"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/76"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/75"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/74"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/73"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/72"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.console/71"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/250">
    <title>wishlist: vnc framebuffer device?</title>
    <link>http://comments.gmane.org/gmane.linux.console/250</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

To make a headless system "less headless", would it be possible
to integrate a vnc framebuffer device into the kernel?

The idea is to have a vnc server instead of a local screen and
keyboard to show the boot output and to provide a console login
on /dev/tty{1..6}. It would be pretty similar to qemu. No need
for fancy graphics, of course. The IP address might either be
obtained using DHCP, or it might use an IP address/netmask
given on the kernel command line.

I understand that authentication might be an issue here.

Hopefully this isn't one of the oh-no-not-again questions. I
haven't seen it mentioned on the kernel or linux-console
mailing lists before.


Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk/caG4ACgkQUTlbRTxpHjf8EwCZAZ0H17WYyEwJB3QgCNjazY2O
3NMAn2e0dJa3sbiZr33nY11m1g0zm0j3
=MANA
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the bod&lt;/pre&gt;</description>
    <dc:creator>Harald Dunkel</dc:creator>
    <dc:date>2012-06-16T11:05:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/248">
    <title>Different scan code behavior in X and console</title>
    <link>http://comments.gmane.org/gmane.linux.console/248</link>
    <description>&lt;pre&gt;Hi there,

Sorry to bother. Not sure whether it is correct to post this question
to the mail list, but can't find a suitable linux console user mail
list for discussing this. If you have good mail list to suggest,
please help me to forward. Thanks!

The question is: I tried to make my emacs have the same key response
on both X and console (ssh pts). However, I can't find scan code for
"Ctrl-PageDown" in console mode. I attached the code for testing the
scan code, and below is different behavior in X and console:

============= X ===========
Press a Key 338   // Just type &amp;lt;PageDown&amp;gt;
Press a Key 27
Press a Key 91
Press a Key 54
Press a Key 59
Press a Key 53
Press a Key 126  // 6-chars for &amp;lt;Ctrl-PageDown&amp;gt;
============ Console =========
Press a Key 338  // Same for &amp;lt;PageDown&amp;gt;
Press a Key         // No response for &amp;lt;Ctrl-PageDown&amp;gt;

Any idea on this? Greatly appreciate your replies, your suggested
readings, and so on!

Best Regards,
Lamu Guo

=============Below is text of the code, for easily reading to skip
attac&lt;/pre&gt;</description>
    <dc:creator>郭晓峰</dc:creator>
    <dc:date>2012-01-15T00:52:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/247">
    <title>Need advice on performant text-mode output API</title>
    <link>http://comments.gmane.org/gmane.linux.console/247</link>
    <description>&lt;pre&gt;Hi. I develop the program that visualizes disk checking process.
Similarly to known DOS program, MHDD.
To get the idea, you can find screencasts of its usage on Youtube.
Or look at my program's screenshot:
http://cloud.github.com/downloads/krieger-od/whdd/whdd_screenshot5.png
So i need to update big zone at left, and stats in top right corner.
The point is that it can be ~1000 blocks processed per second,
although it is ok to render them each Nth time, like at each 10-50
blocks processed.
Currently i use ncurses, and its performance is unacceptable, the
screen blinks awfully, because it prints whole screen of chars on
refresh.

I ask for directing me to any sufficiently performant libs/API, to
replace ncurses.
It would be ok, and even nice, if it is plain text mode (80x25, 16
colors), without any overhead of representing my chars as graphical
points.
It would be _very_ nice, if that API provide 'windows' model in terms
of ncurses, to work with rectangular pieces.
No OS portability is required. Linux only is &lt;/pre&gt;</description>
    <dc:creator>Andrey Utkin</dc:creator>
    <dc:date>2011-12-24T15:57:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/242">
    <title>[PATCH] drivers/tty: don't use the byte channel handle as a parameter in ehv_bytechan.c</title>
    <link>http://comments.gmane.org/gmane.linux.console/242</link>
    <description>&lt;pre&gt;The ePAPR hypervisor byte channel console driver only supports one byte
channel as a console, and the byte channel handle is stored in a global
variable.  It doesn't make any sense to pass that handle as a parameter
to the console functions, since these functions already have access to the
global variable.

This change also fixes this compilation warning on a 64-bit kernel:

  CC      drivers/tty/ehv_bytechan.o
drivers/tty/ehv_bytechan.c: In function 'ehv_bc_console_write':
drivers/tty/ehv_bytechan.c:289:24: warning: cast from pointer to integer of different size
drivers/tty/ehv_bytechan.c: In function 'ehv_bc_console_init':
drivers/tty/ehv_bytechan.c:355:24: warning: cast to pointer from integer of different size

This warning is because the driver is converting the integer byte channel
handle to/from the void* 'data' field of struct console.  Rather than fix
the warning, we just eliminate the code altogether.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 drivers/tty/ehv_bytechan.c |    7 ++-----
 1&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-09-20T18:26:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/240">
    <title>[PATCH] [v3] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/240</link>
    <description>&lt;pre&gt;The ePAPR embedded hypervisor specification provides an API for "byte
channels", which are serial-like virtual devices for sending and receiving
streams of bytes.  This driver provides Linux kernel support for byte
channels via three distinct interfaces:

1) An early-console (udbg) driver.  This provides early console output
through a byte channel.  The byte channel handle must be specified in a
Kconfig option.

2) A normal console driver.  Output is sent to the byte channel designated
for stdout in the device tree.  The console driver is for handling kernel
printk calls.

3) A tty driver, which is used to handle user-space input and output.  The
byte channel used for the console is designated as the default tty.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 arch/powerpc/include/asm/udbg.h |    1 +
 arch/powerpc/kernel/udbg.c      |    2 +
 drivers/tty/Kconfig             |   34 ++
 drivers/tty/Makefile            |    1 +
 drivers/tty/ehv_bytechan.c      |  888 ++++++++++++++++++++++++++++++++++++++&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-07-09T00:06:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/221">
    <title>[PATCH 7/7] [v6] drivers/virt: introduce Freescale hypervisor management driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/221</link>
    <description>&lt;pre&gt;Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.

The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:

1. An ioctl interface for querying and managing partitions

2. A file interface to reading incoming doorbells

3. An interrupt handler for shutting down the partition upon receiving the
   shutdown doorbell from a manager partition

4. A kernel interface for receiving callbacks when a managed partition
   shuts down.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 Documentation/ioctl/ioctl-number.txt |    1 +
 drivers/Kconfig                      |    2 +
 drivers/Makefile                     |    3 +
 drivers/virt/Kconfig                 |   32 ++
 drivers/virt/Makefile                |    5 +
 drivers/virt/fsl_hypervisor.c        |  937 ++++++++++++++++++++++++++++++++++
 include/linux/Kbuild                 |    1 +
 incl&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-06-09T20:52:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/209">
    <title>[PATCH 7/7] [v5] drivers/virt: introduce Freescale hypervisor management driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/209</link>
    <description>&lt;pre&gt;Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.

The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:

1. An ioctl interface for querying and managing partitions

2. A file interface to reading incoming doorbells

3. An interrupt handler for shutting down the partition upon receiving the
   shutdown doorbell from a manager partition

4. A kernel interface for receiving callbacks when a managed partition
   shuts down.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 drivers/Kconfig                |    2 +
 drivers/Makefile               |    3 +
 drivers/virt/Kconfig           |   32 ++
 drivers/virt/Makefile          |    5 +
 drivers/virt/fsl_hypervisor.c  |  983 ++++++++++++++++++++++++++++++++++++++++
 include/linux/Kbuild           |    1 +
 include/linux/fsl_hypervisor.h |  231 ++++++++++
 7 files changed, 1257 insertion&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-06-09T19:13:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/199">
    <title>[PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/199</link>
    <description>&lt;pre&gt;Add the drivers/virt directory, which houses drivers that support
virtualization environments, and add the Freescale hypervisor management
driver.

The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:

1. An ioctl interface for querying and managing partitions

2. A file interface to reading incoming doorbells

3. An interrupt handler for shutting down the partition upon receiving the
   shutdown doorbell from a manager partition

4. An interface for receiving callbacks when a managed partition shuts down.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 drivers/Kconfig                |    2 +
 drivers/Makefile               |    3 +
 drivers/virt/Kconfig           |   22 +
 drivers/virt/Makefile          |    5 +
 drivers/virt/fsl_hypervisor.c  |  961 ++++++++++++++++++++++++++++++++++++++++
 include/linux/Kbuild           |    1 +
 include/linux/fsl_hypervisor.h |  214 +++++++++
 7 files changed, 1208 insertions(+), 0 del&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-06-08T22:45:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/181">
    <title>[PATCH 7/7] [v3] drivers/misc: introduce Freescale hypervisor management driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/181</link>
    <description>&lt;pre&gt;The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:

1. An ioctl interface for querying and managing partitions

2. A file interface to reading incoming doorbells

3. An interrupt handler for shutting down the partition upon receiving the
   shutdown doorbell from a manager partition

4. An interface for receiving callbacks when a managed partition shuts down.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 drivers/misc/Kconfig           |    7 +
 drivers/misc/Makefile          |    1 +
 drivers/misc/fsl_hypervisor.c  |  954 ++++++++++++++++++++++++++++++++++++++++
 include/linux/Kbuild           |    1 +
 include/linux/fsl_hypervisor.h |  214 +++++++++
 5 files changed, 1177 insertions(+), 0 deletions(-)
 create mode 100644 drivers/misc/fsl_hypervisor.c
 create mode 100644 include/linux/fsl_hypervisor.h

diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index d80dcde..3e016b3 100644
--- a/drivers/misc/Kconfig
+++ &lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-06-03T20:47:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/166">
    <title>[PATCH 7/7] [v2] drivers/misc: introduce Freescale hypervisor management driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/166</link>
    <description>&lt;pre&gt;The Freescale hypervisor management driver provides several services to
drivers and applications related to the Freescale hypervisor:

1. An ioctl interface for querying and managing partitions

2. A file interface to reading incoming doorbells

3. An interrupt handler for shutting down the partition upon receiving the
   shutdown doorbell from a manager partition

4. An interface for receiving callbacks when a managed partition shuts down.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 drivers/misc/Kconfig           |    7 +
 drivers/misc/Makefile          |    1 +
 drivers/misc/fsl_hypervisor.c  |  941 ++++++++++++++++++++++++++++++++++++++++
 include/linux/Kbuild           |    1 +
 include/linux/fsl_hypervisor.h |  203 +++++++++
 5 files changed, 1153 insertions(+), 0 deletions(-)
 create mode 100644 drivers/misc/fsl_hypervisor.c
 create mode 100644 include/linux/fsl_hypervisor.h

diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index d80dcde..3e016b3 100644
--- a/drivers/misc/Kconfig
+++ &lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-06-01T18:35:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/161">
    <title>[PATCH 6/7] [v2] tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver</title>
    <link>http://comments.gmane.org/gmane.linux.console/161</link>
    <description>&lt;pre&gt;The ePAPR embedded hypervisor specification provides an API for "byte
channels", which are serial-like virtual devices for sending and receiving
streams of bytes.  This driver provides Linux kernel support for byte
channels via three distinct interfaces:

1) An early-console (udbg) driver.  This provides early console output
through a byte channel.  The byte channel handle must be specified in a
Kconfig option.

2) A normal console driver.  Output is sent to the byte channel designated
for stdout in the device tree.  The console driver is for handling kernel
printk calls.

3) A tty driver, which is used to handle user-space input and output.  The
byte channel used for the console is designated as the default tty.

Signed-off-by: Timur Tabi &amp;lt;timur&amp;lt; at &amp;gt;freescale.com&amp;gt;
---
 arch/powerpc/include/asm/udbg.h |    1 +
 arch/powerpc/kernel/udbg.c      |    2 +
 drivers/tty/Kconfig             |   33 ++
 drivers/tty/Makefile            |    1 +
 drivers/tty/ehv_bytechan.c      |  888 ++++++++++++++++++++++++++++++++++++++&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2011-05-19T18:34:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/136">
    <title>signal to PID 1 from serial console like KeyboardRequest or CAD</title>
    <link>http://comments.gmane.org/gmane.linux.console/136</link>
    <description>&lt;pre&gt;Hi,

I ran into a problem recently on a Linux server with a remote serial 
console.  /sbin/init (actually Upstart) was in a state where nothing 
(useful) was running.  I had to power cycle the machine to get back to 
the boot prompt.  This has the side-effect of triggering raid rebuilds.

It would be nice to have what Ctrl-Alt-Del does at the VGA console with 
PS/2 or USB keyboard. This sends a SIGINT to PID 1, and most distros 
have this set to do "shutdown -r now" which attempts a clean reboot.

Once upon a time there was KeyboardRequest, which would send a SIGWINCH 
to PID 1 (when pressing Alt-UP_arrow?).  I don't see any sign of this 
feature in Linux 2.6.32 though.

Looking at the Sysrq handlers in the kernel I don't see any keystrokes 
that send SIGINT to PID 1 either.

So, I'm wondering if it makes sense to add a Sysrq key to send a signal 
to PID1 ?

&lt;/pre&gt;</description>
    <dc:creator>Jeremy Jackson</dc:creator>
    <dc:date>2011-03-11T13:43:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/90">
    <title>VT console need rewrite</title>
    <link>http://comments.gmane.org/gmane.linux.console/90</link>
    <description>&lt;pre&gt;Hi, there

I'm implementing the UNICODE font of the framebuffer console, (see
http://lkml.org/lkml/2010/11/26/50 in case you do not got my email). But
current vt code is too bugy, too many direct assumes about vt buffer,
This makes me so hard to hack.  There is TODO telling me to add UNICODE
support, but no room for such code, that's why my patch is so tricky.

And the code itself, if you'll excuse me, it isn't as beautiful as rest
of the kernel.
So, it really really need a clean rewrite.I'm ganna take is hard job.
And, please tell me if is worth to do so.


--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Microcai</dc:creator>
    <dc:date>2010-11-28T10:57:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/77">
    <title>[PATCH 1/2] Kernel fbcon UNICODE font support</title>
    <link>http://comments.gmane.org/gmane.linux.console/77</link>
    <description>&lt;pre&gt;Hi, 

 I know there are most people speaking only English, and never meet
non-ASCII characters on console. But, hey , what about others ?
 Then, some of you may come up with a idea than ,there is already fbterm
than supports non-ASCII characters in user-space.
 But, what if you forgot to run fbterm ? And what about some program
that must be run on native tty console ? Or I just want init script
display fine Native Language?

 So, here is the solution: Making framebuffer console handle UNICODE font in
kernel.
 The first thing I need to handle is that, currently there is no room
for adding UNICODE font, only 8bit for characters, how can you do?
 Also , some characters are double-width. So the solution is  make an
backing store. 0xFE and 0xFF stands for character value store else
where, and 0xFF means , left-half of the else where character, and 0xFE
means right-half of the else where character. 

 This is a basic solution, the best is that making vc-&amp;gt;vc_screenbuf
store full UNICODE/attribute value, But changin&lt;/pre&gt;</description>
    <dc:creator>Microcai</dc:creator>
    <dc:date>2010-11-26T10:02:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/76">
    <title>Is this mailing list dead?</title>
    <link>http://comments.gmane.org/gmane.linux.console/76</link>
    <description>&lt;pre&gt;Is anyone reading this mailing list?  I presume that since it's called
"linux-console" and hosted on kernel.org, that this is the right place to ask
for help with writing console drivers.  However, it doesn't appear that anyone
is actually reading this list, so I want to make sure I'm not wasting my time here.

I'm trying to write a console/TTY driver that is not a UART driver, and I can't
seem to find a good example of such a driver out there.  Specfically, my driver
has an interrupt handler that calls tty_insert_flip_string() when it receives
new input.  What I don't understand is how am I supposed to know what "struct
tty_struct" to use for this function.  It appears that it's possible to open the
TTY device multiple times, each time with a different struct tty_struct.  But I
can only have one interrupt handler, so I don't know how I'm supposed to
determine which of the many struct tty_struct pointers to use.

&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2010-10-27T20:38:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/75">
    <title>Warning: unable to open an initial console.</title>
    <link>http://comments.gmane.org/gmane.linux.console/75</link>
    <description>&lt;pre&gt;Hi,

I'm trying to write a console/tty driver, and I need help.  When the kernel
boots, I can see that console output is working through my driver.  However,
after the initial kernel boot, my console stops working.  Here are the relevant
parts of the boot log:

Using P4080DS HV machine description
Memory CAM mapping: 256/256 Mb, residual: 0Mb
Linux version 2.6.34-6506-00741-gbd4ea2b-dirty (b04825&amp;lt; at &amp;gt;efes) (gcc version 4.4.1
(Sourcery G++ Lite 4.4-194) ) #33 SMP Mon Oct 25 16:20:20 CDT 2010
Found initrd at 0xc1300000:0xc3b00000
...
Kernel command line: console=ttyEHV
...
console [ttyEHV0] enabled
...
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Warning: unable to open an initial console. -19
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
Freeing unused kernel memory: 236k init

And this is where it stops.

As you can &lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2010-10-25T21:30:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/74">
    <title>Question about 'device' field of struct console</title>
    <link>http://comments.gmane.org/gmane.linux.console/74</link>
    <description>&lt;pre&gt;I'm trying to write a console and TTY driver that's not based on a serial port,
and I'm confused by the "device' field of 'struct console'.  I found this text
in http://www.linux.it/~rubini/docs/sercons/sercons.html:

"The purpose of the UDP console device is sending kernel messages through the
network. Unlike serial or vt consoles, which are associated to real tty devices,
this console has no tty associated, and that's why the device function is not
defined.

In a real console device, the device function is used to return the device
number associated to this console as a kdev_t value. Only one serial port can be
elected as a console, for example, and the device function defined by the serial
driver is used to tell the caller which one is. The function is used in
drivers/char/tty_io.c to redirect any access to /dev/console. Thus, a process
that opens /dev/console will actually open a different device, provided at least
one of the active console drivers has a device function and the device returned
is known t&lt;/pre&gt;</description>
    <dc:creator>Timur Tabi</dc:creator>
    <dc:date>2010-10-25T18:23:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/73">
    <title>Ic vibrations, and to send out strong psychic cur</title>
    <link>http://comments.gmane.org/gmane.linux.console/73</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Jannise Nagura</dc:creator>
    <dc:date>2010-07-19T22:21:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/72">
    <title>rbs, or the</title>
    <link>http://comments.gmane.org/gmane.linux.console/72</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Veselka Mcrorie</dc:creator>
    <dc:date>2010-06-14T17:07:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/71">
    <title>hey are "well content." A</title>
    <link>http://comments.gmane.org/gmane.linux.console/71</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Battaglia Gladhill</dc:creator>
    <dc:date>2010-06-12T18:42:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.console/70">
    <title>T our forces were of an irregular and guer</title>
    <link>http://comments.gmane.org/gmane.linux.console/70</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Daughtery Bombaci</dc:creator>
    <dc:date>2010-05-18T18:29:24</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.console">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.console</link>
  </textinput>
</rdf:RDF>
