From mboxrd@z Thu Jan 1 00:00:00 1970 From: vvj Date: Tue, 24 Apr 2007 03:33:14 -0700 (PDT) Subject: [U-Boot-Users] UBoot's terminal server In-Reply-To: <20070423190504.6DA55353A40@atlas.denx.de> References: <10141414.post@talk.nabble.com> <1177339341.3904.48.camel@saruman.qstreams.net> <10146755.post@talk.nabble.com> <20070423190504.6DA55353A40@atlas.denx.de> Message-ID: <10158334.post@talk.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Wolfgang, I searched through latest (Uboot 1.2) doc folder, but did not find kind of text you mentioned: "...some distributives (Fedora Core 5 at least)..." Also I recompiled Uboot to support NetConsole: I defined CONFIG_NETCONSOLE CFG_CMD_NET (in CONFIG_COMMANDS, wo it I had compiling errors) CONFIG_NET_MULTI (wo it I had compiling errors) The problem is that when I define CONFIG_NET_MULTI, Uboot does not initialize network at startup - I cant use tftp or any network related. When I "run nc" - serial COM port shell dies, but do not see anything on host (I tried SuSe now) What are the criteria which defines whether board is capable of netconsole or not? What means CONFIG_NET_MULTI and why network stuff - eth_init(bd_t) - does not launch when it is defined? I have UBoot 1.1.2 from STlinux.com and 7100mboard Best regards, Viktor Volke -- View this message in context: http://www.nabble.com/UBoot%27s-terminal-server-tf3632025.html#a10158334 Sent from the Uboot - Users mailing list archive at Nabble.com.