From: nils.faerber@kernelconcepts.de (Nils Faerber)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood, kernel 3.2, vmalloc region overlap, not starting up
Date: Tue, 07 Feb 2012 17:10:52 +0100 [thread overview]
Message-ID: <4F314D0C.50501@kernelconcepts.de> (raw)
In-Reply-To: <20120207152903.GA16238@lunn.ch>
Am 07.02.2012 16:29, schrieb Andrew Lunn:
> Hi Nils
Hey Andrew!
> There was a thread a while back about CONFIG_ARM_PATCH_PHYS_VIRT
> causing problem with some kirkwood boards. Maybe try disabling this
> and set CONFIG_PHYS_OFFSET=0x0.
>
> However, it could be a different problem...
Nope, nothing elese, it worked exactly as you described it!
(Though it took me some minutes to find the options in menuconfig).
Here it is happily up again:
root at tk71:~# uname -a
Linux tk71 3.2.0-00012-g980d683-dirty #31 Tue Feb 7 17:04:50 CET 2012
armv5tel GNU/Linux
Thanks a million!
Should we ever meet in person - I now officially owe you a beer (or
other drink at your choice :)
Apart from my joy - the basic reason for that change would be still
interesting? Does this only apply to Kirwoods or my special board?
> Andrew
Thanks again!
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
next prev parent reply other threads:[~2012-02-07 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 15:29 Kirkwood, kernel 3.2, vmalloc region overlap, not starting up Andrew Lunn
2012-02-07 16:10 ` Nils Faerber [this message]
2012-02-07 16:14 ` Russell King - ARM Linux
2012-02-07 16:18 ` Andrew Lunn
2012-02-07 16:51 ` Russell King - ARM Linux
2012-02-07 17:01 ` Nils Faerber
2012-02-07 16:55 ` Johannes Stezenbach
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 14:41 Nils Faerber
2012-02-13 16:17 ` Russell King - ARM Linux
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=4F314D0C.50501@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-arm-kernel@lists.infradead.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.