public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] serial: Make nulldev a serial device
Date: Tue, 6 Nov 2012 01:47:33 +0100	[thread overview]
Message-ID: <201211060147.33342.marex@denx.de> (raw)
In-Reply-To: <CANr=Z=aXcM4ZXzeetS0014xSjqQ_s+1t0rvX+Qgbs3wJxSbjvQ@mail.gmail.com>

Dear Joe Hershberger,

> Hi Marek.
> 
> On Mon, Nov 5, 2012 at 5:10 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Joe Hershberger,
> > 
> >> Hi Marek,
> >> 
> >> On Fri, Nov 2, 2012 at 8:37 PM, Marek Vasut <marex@denx.de> wrote:
> >> > Dear Joe Hershberger,
> >> > 
> >> >> This allows the default console to be specified as the nulldev.  This
> >> >> is specifically helpful when the real serial console's init() cannot
> >> >> run early in the boot process.  When the init can be run, then the
> >> >> console can be switched to the real device using the std* env vars.
> >> >> 
> >> >> Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
> >> > 
> >> > Isn't it actually better to have null stdio device? Some systems might
> >> > not even use serial port (and so null serial will be useless on these
> >> > systems)!
> >> 
> >> As I described in my commit log, this is for the case where the serial
> >> and console init must not touch the hardware, (since it doesn't exist
> >> yet if it's in an FPGA or on a PCI or USB connection).  Making the
> >> default serial port be the nulldev avoids this issue.
> > 
> > So add nulldev serial device for this stupid case. Even though fixing
> > iomux such that it'd not send anything to serial port at all if nulldev
> > is selected would be even better idea.
> 
> It's not a problem of something being sent to the serial port.  It's
> the call to serial_init() in arch/*/lib/board.c that kills it.  That
> call needs to be no-op-able.

Why?

What about fixing serial_init like this:

struct serial_device *dev = get_current();
int ret = 0;
if (dev)
  ret = dev->start();

return ret;

Best regards,
Marek Vasut

  reply	other threads:[~2012-11-06  0:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 21:46 [U-Boot] [PATCH 1/2] serial: Remove the "serial" console device Joe Hershberger
2012-11-01 21:46 ` [U-Boot] [PATCH 2/2] serial: Make nulldev a serial device Joe Hershberger
2012-11-03  1:37   ` Marek Vasut
2012-11-05  0:24     ` Joe Hershberger
2012-11-05 23:10       ` Marek Vasut
2012-11-06  0:01         ` Joe Hershberger
2012-11-06  0:47           ` Marek Vasut [this message]
2012-11-06  1:00             ` Joe Hershberger
2012-11-06  1:11               ` Marek Vasut
2012-11-03  1:35 ` [U-Boot] [PATCH 1/2] serial: Remove the "serial" console device Marek Vasut
2012-11-05  0:20   ` Joe Hershberger
2012-11-05 23:11     ` Marek Vasut
2012-11-05 23:45       ` Joe Hershberger
2012-11-05 23:55         ` Marek Vasut

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=201211060147.33342.marex@denx.de \
    --to=marex@denx.de \
    --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