public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Newport <crn@netunix.com>
To: Markus Dahms <mad@automagically.de>
Cc: David Miller <davem@davemloft.net>,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: possible endless loop in PROM initialization
Date: Mon, 20 Aug 2007 12:43:59 +0100	[thread overview]
Message-ID: <46C97E7F.3010604@netunix.com> (raw)
In-Reply-To: <20070820105320.GB4911@vimes.madsworld.lan>

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?
>The strange thing is that the PROM prompt handles it correctly:
>
>| 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.
You should also check that any nvramrc entries do not cause conflicts,
it is common for nvramrc entries to refer to devalias entries, so you 
may need to also change an nvramrc entry to match any devalias change.

You can disable the use of nvramrc from the OBP prompt with
setenv if the entry isnon-essential, they are most commonly used
where there is a mirrored root disk.



  reply	other threads:[~2007-08-20 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20  7:59 possible endless loop in PROM initialization Markus Dahms
2007-08-20  8:06 ` David Miller
2007-08-20 10:53   ` Markus Dahms
2007-08-20 11:43     ` Chris Newport [this message]
2007-08-20 13:19       ` Markus Dahms
2007-08-20 18:19     ` Krzysztof Helt
2007-08-20  8:50 ` Odp: " Krzysztof Helt
2007-08-20 10:34   ` Markus Dahms

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=46C97E7F.3010604@netunix.com \
    --to=crn@netunix.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mad@automagically.de \
    --cc=sparclinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox