From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: Manish Lachwani <mlachwani@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Custom kernel crashes
Date: Tue, 02 Nov 2004 18:07:29 +0100 [thread overview]
Message-ID: <4187BED1.2060208@enix.org> (raw)
In-Reply-To: <4187BB44.4030508@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hello,
Manish Lachwani a écrit :
> This may or may not apply to your case. Is this board still the one that
> has the Marvell Discovery ethernet device? If yes, Marvell Discovery has
> its SRAM located at 0xfe000000. So, make a check in the ethernet driver
> or other board specific sources and see if there is any access to this
> SRAM location.
The DMA buffers and DMA buffer descriptors used for the serial driver
are all located in the SRAM of the Marvell, which is mapped using a
wired uncached TLB entry.
Here's the code that wires the entry :
add_wired_entry(ENTRYLO(NPP_BOARD_INTERNAL_SRAM_BASE),
ENTRYLO(NPP_BOARD_INTERNAL_SRAM_END),
NPP_BOARD_INTERNAL_SRAM_BASE,
PM_256K);
I would like to use ioremap() instead of wired TLB entries, but for the
moment, I'm focusing on this crash.
Thanks,
Thomas
--
PETAZZONI Thomas - thomas.petazzoni@enix.org
http://thomas.enix.org - Jabber: kos_tom@sourcecode.de
KOS: http://kos.enix.org/ - Lolut: http://lolut.utbm.info
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2004-11-02 17:05 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 [this message]
2004-11-02 17:12 ` Manish Lachwani
2004-11-02 17:22 ` Thomas Petazzoni
2004-11-02 17:36 ` Manish Lachwani
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=4187BED1.2060208@enix.org \
--to=thomas.petazzoni@enix.org \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox