Port-macppc archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: NetBSD does not recognize USB keyboard



Hello,
I think the place to start is to see how the configuration can be extracted from the device tree. A clue to that would be how the boot process transfers the open source device tree to the requesting OS. I will work with you as best I can in accomplishing this. You will just have to remember that FORTH and open firmware are somewhat new to me. I will also need to know what modules of macppc are involved of that is necessary.
Frank

On May 31, 2008, at 3:56 PM, Michael Lorenz wrote:

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

Hello,

On May 30, 2008, at 23:40, Frank J. R. Hanstick wrote:

Hello,
FYI: If you just sent a post to port-macppc%netbsd.org@localhost, I will not get two email messages. The BootROM version is 4.2.5f1 and lists the following related devalias:

        adb                             /pci@F2000000/mac-io@17/via-pmu/adb
        adb-keyboard    /pci@F2000000/mac-io@17/via-pmu/adb-keyboard
        adb-mouse               /pci@F2000000/mac-io@17/via-pmu/adb-mouse

Those are just aliases - I have them too but they don't point at anything.

        keyboard                /pseudo-hid/keyboard
        mouse                   /pseudo-hid/mouse

Hmm, I've got /psuedo-hid/* like many other models. I wonder if our code only looks for /psuedo-hid

with pseudo-hid not defined. Under my configuration, the pseudo- hid alias should be

        pseudo-hid              /pci@F2000000/usb@18/hub@1/hub@1/device@1

because I have two external hubs fanned out rather than serialized. The fact that pseudo-hid is not defined means it does not matter if the keyboard is directly connected to the box or not, it still will not be seen via alias.

I don't have that devalias either - /pseudo-hid/* should take care of that.

        dev / ls shows the following at /pci@F2000000/mac-io@17/via-pmu:

        /rtc
        /power-mgt
        /power-mgt/usb-power-mgt

Ok, at least your firmware doesn't lie about ADB support.

        Does this help?

It's a hint, let's see if I can find anything. At least a workaround shouldn't be hard - with no ADB support present in the firmware we can skip the ADB-or-USB decision but I'd like to see that code working anyway.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSEHXl8pnzkX8Yg2nAQLlNQf/d0GjosZmFGx7b60mQZZEiFmHaZ1EnisO
W9j1J8FfzK25qwA64r3Y6xaAkjTMJPr/l8D6POUe1RWOslLCXZHL7tDqIj0xbDFN
VL8xz1F3fnRIjzBmWWT6eygRJ0OCwlGYOyhLlugh29ykbkDfIBNun/mLVVfSi+aW
DdJ0nc8FLkXZAzu/qma6Foo4JTw0J7j1C9fsjnSpt7YXpp93wlIVnQyTttU6+noV
x3NYzwi7n3cJJ2Q2PVRs5nJX7b3jchR720fKbM0+4jDATtB904ItHCXzedUrTe9A
KfO49cf/kOV5lPv4s6FWhh5M6AVKq1nnm2No2I3YnnMgoBzgg+Fpeg==
=iK/U
-----END PGP SIGNATURE-----



Home | Main Index | Thread Index | Old Index