Re: possible endless loop in PROM initialization

2007-08-20 Thread Krzysztof Helt
On Mon, 20 Aug 2007 12:53:20 +0200 Markus Dahms <[EMAIL PROTECTED]> wrote: > Hello again, > As I'm not sure anymore whether the device tree (show-devs) or the aliases > (devalias) are broken on the Classic X (I "upgraded" mine to a Classic by > changing some NVRAM bytes) this may be a non-issue.

Re: possible endless loop in PROM initialization

2007-08-20 Thread Markus Dahms
Hi, >> | ok devalias scsi /iommu/sbus/espdma/esp >> | scsi isn't unique > Non-unique devalias entries are NASTY. Get rid of them, for example > your second definition of scsi could be changed to scsidisk. Yes, it is nasty and I don't really want to use it. But it is possible and IMHO Linux should

Re: possible endless loop in PROM initialization

2007-08-20 Thread Chris Newport
Markus Dahms wrote: Hello again, David Miller wrote: When we boot the firmware provides a vector of function pointers, and this is prom_nodeops. So prom_nodeops->no_nextprop() is a routine inside the PROM. Thanks. So there is no real chance to fix it but to override this function? T

Re: possible endless loop in PROM initialization

2007-08-20 Thread Markus Dahms
Hello again, David Miller wrote: > When we boot the firmware provides a vector of function > pointers, and this is prom_nodeops. So prom_nodeops->no_nextprop() > is a routine inside the PROM. Thanks. So there is no real chance to fix it but to override this function? The strange thing is that th

Re: possible endless loop in PROM initialization

2007-08-20 Thread David Miller
From: Markus Dahms <[EMAIL PROTECTED]> Date: Mon, 20 Aug 2007 09:59:49 +0200 > I could track down the issue to the function __prom_nextprop() in > arch/sparc/prom/tree.c, but I am now looking for the definition of > prom_nodeops->no_nextprop() without success. When we boot the firmware provides a