Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulrich Eckhardt <eckhardt@satorlaser.com>
To: linux-mips@linux-mips.org
Subject: Re: au1000_lowlevel_probe on au1000_eth.c
Date: Tue, 27 Jun 2006 08:36:08 +0200	[thread overview]
Message-ID: <200606270836.09057.eckhardt@satorlaser.com> (raw)
In-Reply-To: <20060626221441.GA10595@enneenne.com>

On Tuesday 27 June 2006 00:14, Rodolfo Giometti wrote:
> I notice that during sleep/wakeup au1000_lowlevel_probe() tries to
> access to variables arcs_cmdline,prom_envp & Co.. This sometime does
> an oops.
>
> What I like to understand is if I simply have to skip accessing to
> these variables during wake up or I have to save them during system
> boot or what...?

What is the _right_ thing is difficult to answer, but the reasons for the oops 
are simple (at least they were on the platform I used): you have more than 
one device connected to the same system bus. In my case, it was the boot-PROM 
and (I think) the PCMCIA memory. So, in practice one could only access one of 
the two and you had to toggle between them. I'm not sure it is worth the 
hassle of toggling (and doing so in an orderly fashion!), I'd rather parse 
the PROM once and then store the results in RAM.

HTH

Uli

****************************************************
Visit our website at <http://www.domino-printing.com/>
****************************************************
This Email and any files transmitted with it are intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any reading, redistribution, disclosure or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient please contact the sender immediately and delete the material from your computer.

E-mail may be susceptible to data corruption, interception, viruses and unauthorised amendment and Domino UK Limited does not accept liability for any such corruption, interception, viruses or amendment or their consequences.
****************************************************

  reply	other threads:[~2006-06-27  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 22:14 au1000_lowlevel_probe on au1000_eth.c Rodolfo Giometti
2006-06-27  6:36 ` Ulrich Eckhardt [this message]
2006-06-27  7:34   ` Rodolfo Giometti
2006-06-27 15:59 ` Rodolfo Giometti
2006-06-29 15:03   ` Sergei Shtylyov
2006-06-29 15:11     ` Rodolfo Giometti
2006-07-02 19:22       ` Sergei Shtylyov

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=200606270836.09057.eckhardt@satorlaser.com \
    --to=eckhardt@satorlaser.com \
    --cc=linux-mips@linux-mips.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