Open PRs

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

there's a bunch of ancient PRs related to NetBSD/macppc
which I'd like 
to get rid of. Namely:

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=11894
Subject: simultaneous nfs and ftp transfer hangs tcp stack
The PR is about 1.5, can anyone still reproduce this? I
can't and if no 
one else can I'll assume it has been fixed and close the
PR.

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=25966
Subject: IDE drives no longer detected
That's about 2.0_BETA on a beige G3. I think it has been
fixed but I'd 
like to hear if anyone still has this problem.

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=11420
Subject: LCD screen goes black (or is dimmed) during boot
1.5H on a PowerBook Lombard. Does it still happen?

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=29348
Subject: can't use PowerBook's trackpad
That's about 2.99.15 on a PowerBook G4 - can anyone still
reproduce it?

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=24778
Subject: netbsd/macppc won't book on PowerBook G4 (12-inch
DVI)
That's about 1.6, the IDE driver seems to have trouble and
the keyboard 
doesn't work. Since there were numerous fixes in these
areas - can 
anyone still reproduce it?

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=13545
Subject: mc0 ping fails on 1.5.1 install (macppc)
Looks more like a bug in the 1.5.1 installer - does it still
happen? It 
didn't in 1.6.2 on my S900 but I'd like to have some
confirmation.

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=21289
Subject: XFree86 on PowerBook G4 -- cannot open /dev/pci0
Looks like a missing device node to me or can anyone confirm
that 
there's more to it?

http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=13022
Subject: X Window System VRAM mapping problem
Looks like a bug in whatever XFree shipped with -current 1.5
or some 
serious misconfiguration. Can anyone reproduce the problem?

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRN5NZspnzkX8Yg2nAQKExAf/X11eSBJAd/2+2BsoX6NMf4TxISxu
Fjfw
vQi7bRB4jRcBaFL0ZxOGgQeFx6CpptuY+F8T0/tZSlPhgbr9R4fg2JRlBKP3
+4ut
Kl0hL/T+8SekCEGrvYp6L6e7KwLrmVOmN7nTyqt2AOZwTJIpZBGJRDhlNeow
j5V9
xWMs56DQ4wbLdrSuz+5lpvsSbZ5Vqbx2ncczWa7ZPZdedgCVeLtzRfnMcYFw
ch0w
MOxUmo6UDcihnCrcrjtSQSmU0GluNX2ytpI0ICpbxa08Puyj957r0s+fEyAJ
cAo9
JGSXGrXn9E9fOMK3P/uOs1rZXT7jgoUHMqozbQ4JhBY/yzHcZaH2pg==
=wMji
-----END PGP SIGNATURE-----

On Aug 12, 2006, at 5:51 PM, Michael Lorenz wrote:

> http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=11420
> Subject: LCD screen goes black (or is dimmed) during
boot
> 1.5H on a PowerBook Lombard. Does it still happen?

As of 2.99.something or equivalent it was also happening on
the  
Wallstreet. As soon as abtn0 is loaded the screen shuts off
if you  
have a clear nvram, you have to push the brightness keys to
bring it  
up and it never reaches full brightness ever again. Only
before abtn  
is loaded. 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Aug 13, 2006, at 00:26, Chris Tribo wrote:

> On Aug 12, 2006, at 5:51 PM, Michael Lorenz wrote:
>
>> http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=11420
>> Subject: LCD screen goes black (or is dimmed)
during boot
>> 1.5H on a PowerBook Lombard. Does it still happen?
>
> As of 2.99.something or equivalent it was also
happening on the 
> Wallstreet. As soon as abtn0 is loaded the screen shuts
off if you 
> have a clear nvram, you have to push the brightness
keys to bring it 
> up and it never reaches full brightness ever again.
Only before abtn 
> is loaded.

Most likely that's the same problem as machines turning
themselves off 
when you try to adjust brightness - happened on my iBook G4.
Our PMU 
communication code is bust, on most halfway recent models
the only 
thing that seems to work is ADB.

I bet when the PMU code is fixed all these problems will
just go away.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRN6u0cpnzkX8Yg2nAQI40AgAqt9aLJHCE0UZ3/KFMTZpG9SOETAB
7PBm
mNqEFs2BllQsVOQCJMV57suZrhcsO88FEV11PDTurtYu+7PzCjTevJCYxJUV
Kzw6
9iGqmeWgsbjHHMtmdIwbzw7XFKm74EeXTdtR/p+/3CxENeXydBMBVsOtT40r
R+dV
8p4DYRV+M1DVg3VQvfd8AddpL1CDX20bWyh64RW1DIx3UwvPZHFplXb5UHuq
R7dx
ylqK8s5hE1HDr1wCuVMlSzL+Z1dh2aGviBGP4+OUUAqM4LqB2uiieFlRDk4u
8Pqn
BgXWr95K88xtfqkZKpbcPzj9M83YbWFPVbf0pbBSrzkaIYSZC7isuQ==
=HR2O
-----END PGP SIGNATURE-----

| To: netbsd-macppc macppc <port-macppcNetBSD.org>
| From: Michael Lorenz <macallanNetBSD.org>
| Subject: Open PRs
| Date: Sat, 12 Aug 2006 17:51:33 -0400

> http://www.netbsd.org/cgi-bin/query-pr-single.pl?nu
mber=13022
> Subject: X Window System VRAM mapping problem
> Looks like a bug in whatever XFree shipped with
-current 1.5 or some 
> serious misconfiguration. Can anyone reproduce the
problem?

Thanks Michael keeping track of ancient PR's.
I have several reasons to decline this PR, sorry:

(1) The machine, G4/350, was the one in my previous firm
which I
 have no longer access to the box.
 It is kind of rare model before by G4/400(PCI) came out.

(2) It is too old (5 years now).

(3) To my understanding, the screen size of Open Firmware
 depends video driver in lower part of the disk partition, 
 which we may only able to update from Mac OS. It's likely
 out of our control .. (?)

 I have tried to change screen size with:
 > dev screen
 > words
 > show-modes
 > 22 enable-videomode
 > 22 set-mode
   ( garbaged screen )
 > reset-all
   (return to the 640x400)

Thanks anyway,
---
Makoto Fujiwara

On 8/13/06, Michael <macallan1888gmail.com> wrote:

>
> Most likely that's the same problem as machines
turning themselves off
> when you try to adjust brightness - happened on my
iBook G4. Our PMU
> communication code is bust, on most halfway recent
models the only
> thing that seems to work is ADB.

I've got an OFW wrapper driver for brightness control:

See:

http://mail-index.netbsd.org/port-macppc/2006/07/17
/0000.html

for the discussion,

and

ftp://ftp.netbsd.org/pub/NetBSD/misc/cherry/macppc

for code.

>
> I bet when the PMU code is fixed all these problems
will just go away.

Its more to do with using the right PMU routines on the
right models.
Blame the MD autoconf :-(

I'll try to beat it up as soon as I get a replacement
notebook soon (TM)

-- 
~Cherry