OEMHLP$

[ktk]

Are there any changes needed on OEMHLP$? We do have a patched version by Martin Kiewitz and Veit was/is working on OEMHLP2.SYS, so the question is do we still need that and if so, for what reasons.

[ktk]

Snipped from the discussion in the list:

--

Veit you have been working on an OEMHLP2.SYS

that we can load as a basedev. Should we install this with ACPI ?

The driver file currently has 2 drivers, and one is required for the cbenable package to work. Maybe i should try to unbundle them.

Again its my lacking knowledge as to exactly what your update does for the kernel. Can your code be used a basis to patch OEMHLP in the kernel in memory !? I'm asking because Eugene Pasha want to put the functionalty of OEMHLP2 in ACPICA.ADD ?

Wrote driver code. In case of PCI functions, it handles them (both IOCTL and IDC). In other cases it forwads them to the 'original' driver. I can post the source if needed. The 'trick' to take over the 'OEMHLP' name is that OEMHLP2 searches the original driver header and changes the name (to 'OEMHL_$') and then renames itself to 'OEMHLP$'.

I have heard different opinions on resource.sys. Rudiger Ihle made a patched version that I think supports up to 64 IRQ's. Is further patching needed ? We have an old Warp 3 DDK source code. As I think Daniela mentioned, we miss a lot of updates.

If needed, i can try to make room in the current resource sys code and data segment to add some addiotinal code to add IRQ 16..48 resource types. could be semi-automatic in case IBM releases newer versions.

[pasha]

Replying to ktk:

Are there any changes needed on OEMHLP$? We do have a patched version by Martin Kiewitz and Veit was/is working on OEMHLP2.SYS, so the question is do we still need that and if so, for what reasons.

Now is don't actual?