/Kconfig.debug
+++ b/arch/powerpc/Kconfig.debug
@@ -147,6 +147,13 @@ choice
enable debugging for the wrong type of machine your kernel
_will not boot_.
+config PPC_EARLY_DEBUG_BOOTX
+ bool "BootX or OpenFirmware"
+ depends on BOOTX_TEXT
+ help
+ Sele
Hi,
I have looked at the -S output for mesh.c from both 4.1.2 and 4.3.5.
The generated code is quite different but I can not see any difference
that is causing the problem?
If I read and print the bus status register 0, it does appear to have
the busy bit set?
I'm in way over my head here. It ap
On Fri, 2011-02-04 at 11:21 -0600, kevin diggs wrote:
>
> P.S.: I posted some documentation for dump_stack()/show_stack() but
> have not heard anything? Is that not something we are interested in
> doing?
Or I haven't had a chance to review it yet ... I'm very very busy at the
moment so things
Hi,
FYI:
This driver has some pretty good diagnostics/debug capabilities built
in. Once that is enabled it shows that the inquiry works and the sync
negotiation works. The next command (I think) is test unit ready,
which does not work. It is retried multiple times. The result is 2
which I thi
On Wed, 2011-02-02 at 16:09 -0600, kevin diggs wrote:
> Hi,
>
> And one more thing: Why does an SMP kernel (mesh compiled in an SMP
> enabled kernel) work?
Could be an alignment or timing problem, depending on random things the
alignment of some DMA data structures or timing of access might end
Hi,
And one more thing: Why does an SMP kernel (mesh compiled in an SMP
enabled kernel) work?
What all does SMP do? If it matters, I'm voluntary preempt.
Is the DMA hardware in this thing used in any other system (I guess I
mean both other computers and other sub-systems in this computer -
does
Ben,
I know you are VERY busy. I appreciate your taking the time to reply.
Since I'm am still using this thing I'll take a stab at trying to
track it down. I just posted the FYI to see if I could trigger some
thoughts (like your post).
With a 4.3.5 compiled mesh, it fails a lot of early stuff li
On Wed, 2011-02-02 at 13:36 -0600, kevin diggs wrote:
> Hi,
>
> FYI:
>
> I have narrowed this down to drivers/scsi/mesh.c (the root disk
> controller for the PowerMac 8600). I have compiled everything else for
> 2.6.36 with 4.3.5, including modules. With a 4.1.2 compiled mesh.c the
> beast boots.
Hi,
FYI:
I have narrowed this down to drivers/scsi/mesh.c (the root disk
controller for the PowerMac 8600). I have compiled everything else for
2.6.36 with 4.3.5, including modules. With a 4.1.2 compiled mesh.c the
beast boots. I am using it to post this follow up.
kevin
> On Sat, Jan 22, 2011
cpufreq driver gets disabled. It is fairly isolated
> code though. Should not be able to nuke the spinlock in kernel/acct.c
>
> On Fri, Jan 21, 2011 at 1:26 PM, kevin diggs wrote:
>> Hi,
>>
>> Anyone familiar with BootX? Could my problems with the 8600 be related
>
gt; Thanks!
>
> kevin
>
> P.S.: There is one other difference for the SMP 4.3.5 compiled
> 2.6.28: my 750gx cpufreq driver gets disabled. It is fairly isolated
> code though. Should not be able to nuke the spinlock in kernel/acct.c
>
> On Fri, Jan 21, 2011 at 1:26 PM, k
oes.
Thanks!
kevin
P.S.: There is one other difference for the SMP 4.3.5 compiled
2.6.28: my 750gx cpufreq driver gets disabled. It is fairly isolated
code though. Should not be able to nuke the spinlock in kernel/acct.c
On Fri, Jan 21, 2011 at 1:26 PM, kevin diggs wrote:
> Hi,
>
> Anyo
hat's in
distros like debian or genpoo..
Cheers,
Ben.
> kevin
>
> On Fri, Jan 21, 2011 at 7:50 PM, Benjamin Herrenschmidt
> wrote:
> > On Fri, 2011-01-21 at 19:48 -0600, kevin diggs wrote:
> >> Hi,
> >>
> >> This would require quik, right? I wen
gt;>
>> This would require quik, right? I went to penguinppc.org and tried to
>> get the latest BootX and quik but the links are dead. Do you know
>> where the latest versions are?
>
> That link still works:
>
> Oops... typing FAIL :-)
>
> I meant:
>
>
On Fri, 2011-01-21 at 19:48 -0600, kevin diggs wrote:
> Hi,
>
> This would require quik, right? I went to penguinppc.org and tried to
> get the latest BootX and quik but the links are dead. Do you know
> where the latest versions are?
That link still works:
Oops... typing FA
On Fri, 2011-01-21 at 19:48 -0600, kevin diggs wrote:
> Hi,
>
> This would require quik, right? I went to penguinppc.org and tried to
> get the latest BootX and quik but the links are dead. Do you know
> where the latest versions are?
That link still works:
> kevin
>
>
Hi,
This would require quik, right? I went to penguinppc.org and tried to
get the latest BootX and quik but the links are dead. Do you know
where the latest versions are?
kevin
On Fri, Jan 21, 2011 at 3:21 PM, Benjamin Herrenschmidt
wrote:
> On Fri, 2011-01-21 at 13:26 -0600, kevin diggs wr
On Fri, 2011-01-21 at 13:26 -0600, kevin diggs wrote:
> Hi,
>
> Anyone familiar with BootX? Could my problems with the 8600 be related
> to some interaction with BootX?
It's possible. Have you tried using OF booting instead ? The 8600 should
be cable to boot off SCSI or ne
Hi,
Anyone familiar with BootX? Could my problems with the 8600 be related
to some interaction with BootX?
kevin
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On Wed, 2008-08-20 at 18:25 +1000, Finn Thain wrote:
>
> On Wed, 20 Aug 2008, Benjamin Herrenschmidt wrote:
>
> > On Wed, 2008-08-20 at 03:23 +1000, Finn Thain wrote:
> > >...
> > >
> > > The Debian Sarge 2.6.8-4 kernel does not seem to have this problem
> > > though kernel.org 2.6.16 and later
On Wed, 20 Aug 2008, Benjamin Herrenschmidt wrote:
> On Wed, 2008-08-20 at 03:23 +1000, Finn Thain wrote:
> >...
> >
> > The Debian Sarge 2.6.8-4 kernel does not seem to have this problem
> > though kernel.org 2.6.16 and later versions do.
> >
> > Any ideas?
>
> How "late" have you tried ? I
On Wed, 2008-08-20 at 03:23 +1000, Finn Thain wrote:
> Hi All,
>
> When I build kernels with CONFIG_BOOTX_TEXT enabled I can't boot a PB 3400
> with BootX. I get a black screen with "Welcome to Linux" at the top, then
> it appears to hang. Debian kernels are conf
Hi All,
When I build kernels with CONFIG_BOOTX_TEXT enabled I can't boot a PB 3400
with BootX. I get a black screen with "Welcome to Linux" at the top, then
it appears to hang. Debian kernels are configured this way and suffer the
same problem.
I don't know if Quik is a
BootX text code is only supported on systems with real OF at this point
which is PPC_OF && PPC_MULTIPLATFORM.
Signed-off-by: Kumar Gala <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig.debug |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/Kconfi
24 matches
Mail list logo
