public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Gary Jennejohn <garyj@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 V2] IOMUX: Add console multiplexing support.
Date: Tue, 21 Oct 2008 13:32:54 +0200	[thread overview]
Message-ID: <20081021133254.2674b1eb@ernst.jennejohn.org> (raw)
In-Reply-To: <20081021103430.8ADE3835694E@gemini.denx.de>

On Tue, 21 Oct 2008 12:34:30 +0200
Wolfgang Denk <wd@denx.de> wrote:

> In message <20081021114543.1c44ff03@ernst.jennejohn.org> you wrote:
> >
> > By the time the problem arises we're already running out of RAM.
> 
> So maybe you can describe exactly what happens, and when?
> 
> > I think the real problem is that console_init_r() is called too
> > early.  If it were called *after* eth_initialize() then there would
> > be no difficulties.
> > 
> > AFAICT moving console_init_r() shouldn't present any problems, since
> > until its invocation U-Boot will simply use the serial interface.
> 
> I am not so sure. Moving things around not as trivial as it may seem,
> as we have all kinds of configurations with LCD display, modem support
> etc.
> 

All console_init_r() does is to search for devices which can be used
for STDIN/STDOUT/STDERR (whether in the environment or the device list),
call console_setfile() and then print out the list of devices found.
console_setfile() actually calls the device start routines.  The actual
registration of the devices happens in device_init() which is called
before console_init_r().

So I see no reason why moving console_init_r() would have any effect.

> > It isn't clear to me whether the architecture-specific libs have custodians.
> > Does anyone know?
> 
> What is not clear about that? Do we have custodians for  architecture
> specific  files?  Yes, we do. So whay do you doubt that the libs fall
> into their responsibility, too?
> 

Did I write that I doubt anything?  No.  I just asked for some
clarification because it wasn't clear to me from the very abbreviated
descriptions on the Custodian page just exactly what is within the
purview of a custodian.

---
Gary Jennejohn
*********************************************************************
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
*********************************************************************

  reply	other threads:[~2008-10-21 11:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 14:45 [U-Boot] [PATCH 2/2] IOMUX: Add console multiplexing support Gary Jennejohn
2008-09-14 16:07 ` Wolfgang Denk
2008-09-14 17:19   ` Gary Jennejohn
2008-09-14 18:34     ` Wolfgang Denk
2008-09-15  8:46       ` Gary Jennejohn
2008-09-15 11:08         ` Wolfgang Denk
2008-10-20 11:58 ` [U-Boot] [PATCH 2/2 V2] " Gary Jennejohn
2008-10-20 13:24   ` Wolfgang Denk
2008-10-20 13:57     ` Gary Jennejohn
2008-10-20 16:26       ` Gary Jennejohn
2008-10-20 19:43         ` Wolfgang Denk
2008-10-20 20:13           ` Ben Warren
2008-10-21  9:45             ` Gary Jennejohn
2008-10-21 10:34               ` Wolfgang Denk
2008-10-21 11:32                 ` Gary Jennejohn [this message]
2008-10-20 19:32       ` Wolfgang Denk

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=20081021133254.2674b1eb@ernst.jennejohn.org \
    --to=garyj@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