public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Joey Oravec <joravec@drewtech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How console redirection is done
Date: Fri, 13 Jul 2007 08:14:40 -0400	[thread overview]
Message-ID: <f77qbl$223$1@sea.gmane.org> (raw)
In-Reply-To: 65487840707122317ve675e94x222e48968a8a730b@mail.gmail.com

"Ori Idan" <ori@helicontech.co.il> wrote in message 
news:65487840707122317ve675e94x222e48968a8a730b at mail.gmail.com...
>I am sorry, I can not understand the question.
> U-boot always outputs to serial port.
> If you would like to change to another serial port look at the
> configuration file corresponding to your board under include/configs.

That's not exactly true. After the initial console (bootup) you can use more 
than serial.

There are a few functions like drv_lcd_init in lcd.c that create a device_t 
structure -- in my version they're all called within devices_init in 
common/devices.c during boot. This defines a putc, puts, getc, and tstc to 
handle I/O character by character. Once you call device_register() it will 
available to the system. Using the environment variables stdin, stdout, and 
stderr you can choose which device is active, and console.c calls the 
appropriate function pointer. Set the variable and you can be printing on 
the LCD instead.

Of course all this can be changed with a million CONFIG_ parameters, and it 
is a little strange if you have several consoles available and no default.

-joey 

  parent reply	other threads:[~2007-07-13 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13  4:56 [U-Boot-Users] How console redirection is done yasosyaso
2007-07-13  6:17 ` Ori Idan
2007-07-13 10:47   ` yasosyaso
2007-07-13 12:14   ` Joey Oravec [this message]
2007-07-16  6:03     ` yasosyaso
2007-07-16  6:05       ` yasosyaso
  -- strict thread matches above, loose matches on Subject: below --
2007-07-13  4:57 yasothabalanr at gmail.com

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='f77qbl$223$1@sea.gmane.org' \
    --to=joravec@drewtech.com \
    --cc=u-boot@lists.denx.de \
    /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