On Fri, 2004-04-30 at 16:50, Guido Guenther wrote:
> On Thu, Apr 29, 2004 at 09:18:01AM +1000, Benjamin Herrenschmidt wrote:
> > We know how to extract the f-code, but we still need to write a
> > working OF environment to run it into
> Would
> http://www.openbios.org/development/kernel.html
>
On Thu, Apr 29, 2004 at 09:18:01AM +1000, Benjamin Herrenschmidt wrote:
> We know how to extract the f-code, but we still need to write a
> working OF environment to run it into
Would
http://www.openbios.org/development/kernel.html
help here.
-- Guido
signature.asc
Description: Digital sign
On Wed, 2004-04-28 at 22:23, Guido Guenther wrote:
> On Wed, Mar 03, 2004 at 10:28:07AM +0100, Michael Schmitz wrote:
> > OK; in the meantime I found out that stuff is missing in the OF
> > properties. Next try: 817 bytes of a NVDA,BMP property which is also
> > present in OF. No other large chunks
On Wed, Mar 03, 2004 at 10:28:07AM +0100, Michael Schmitz wrote:
> OK; in the meantime I found out that stuff is missing in the OF
> properties. Next try: 817 bytes of a NVDA,BMP property which is also
> present in OF. No other large chunks of data visible from OF.
I too looked through OF on my pbo
> > Boot into MacOS X, open a shell and run the command "ioreg -p
> IODeviceTree
> > -l -x -w 512000 > ioreg.out and send me the resulting file.
>
> Here are the ATY* entries reported by this command for an iBook G4 12"
> (not an nvidia, but should help too), kindly provided by Antoine Reilles.
Th
Hi,
> Boot into MacOS X, open a shell and run the command "ioreg -p
IODeviceTree
> -l -x -w 512000 > ioreg.out and send me the resulting file.
Here are the ATY* entries reported by this command for an iBook G4 12"
(not an nvidia, but should help too), kindly provided by Antoine Reilles.
Hope thi
> > You may be missing the part where the kernel copies the original device
> > tree data to wherever fs/proc/proc_devtree.c finds them later on to
> > display them :-)
>
>
> Mh, that's probably it.
> Looks like it's done in arch/ppc/syslib/prom.c but I don't find either :)
Nope, it's in arch/ppc/
> > Just for completeness, double check that OF isn't putting something
> > in the device-tree with the f-code already :) I doubt it, but since
> > linux "skips" too large properties when copying the device-tree during
> > boot, it might actually be there and not visible in linux...
>
> Btw, why do
> You may be missing the part where the kernel copies the original device
> tree data to wherever fs/proc/proc_devtree.c finds them later on to
> display them :-)
Mh, that's probably it.
Looks like it's done in arch/ppc/syslib/prom.c but I don't find either :)
--
Colin
This message represents
Hi,
> Just for completeness, double check that OF isn't putting something
> in the device-tree with the f-code already :) I doubt it, but since
> linux "skips" too large properties when copying the device-tree during
> boot, it might actually be there and not visible in linux...
Btw, why does it
> > Me? I don't own any recent sort of Mac laptop yet. And I'd probably go for
> > disk suspend instead, short term. The only thing that's strange there is
> > the system clock being restored to suspend time :-)
>
> I had a similar problem on my Pismo when waking up from sleep and
> using NTP. I fi
> > :-( That's all been on a flat panel iMac, though - we'd need same
> > information from a laptop user.
>
> I have the same error message on my powerbook 1GHz:
>
> pmud [treshold = 420, margin =15] started
> PMU Version 12: iBook/G3 Pismo/G4 Titanium
> No sleep support on this hardware, exiting!
On Wed, Mar 03, 2004 at 12:23:20PM +0100, Michael Schmitz wrote:
> > > OK; in the meantime I found out that stuff is missing in the OF
> > > properties. Next try: 817 bytes of a NVDA,BMP property which is also
> > > present in OF. No other large chunks of data visible from OF.
> >
> > Hrm.. No clue
On Wed, Mar 03, 2004 at 12:23:20PM +0100, Michael Schmitz wrote:
> > > OK; in the meantime I found out that stuff is missing in the OF
> > > properties. Next try: 817 bytes of a NVDA,BMP property which is also
> > > present in OF. No other large chunks of data visible from OF.
> >
> > Hrm.. No clue
> > OK; in the meantime I found out that stuff is missing in the OF
> > properties. Next try: 817 bytes of a NVDA,BMP property which is also
> > present in OF. No other large chunks of data visible from OF.
>
> Hrm.. No clue what this can be.
:-( That's all been on a flat panel iMac, though - we'd
> OK; in the meantime I found out that stuff is missing in the OF
> properties. Next try: 817 bytes of a NVDA,BMP property which is also
> present in OF. No other large chunks of data visible from OF.
Hrm.. No clue what this can be.
Maybe, in the long term, beeing able to shell the "ndrv" in a s
> > ioreg found this:
> >
> > "driver,AAPL,MacOS,PowerPC"
> >
> > with some hex data in it. I need to get it to dump only that property (the
> > output is clipped at col. 80 currently).
> >
> > I guess that's what we're looking for?
>
> No. That's the MacOS "ndrv" driver...
>
> (The MacOS equivalen
On Wed, 2004-03-03 at 02:35, Michael Schmitz wrote:
> > > Good idea - do you have a lsprop tool for MacOS X ?
> >
> > ioreg. Or use OF itself:
>
> ioreg found this:
>
> "driver,AAPL,MacOS,PowerPC"
>
> with some hex data in it. I need to get it to dump only that property (the
> output is clipped
> > Good idea - do you have a lsprop tool for MacOS X ?
>
> ioreg. Or use OF itself:
ioreg found this:
"driver,AAPL,MacOS,PowerPC"
with some hex data in it. I need to get it to dump only that property (the
output is clipped at col. 80 currently).
I guess that's what we're looking for?
On Sat, 2004-02-28 at 02:04, Colin Leroy wrote:
> > For M6/M7/M9 style chips, there is still
> > a lot to do to get it right, but ATI was kind enough to
> > provide me with the necessary code.
>
> Good news... Does "M9" include "M9+" ?
> Consider me in for beta-testing when you'll have something
El vie, 27-02-2004 a las 21:02, Yves Combe escribió:
> Carlos Perelló Marín a écrit :
> > As I said in the past, my TFT 15" iMac with a Nvidia GeForce2 MX/MX 400
> > sleeps and wakes up without problem since long ago, I think the problem
> > is only with laptops that should turn off the video card
On 27 Feb, this message from Gabriel Paubert echoed through cyberspace:
[snip]
> And now even Linus is using PPC ;-)
Linus/PPC ?
Although, that would be a good nick for BenH :-)))
Cheers
Michel
-
Michel Lanners
Carlos Perelló Marín a écrit :
As I said in the past, my TFT 15" iMac with a Nvidia GeForce2 MX/MX 400
sleeps and wakes up without problem since long ago, I think the problem
is only with laptops that should turn off the video card to save battery
power.
Wow! My pmac (bi G4 windtunnel, NVidia G
El vie, 27-02-2004 a las 11:05, Benjamin Herrenschmidt escribió:
> On Fri, 2004-02-27 at 03:49, Domingo Fiesta Segura wrote:
> > El Thursday 26 February 2004 09:04, Fleny68 escribió:
> > > Apple's sleep is not opensourced in darwin?
> >
> > Not now, but they used to be before. That is what Ben say
> For M6/M7/M9 style chips, there is still
> a lot to do to get it right, but ATI was kind enough to
> provide me with the necessary code.
Good news... Does "M9" include "M9+" ?
Consider me in for beta-testing when you'll have something...
--
Colin
This message represents the official view o
Hi Geert,
On Fri, Feb 27, 2004 at 02:27:52PM +0100, Geert Uytterhoeven wrote:
> On Fri, 27 Feb 2004, Michael Schmitz wrote:
> > > > What would it take to do just that - assuming the OF init code can be
> > > > accessed after kernel init, and all access to the chip can be blocked b
On Fri, 27 Feb 2004, Michael Schmitz wrote:
> > > What would it take to do just that - assuming the OF init code can be
> > > accessed after kernel init, and all access to the chip can be blocked by
> > > e.g. staying on the dummy fb console until after re-init?
> > >
> > > It's a sick idea, though
> > What would it take to do just that - assuming the OF init code can be
> > accessed after kernel init, and all access to the chip can be blocked by
> > e.g. staying on the dummy fb console until after re-init?
> >
> > It's a sick idea, though ..
>
> Not that sick, I've been considering it quite
> The boot ROM? I thought that wasn't all that big on newworlds...
It's 1Mb compressed iirc, and it contains OF along with the OF
F-code drivers for the built-in hardware.
> Good idea - do you have a lsprop tool for MacOS X ?
ioreg. Or use OF itself:
dev /[EMAIL PROTECTED]/ATY,blah
.propertie
On Fri, 2004-02-27 at 23:07, Michael Schmitz wrote:
> > scratch. It's not simple, it's probably undreds of magic values to
> > blast in specific non documented chip registers in the right sequence,
> > difficult to do without some support from ATI... Or a way to re-run
> > the OF f-code driver.
>
> scratch. It's not simple, it's probably undreds of magic values to
> blast in specific non documented chip registers in the right sequence,
> difficult to do without some support from ATI... Or a way to re-run
> the OF f-code driver.
What would it take to do just that - assuming the OF init code
On Fri, 2004-02-27 at 03:49, Domingo Fiesta Segura wrote:
> El Thursday 26 February 2004 09:04, Fleny68 escribió:
> > Apple's sleep is not opensourced in darwin?
>
> Not now, but they used to be before. That is what Ben says.
Nah, what is in Darwin is the necessary low level bits to get the
mothe
El Thursday 26 February 2004 09:04, Fleny68 escribió:
> Apple's sleep is not opensourced in darwin?
Not now, but they used to be before. That is what Ben says.
Fleny68 <[EMAIL PROTECTED]> writes:
> Colin Leroy a écrit :
>>>PowerBook G4 Alu 15"
>>
>> Well, sleep isn't supported by the kernel on this machine :-) (due to
>> the video chip)
I can't believe it!
> Apple's sleep is not opensourced in darwin?
You mean Apple sleeps?! ;-)
Cheers,
--
.''`.
Colin Leroy a écrit :
PowerBook G4 Alu 15" (or '?! ;-)
$ uname -a
Feb 25 18:39:19 oz pmud[9477]: No sleep support on this hardware,
exiting!
If someone knows what happens ;-)
Well, sleep isn't supported by the kernel on this machine :-) (due to the
video chip)
Apple's sleep is not ope
> PowerBook G4 Alu 15" (or '?! ;-)
> $ uname -a
>
> Feb 25 18:39:19 oz pmud[9477]: No sleep support on this hardware,
exiting!
>
> If someone knows what happens ;-)
Well, sleep isn't supported by the kernel on this machine :-) (due to the
video chip)
--
Colin
This message represents the offic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PowerBook G4 Alu 15" (or '?! ;-)
$ uname -a
Linux oz.fapse.ulg.ac.be 2.6.3-rc2-ben1
#1 Sat Feb 14 15:54:36 CET 2004 ppc GNU/Linux
Trying to start pmud, I got:
Feb 25 18:39:19 oz pmud[9477]: pmud [treshold = 420, margin = 15] started
Feb 25 18:39:19
37 matches
Mail list logo
