From: Frederic TEMPORELLI <frederic.temporelli@laposte.net>
To: linux-mips@linux-mips.org
Subject: SGI IP32 and 2.6.11
Date: Sun, 06 Mar 2005 18:23:00 +0100 [thread overview]
Message-ID: <422B3C74.9090706@laposte.net> (raw)
Hello,
I've just been able to start 2.6.11 from my own compilation on IP32.
Can I have some help about following problems/comments ?
1/ It was really difficult because kernel was falling in breakpoint call
(BUG macro) in free_bootmem_core.
=> I've successfully try to comment this BUG macro in free_bootmem_core
(bootmem.c)
Of course, I'm thinking this is really sad... but I've a really poor
knowledge in kernel development...
may someone can explain how to solve such issue in a better way ?
This breakpoint was boring me since 2.6.10...
2/ There's also a problem with ip32-memory.c, which isn't able to detect
64MB dimm.
Yet, not enough knowledge for processing bankctl (prom_meminit) in the
nice way for detecting 64MB dimms...
(All memory slots are used on my O2: slots 1 to 6 with 32MB dimms and
slots 7 & 8 with 64MB dimms) .
Best regards
Frederic TEMPORELLI
next reply other threads:[~2005-03-06 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 17:23 Frederic TEMPORELLI [this message]
2005-03-06 19:13 ` SGI IP32 and 2.6.11 Ilya A. Volynets-Evenbakh
2005-03-06 20:01 ` Frederic TEMPORELLI - astek
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=422B3C74.9090706@laposte.net \
--to=frederic.temporelli@laposte.net \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox