public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Bastos Fernandez Alexandre <ALEBAS@televes•com>
To: "'Walter L. Wimer III'" <walt.wimer@timesys•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: RE: Problem running Linux 2.6.11 on MPC8272ADS
Date: Tue, 29 Mar 2005 08:29:50 +0200	[thread overview]
Message-ID: <51DB8827D393D411BB69003048003F4601B1C1CE@tvesntr> (raw)

Hi, 

>From "linux/arch/ppc/platforms/pq2ads.h"
#define BCSR_ADDR ((uint) 0xf4500000)
>From "u-boot/include/configs/MPC8260ADS.h"
#define CFG_BCSR 0xF4500000
So ...
Which version of u-boot and/or linux tree are you using?
With linuxppc-2.5 and u-boot 1.2 everything works fine for me.
Maybe Mike's problem is other. Maybe not. :-)

Best regards,
Alex

> -----Original Message-----
> From:	Walter L. Wimer III [SMTP:walt.wimer@timesys•com]
> Sent:	Monday, March 28, 2005 6:07 PM
> To:	Mike Rapoport
> Cc:	linuxppc-embedded@ozlabs•org
> Subject:	Re: Problem running Linux 2.6.11 on MPC8272ADS
> 
> 
> Hi Mike,
> 
> I had the same "hang" experience.  The file arch/ppc/platforms/pq2ads.c
> contains the following function:
> 
>   void __init
>   m82xx_board_setup(void)
>   {
>   	/* Enable the 2nd UART port */
>   	*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_RS232_EN2;
>   }
> 
> 
> I had to ifdef-out the assignment statement above.  It appears that the
> definition for BCSR_ADDR in the kernel code differs from what U-Boot is
> using, and that area of memory isn't properly mapped into the kernel
> address space this early in the boot sequence.  As a result, I was
> getting an Oops() before the console was even enabled (I could see the
> Oops message by examining the kernel's printk log buffer using a
> BDI-2000 hardware debugger).
> 
> 
> 
> Good luck,
> 
> Walt Wimer
> TimeSys Corporation
> 
> 
> 
> 
> On Sun, 2005-03-27 at 11:31 +0200, Mike Rapoport wrote:
> > Hi,
> > I'm trying to bring up the Linux 2.6.11 on MPC8272ADS and it seem to 
> > hang up at the very beginning.
> > I use ads8272_defconfig and then enable console on SCC:
> > 
> > CONFIG_SERIAL_CPM=y
> > CONFIG_SERIAL_CPM_CONSOLE=y
> > CONFIG_SERIAL_CPM_SCC1=y
> > 
> > 
> > when I boot the kernel from the u-boot the system hangs up right after 
> > the kernel decompression.
> > 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

             reply	other threads:[~2005-03-29  6:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  6:29 Bastos Fernandez Alexandre [this message]
2005-03-29 15:44 ` Problem running Linux 2.6.11 on MPC8272ADS Walter L. Wimer III
     [not found]   ` <424A60E1.4080802@compulab.co.il>
2005-03-30 16:00     ` Walter L. Wimer III
2005-03-30 17:42       ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31  8:22 Li Yang-r58472
2005-03-31 11:17 ` Eugene Surovegin
2005-03-31 15:36 ` Jon Loeliger
2005-03-31  3:03 Li Yang-r58472
2005-03-31  3:26 ` Eugene Surovegin
2005-03-27  9:31 Mike Rapoport
2005-03-28 16:06 ` Walter L. Wimer III
2005-03-28 16:21   ` Kumar Gala
2005-03-28 16:24     ` Walter L. Wimer III

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=51DB8827D393D411BB69003048003F4601B1C1CE@tvesntr \
    --to=alebas@televes$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=walt.wimer@timesys$(echo .)com \
    /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