linux-mips
[Top] [All Lists]

Re: au1000_lowlevel_probe on au1000_eth.c

To: Ulrich Eckhardt <eckhardt@satorlaser.com>
Subject: Re: au1000_lowlevel_probe on au1000_eth.c
From: Rodolfo Giometti <giometti@linux.it>
Date: Tue, 27 Jun 2006 09:34:36 +0200
Cc: linux-mips@linux-mips.org
In-reply-to: <200606270836.09057.eckhardt@satorlaser.com>
Organization: GNU/Linux Device Drivers, Embedded Systems and Courses
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20060626221441.GA10595@enneenne.com> <200606270836.09057.eckhardt@satorlaser.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.5.1+cvs20040105i
On Tue, Jun 27, 2006 at 08:36:08AM +0200, Ulrich Eckhardt wrote:
> 
> 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.

I see. But maybe the «best» thing to do is just to skip these settings
during wake up after a sleep since they are magniful only during boot
time...

Ciao,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail:    giometti@enneenne.com
Linux Device Driver                             giometti@gnudd.com
Embedded Systems                                giometti@linux.it
UNIX programming                     phone:     +39 349 2432127

Attachment: signature.asc
Description: Digital signature

<Prev in Thread] Current Thread [Next in Thread>