-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
Some SIO/PNP devices are abusing register 0x30 for multiple LDN enables, like mine W83627EHF.
This patch introduces a concept of virtual LDN. Each virtual LDN is unique, but maps to original LDN and bit position in register 0x30.
VirtualLDN = origLDN[7:0] | bitpos[10:8]
For example mine GPIO5 device is on LDN 0x9 and bit position 3 -> virtualLDN is 0x309.
As the nice effect one can have now in Config.lb right enable:
device pnp 2e.309 on #GPIO5 on end
Plus normal resources if it is a GAME port for example:
device pnp 2e.107 on #GAME on io 0x60 = 0x201 end
This patch just modifies the core PNP subsystem, other patches will follow.
Signed-off-by: Rudolf Marek r.marek@assembler.cz
Thanks,
Rudolf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I forgot to show the boot log: http://assembler.cz/download/bootldn.txt
Rudolf
Rudolf Marek wrote:
Plus normal resources if it is a GAME port for example:
device pnp 2e.107 on #GAME on io 0x60 = 0x201 end
So this is the same as the following?
device pnp 2e.7 on io 0x60 = 0x201 end
Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
So this is the same as the following?
device pnp 2e.7 on io 0x60 = 0x201 end
Nope because 2e.7 is just handling bit0 in reg 0x30
2e.107 handles bit1 reg 0x30
Rudolf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello
In other words, it is fully compatible with existing code base, except of the small change in pnp_device.c. No other files needs to be modified in any way (only if the superio has same multiple enable bits).
Lets say 2e.7 handles the "original" bit0 trigger and other bit triggers in 0x30 are handled by 2e.107 2e.207 2e.307 ... 2e.707
Thanks,
Rudolf
* Rudolf Marek r.marek@assembler.cz [080217 01:24]:
This patch just modifies the core PNP subsystem, other patches will follow.
Signed-off-by: Rudolf Marek r.marek@assembler.cz
Acked-by: Stefan Reinauer stepan@coresystems.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Thanks,
Committed revision 3104.
Rudolf