Chameleon 2.0 Extension.mkext loading

[parken]

I have two Extensions.mkext: one in /Extra and the "vanila" /System/Lybrary/Extensions.mkext.
/Extra/Extensions.mkext contains some older kexts that are also present in /System/Lybrary/Extensions.mkext, but with a higher version number.
How does Chameleon present this two mkexts to the kernel? Does ignore /System/Lybrary/Extensions.mkext altogether or it does selectively skip older/Extra/Extensions.mkext components?
Tanks in advance for help.

[thorazine74]

If I understand it right all kexts look the same to the kernel, and it chooses the most appropiate according to its matching rules, and higher version kext would always be preferred than lower, so if you need a kext in extra to override another one in s/l/e you would need to bump up its version.

[parken]

thorazine74, thanks for your answer.
I'm afraid that either the kernel's matching rules are more sophisticated, or Chameleon way of presenting mkexts to the kernel is more selective: my /E/*.mkext carries three kexts that are of a previous version n. than those present in /S/L/*.mkexts (to be precise the AppleIntelGMA950.kext 6.0 vs 6.0.2, the AppleIntelIntegratedFramebuffer.kext 6.0 vs 6.0.2, and the IOATAFamily.kext 2.0.1 vs 2.5).
If I look at what is actually running in my system (with kextstat) what is laded is :
AppleIntelGMA950.kext 6.0
AppleIntelIntegratedFramebuffer.kext 6.0
IOATAFamily.kext 2.5

It might be that the first two have been hacked themselves to override the newer versions (IOATAFamily.kext is genuine Apple's from 10.5.7 and 10.6 respectively), but I would like to know precisely what is Chameleon's behavior for the future updates...