On 01/07/2012 03:25 AM, Florian Fainelli wrote:
Le samedi 07 janvier 2012 00:32:31, Peter Naulls a écrit :
On 01/06/2012 08:10 AM, Peter Naulls wrote:
As an alternative, I'm looking at first jumping to an ar71xx version
of u-boot (as per OpenWrt build), all I should need to add to that
is flash
Le vendredi 06 janvier 2012 20:17:44, Peter Naulls a écrit :
> On 01/06/2012 02:48 AM, Florian Fainelli wrote:
> > Then this might be an entirely different issue. Try to run the kexec'd
> > kernel uncached and see if that helps (there is a MIPS-specific Kconfig
> > option to do that).
>
> CONFIG_M
Le samedi 07 janvier 2012 00:32:31, Peter Naulls a écrit :
> On 01/06/2012 08:10 AM, Peter Naulls wrote:
> > As an alternative, I'm looking at first jumping to an ar71xx version
> > of u-boot (as per OpenWrt build), all I should need to add to that
> > is flash support for the G300NH(2). Perhaps th
On 01/06/2012 08:10 AM, Peter Naulls wrote:
As an alternative, I'm looking at first jumping to an ar71xx version
of u-boot (as per OpenWrt build), all I should need to add to that
is flash support for the G300NH(2). Perhaps that puts the system
in more consistent state before starting Linux.
I
On 01/06/2012 02:48 AM, Florian Fainelli wrote:
Then this might be an entirely different issue. Try to run the kexec'd kernel
uncached and see if that helps (there is a MIPS-specific Kconfig option to do
that).
CONFIG_MIPS_L1_CACHE_SHIFT=5 ? There's other related stuff in
arch/mips/Kconfig b
On 01/06/2012 07:06 AM, Paolo Pisati wrote:
On 01/06/2012 11:48 AM, Florian Fainelli wrote:
Then this might be an entirely different issue. Try to run the kexec'd
kernel uncached and see if that helps (there is a MIPS-specific Kconfig
option to do that).
but is kexec working at all on MIPS cp
On 01/06/2012 11:48 AM, Florian Fainelli wrote:
>
> Then this might be an entirely different issue. Try to run the kexec'd
> kernel uncached and see if that helps (there is a MIPS-specific Kconfig
> option to do that).
but is kexec working at all on MIPS cpus? on arm, at least, it was badly
broke
On 01/05/12 23:19, Peter Naulls wrote:
On 01/05/2012 09:43 AM, Florian Fainelli wrote:
Hello,
You should enable kernel debugging in your kexec'd kernel and see
whether the
serial port is being left with IRQs disabled from the original kernel.
I turned on kernel debug, but I'm unsure what e
On 01/05/2012 09:43 AM, Florian Fainelli wrote:
Hello,
You should enable kernel debugging in your kexec'd kernel and see whether the
serial port is being left with IRQs disabled from the original kernel.
I turned on kernel debug, but I'm unsure what exactly I'm looking at.
It may be that th
Hello,
On 01/05/12 18:36, Peter Naulls wrote:
I'm trying to use kexec as a fallback/flash mechanism. But something is
going wrong:
http://pastebin.com/0uvNnMQd
So the device halts after/during the serial port setup, and returns to boot
loader. Anyone want to suggest what might be going wrong,
I'm trying to use kexec as a fallback/flash mechanism. But something is going
wrong:
http://pastebin.com/0uvNnMQd
So the device halts after/during the serial port setup, and returns to boot
loader. Anyone want to suggest what might be going wrong, or where to
start looking?
11 matches
Mail list logo
