All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manish Lachwani <mlachwani@mvista.com>
To: Thomas Petazzoni <thomas.petazzoni@enix.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Custom kernel crashes
Date: Tue, 02 Nov 2004 09:36:04 -0800	[thread overview]
Message-ID: <4187C584.4060000@mvista.com> (raw)
In-Reply-To: <4187C26E.1090402@enix.org>

Hello Thomas,

Quick suggestion since I dont know all the details: Can you increase the 
  size of the space mapped to say 16 MB (some larget value than 256 KB) 
and check if the bus error repeats?

#define NPP_BOARD_INTERNAL_SRAM_SIZE (16 *1024 * 1024)

Thanks
Manish Lachwani



Thomas Petazzoni wrote:
> Hello,
> 
> Manish Lachwani a écrit :
> 
>> What are these values: NPP_BOARD_INTERNAL_SRAM_BASE, 
>> NPP_BOARD_INTERNAL_SRAM_END and NPP_BOARD_INTERNAL_SRAM_BASE.
> 
> 
> #define NPP_BOARD_INTERNAL_SRAM_BASE 0xfe000000UL
> #define NPP_BOARD_INTERNAL_SRAM_SIZE (256*1024)
> #define NPP_BOARD_INTERNAL_SRAM_END  \
>         (NPP_BOARD_INTERNAL_SRAM_BASE + NPP_BOARD_INTERNAL_SRAM_SIZE)
> 
> Do you think it's a problem related to the SRAM ?
> 
>> Also, what is ENTRYLO() defined as?
> 
> 
> static inline unsigned long ENTRYLO(unsigned long paddr)
> {
>         return ((paddr & PAGE_MASK) |
>                (_PAGE_PRESENT | __READABLE | __WRITEABLE | _PAGE_GLOBAL |
>                 _CACHE_UNCACHED)) >> 6;
> }
> 
> This code is taken from the jaguar_atx setup.c file.
> 
> Thanks,
> 
> Thomas

      reply	other threads:[~2004-11-02 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 16:00 Custom kernel crashes Thomas Petazzoni
2004-11-02 16:52 ` Manish Lachwani
2004-11-02 17:07   ` Thomas Petazzoni
2004-11-02 17:12     ` Manish Lachwani
2004-11-02 17:22       ` Thomas Petazzoni
2004-11-02 17:36         ` Manish Lachwani [this message]

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=4187C584.4060000@mvista.com \
    --to=mlachwani@mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas.petazzoni@enix.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.