public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel•crashing.org>
To: Niklaus Giger <niklaus.giger@member•fsf.org>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Problems porting to a custom PPC405GPr board using a vanilla 2.6.10 kernel
Date: Sun, 27 Feb 2005 09:08:51 -0700	[thread overview]
Message-ID: <20050227090851.B11020@cox.net> (raw)
In-Reply-To: <200502271610.30615.niklaus.giger@member.fsf.org>; from niklaus.giger@member.fsf.org on Sun, Feb 27, 2005 at 04:10:30PM +0100

On Sun, Feb 27, 2005 at 04:10:30PM +0100, Niklaus Giger wrote:
> Am Samstag, 26. Februar 2005 23.28 schrieb Niklaus Giger:
> > Hi
> >
> > I would like to port Linux to a custom PPC405GPr board. Its hardware runs
> > vxWorks fine for more than a year.
> >
> I made some more progress. After adding 3 lines for MMU support with the BDI
> I can debug the startup up to kernel_start using BDI. 
> 
> Afterwards my console changes the baudrate for still unknown reasons.

How do you know this? Console isn't initialized until after the kernel 
command line printk and a few other facilities are initialized.

> Analysing the __log_buf I get the following output
> (gdb) x/s &__log_buf
> 0xc01accfc <ratelimit_lock.9>:   "<4>Linux version 2.6.10 
> (niklaus@ng•ngiger.dyndns.org) (gcc-Version 3.3.5 (Debian 1:3.3.5-8)) #15 Sun 
> Feb 27 14:44:27 CET 2005\n<7>On node 0 totalpages: 8240\n<7>  DMA zone: 8240 
> pages, LIFO batch:2\n<7>"...
> (gdb) x
> 0xc01acdc4 <ratelimit_lock.9+200>:       "  Normal zone: 0 pages, LIFO 
> batch:1\n<7>  HighMem zone: 0 pages, LIFO batch:1\n<4>Built 1 
> zonelists\n<4>Kernel command line: ip=172.25.1.6\n<4>PID hash table entries: 
> 256 (order:8, 4096 bytes)\n"
> (gdb) x
> 0xc01ace84 <ratelimit_lock.9+392>:       ""

Is this all of the log_buf output? Try setting your kernel cmdline
with "console=ttyS0,115200" where 115200 is you console baudrate
you are using in U-Boot. Otherwise, the kernel 8250 driver has no
idea which baudrate to set for the 8250/console.

-Matt 

  reply	other threads:[~2005-02-27 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 22:28 Problems porting to a custom PPC405GPr board using a vanilla 2.6.10 kernel Niklaus Giger
2005-02-27 15:10 ` Niklaus Giger
2005-02-27 16:08   ` Matt Porter [this message]
2005-02-27 17:20     ` Niklaus Giger
2005-04-17 20:13       ` Niklaus Giger
2005-02-27 15:59 ` 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=20050227090851.B11020@cox.net \
    --to=mporter@kernel$(echo .)crashing.org \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=niklaus.giger@member$(echo .)fsf.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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