kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is a console? and Why it is always associated with UART?
Date: Mon, 9 Jan 2012 22:59:54 -0800	[thread overview]
Message-ID: <CABi1daFhr5Ay9hNQp4Q6Sf=6nyKOAPnANPYckx0EhGwoeO_Atg@mail.gmail.com> (raw)
In-Reply-To: <CAL7WMDdRon_8SQ0phwhrgAV5TiB+mvyPEduE7Qzoz+o+EF8vMA@mail.gmail.com>

Hi sandeep,

On Mon, Jan 9, 2012 at 10:37 PM, sandeep kumar
<coolsandyforyou@gmail.com> wrote:
> Hi All,
>
> I want to know "What is a console?

A console is where the output from printk goes.

> and Why it is always associated with
> UART?"

While console's may often be associated with a UART (typical for
embedded systems) there is no need or requirement for them to be
associated with a console. You can regitser a console to send the
output wherever you like.

> What is a serial console??

A serial console is a console driver (registered via register_console)
which sends the output to a serial port, typically also allowing the
serial port to be used as a tty interface.

> Can there be a USB console??

Sure. I don't know if a driver for this exists yet, but if it doesn't
you can always write one.

There is already something called a netconsole (see
Documentation/networking/netconsole.txt). This is an example of a
console which isn't associated with a serial port.

There is also a framebuffer console (See Documentation/fb/fbcon.txt)

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com

  reply	other threads:[~2012-01-10  6:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  6:37 What is a console? and Why it is always associated with UART? sandeep kumar
2012-01-10  6:59 ` Dave Hylands [this message]
2012-01-25  5:31   ` Peter Teoh

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='CABi1daFhr5Ay9hNQp4Q6Sf=6nyKOAPnANPYckx0EhGwoeO_Atg@mail.gmail.com' \
    --to=dhylands@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).