All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Siemsen <rsiemsen@rossvideo.com>
To: Daren Hayward <darenh@4bridgeworks.com>
Cc: "'Matt Porter'" <mporter@kernel.crashing.org>,
	Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: early UART mapping in head_44x.S
Date: Tue, 03 Aug 2004 13:58:20 -0400	[thread overview]
Message-ID: <410FD23C.2070506@rossvideo.com> (raw)
In-Reply-To: <C18BA5DDB58DD511BD0700C0DF0DD45011C475@NTSERVER4>


Daren Hayward wrote:
 > Hi,
 >
 > I have been having the same problems with the head_44x.S, what does
 > the patch do just remove the duplicate entries?
 >
 > Where can I browse the PPC BK tree online?

Hi Daren

I'm using mainline sources (eg. tarball from kernel.org)... its a
one-line fix for the TLB setup.. the second one should use slot 2
not slot 1 (which is already setup).  Note this only affects you if you
build with CONFIG_EARLY_SERIAL_DEBUG.

I just found your post to the u-boot mailing list from 2004-07-02 where
you mention networking problems unless you use u-boot to touch the
network somehow before the kernel boots.

I am seeing very much similar behaviour, with 2.6.7 kernel and using
PIBS bootloader.

Looks very much like the kernel is missing some initialization that is
required.  Did you make any progress tracking down the cause?

-Ralph

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-08-03 17:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 12:30 early UART mapping in head_44x.S Daren Hayward
2004-08-02 13:57 ` Matt Porter
2004-08-03 17:58 ` Ralph Siemsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-13 21:23 Ralph Siemsen
2004-07-13 21:51 ` Ralph Siemsen
2004-07-13 22:28 ` James Perkins
2004-07-13 22:48   ` Ralph Siemsen
2004-07-22 23:55 ` Matt Porter

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=410FD23C.2070506@rossvideo.com \
    --to=rsiemsen@rossvideo.com \
    --cc=darenh@4bridgeworks.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mporter@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.