2.6.17 on Broadcom BigSur (BCM91x80 A/B)

2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Anyone running 2.6.17 on the above Broadcom board or derivative?

I'm trying to run it an our hardware that is based on this
board. It's slightly patched so that it builds :), and so
that certain things work right on our board.

Kernel 2.6.14 works, and the patches migrated to 2.6.17
without too many difficulties.

It hangs on startup around the point where dynamic IP
configuration is done.

Sometimes the last output that is seen is the printk message

  Sending DHCP and RARP requests .

Sometimes it doesn't appear.

So before I dive into it head first, I thought I'd
poke the mailing list.

2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Anyone running 2.6.17 on the above Broadcom board or derivative?

I'm trying to run it an our hardware that is based on this
board. It's slightly patched so that it builds :), and so
that certain things work right on our board.

Kernel 2.6.14 works, and the patches migrated to 2.6.17
without too many difficulties.

It hangs on startup around the point where dynamic IP
configuration is done.

Sometimes the last output that is seen is the printk message

  Sending DHCP and RARP requests .

Sometimes it doesn't appear.

So before I dive into it head first, I thought I'd
poke the mailing list.

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Manoj Ekbote]

Hi Kaz,

Kindly make sure that the below 2 patches have been applied.
 
http://www.linux-mips.org/archives/linux-mips/2006-07/msg00021.html
http://www.linux-mips.org/archives/linux-mips/2006-07/msg00020.html

HTH,
/manoj

>-----Original Message-----
>From: linux-mips-bounce@linux-mips.org 
>[mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Kaz Kylheku
>Sent: Thursday, August 10, 2006 5:49 PM
>To: linux-mips@linux-mips.org
>Subject: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)
>
>Anyone running 2.6.17 on the above Broadcom board or derivative?
>
>I'm trying to run it an our hardware that is based on this 
>board. It's slightly patched so that it builds :), and so that 
>certain things work right on our board.
>
>Kernel 2.6.14 works, and the patches migrated to 2.6.17 
>without too many difficulties.
>
>It hangs on startup around the point where dynamic IP 
>configuration is done.
>
>Sometimes the last output that is seen is the printk message
>
>  Sending DHCP and RARP requests .
>
>Sometimes it doesn't appear.
>
>So before I dive into it head first, I thought I'd poke the 
>mailing list.
>
>
>

Re: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Ralf Baechle]

On Thu, Aug 10, 2006 at 07:24:02PM -0700, Manoj Ekbote wrote:

> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00021.html
> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00020.html

Both were applied quite a while ago.

  Ralf

Re: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Ralf Baechle]

On Thu, Aug 10, 2006 at 05:48:35PM -0700, Kaz Kylheku wrote:

> Anyone running 2.6.17 on the above Broadcom board or derivative?

I've got a success and a failure report for BCM1480 systems, both with
fairly recent kernels and 2.6.17.

  Ralf

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Manoj Ekbote]

Ralf,

Could you share the failure report that you have for BCM1480?

Thx
/manoj

-----Original Message-----
From: linux-mips-bounce@linux-mips.org
[mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Ralf Baechle
Sent: Friday, August 11, 2006 3:57 PM
To: Kaz Kylheku
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

On Thu, Aug 10, 2006 at 05:48:35PM -0700, Kaz Kylheku wrote:

> Anyone running 2.6.17 on the above Broadcom board or derivative?

I've got a success and a failure report for BCM1480 systems, both with
fairly recent kernels and 2.6.17.

  Ralf

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Manoj Ekbote wrote:
> Hi Kaz,
> 
> Kindly make sure that the below 2 patches have been applied.
>  
> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00021.html
> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00020.html
> 
> HTH,
> /manoj

Hi Manoj,

Thanks for the pointers to these patches. I have them in my patch
stack now. They don't solve the problem, but I'm keeping them.

I'm now going to do a binary search over the revision history to
find the very first kernel release which has the problem.  

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Manoj Ekbote wrote:
> Hi Kaz,
> 
> Kindly make sure that the below 2 patches have been applied.
>  
> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00021.html
> http://www.linux-mips.org/archives/linux-mips/2006-07/msg00020.html
> 
> HTH,
> /manoj

Hi Manoj,

Thanks for the pointers to these patches. I have them in my patch
stack now. They don't solve the problem, but I'm keeping them.

I'm now going to do a binary search over the revision history to
find the very first kernel release which has the problem.  

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Ralf Baechle:
> I've got a success and a failure report for BCM1480 systems, both with
> fairly recent kernels and 2.6.17.
> 
>   Ralf
> 

Thanks a lot Ralf.

The git bisect tool looks very cool; I will probably make use of it in
the future. However, I solved the problem at hand. It's the interrupt
dispatcher. I forward-ported the old assembly-language interrupt
dispatcher and the system now boots.

If I have time, I might look at the C code to see what it does
differently from the assembly code and try to fix it.

Cheers ...

RE: 2.6.17 on Broadcom BigSur (BCM91x80 A/B)

[Kaz Kylheku]

Ralf Baechle:
> I've got a success and a failure report for BCM1480 systems, both with
> fairly recent kernels and 2.6.17.
> 
>   Ralf
> 

Thanks a lot Ralf.

The git bisect tool looks very cool; I will probably make use of it in
the future. However, I solved the problem at hand. It's the interrupt
dispatcher. I forward-ported the old assembly-language interrupt
dispatcher and the system now boots.

If I have time, I might look at the C code to see what it does
differently from the assembly code and try to fix it.

Cheers ...