Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Lars

Pages: [1] 2 3 ... 27
1
Events / USB maintainer wanted!
« on: August 09, 2019, 08:40:10 am »
In October I will be working in a foreign country for 2 years.
That will also be the moment in time where I will move away from OS/2.
If there is interest to take over the USB repository and if you have the necessary skills to maintain/further develop the drivers then please let me know and I can help you to quickly pick up.

2
Applications / Re: XWP v1.0.13 Beta 1
« on: August 06, 2019, 07:33:31 am »
It also works here.
I do like the automatic setup of the reboot menu but would it be possible to remove/avoid the entries for USB sticks/HDDs (that had been plugged in on system start) and only keep those for fixed disks ?

3
Applications / Re: XWP v1.0.13 Beta 1
« on: August 06, 2019, 07:21:44 am »
Hi Rich, it is working fine here for the moment.

Thanks for the full version, I got used to the "Pack this tree" and I use the "WPS Class List" also.

It is not a bug. About "WPS Class List", where can I suggest some text for some undocumented classes?
Like "CWBubblepad": "This is a replacement class for LaunchPad included in the Bubblepad package. Reduces the size of the original launchpad. The drawers may be hidden and every action button may be independently removed. "

Regards

\tools\wps\xworkplace\help\xfclsXXX.txt where "XXX" is your language code.

4
General Discussion / Re: Email address of Dave McKenna ?
« on: August 05, 2019, 07:18:27 am »
I now have it, never mind.

5
General Discussion / Email address of Dave McKenna ?
« on: August 04, 2019, 03:14:07 pm »
Can anyone provide me with his email address ?
If yes, please do not post it publicly on this forum but send it privately via email:
lars dot erdmann at arcor dot de

Lars

6
Hardware / Re: ArcaOS Hardware Support Discussion
« on: August 04, 2019, 12:21:18 pm »
Unfortunately, I know too little about UEFI. The only things I know:

1) I have a machine with UEFI and CSM (compatibility support module = legacy BIOS support). It does have legacy USB support and even though the support is a bit buggy it works well enough for the USB keyboard to be usable without native USB drivers taking over support (I can boot to an OS/2 commandline without ANY USB drivers loaded and still use the keyboard)

2) I know of at least one other person that does have a machine with a legacy BIOS (or UEFI and CSM, I cannot remember) that however does NOT have legacy USB support. On this system, you will NOT have any USB support unless a native USB driver takes over support. My belief is that if this machine is a UEFI+CSM machine that then, ONLY UEFI USB drivers are provided along with the BIOS so that you can enter the BIOS (to change settings) or boot to a UEFI console and use the USB mouse/USB keyboard.

However "UEFI USB drivers" work completely differently: they are completely implemented in the BIOS FW and they DIRECTLY support USB mouse and keyboard (in the same way that the OS/2 SW drivers support that USB HW). In contrast, "legacy USB" support uses USB host controller HW support and also SMI to "fake" to the BIOS that an USB mouse/keyboard is a PS/2 keyboard/mouse. In short: this works completely differently. And the USB HC HW support for "legacy" operation is optional (USB HC HW does not have to provide this support).

That said, I DO believe that "legacy USB" support as we now it today will die sooner or later.

Lars

7
Hardware / Re: ArcaOS Hardware Support Discussion
« on: August 04, 2019, 12:11:50 am »
Some info:

1) I think there is no chance that booting from a USB device attached to a plug-in USB card will actually work. I seem to remember that there are some HW limitations that will prevent this from working (some necessary HW signal line not wired via the PCI slot).

2) yes, VIA UHCI host controllers are supported. As far as I understand from ivan, the USB keyboard and trackball work if they are attached to the 2 "USB 2.0 only" USB ports for "normal" operation, that means, way past the boot stage. If the mouse and keyboard support does not work in the booting stage (that is, while you are presented with a fullscreen text mode with the driver signon messages showing etc.) then that either means that the system does not have USB legacy support in the "conventional" BIOS/UEFI CSM layer (that is, disregarding USB support via the UEFI BIOS which does not help OS/2 as OS/2 does not boot up via UEFI) or that the USB support breaks when switching from USB legacy support to native USB support.
What you could try out: back up \os2\boot\config.x and then remove all USB support from this file.
Then, restart the system, hit Alt-F1 and then F2 which will get you to a full screen commandline. Test the USB keyboard, it should work. If not, you are hosed and your system does not support legacy USB (via the "conventional" BIOS / UEFI CSM layer).
Don't forget to reinstate the original \os2\boot\config.x file after the test !

Lars

8
Hardware / Re: ArcaOS Hardware Support Discussion
« on: August 03, 2019, 03:09:03 pm »
Quote
I had to borrow a keyboard with a PS/2 plug to get everything up and working again

This is one of the main problems with using USB keyboards. They don't work after the BIOS loses control (sometime early in the boot sequence), and before the driver initializes (right at the end of the boot sequence). At that time, USB keyboards cannot be used to do simple things like hit <enter>. This is not new with new USB drivers, it has always been the case.

No this is not true. The idea is to prevent the HC drivers from resetting the host controllers until finally the system is up and running in order to not prematurely break legacy USB support. It is the job of USBD.SYS to call into the HC drivers to trigger the host controller reset and once this is done to start the enumeration process (as then the HUB HW is able to properly do its work and react to port checking requests etc.). So, the idea is to delay this process until finally the system has booted far enough to no longer need USB legacy support.

I have modified my USB drivers to do just that: USBD.SYS queues the HC driver registration requests with a timer. It additionally checks if the system has already notified (via USBMSD.ADD calling into USBD.SYS) that INT13 boot support for USB MSD is no longer needed. If the timer expires (no more HC drivers asked for registration + the system has signaled it no longer needs INT13 boot support), then USBD.SYS will go ahead and reset the HC controllers.
I can easily boot to a commandline via Alt-F1 and F2 and then use my USB keyboard. There is a short moment where the keyboard will not work from the point in time where the HC drivers have been reset (and legacy USB support ceased) until native USB support has been enabled but you can continue to type and it will eventually continue to work, in practice I have no problem using a USB keyboard from a booted up commandline.
If I additionally run "lvm /rediscoverprm" from that commandline, I can also use attached USB MSD devices.

But of course, the BIOS has to provide legacy USB support. I wonder how long that will still be the case.

The upcoming 10.229 version of my drivers will have the rest of changes I have missed in the past to support the behaviour mentioned above.

9
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: August 01, 2019, 05:13:21 am »
Ok, I just realized that I also need to update USBMSD.ADD and USBD.SYS. I will send the modified set as soon as I have tested all the changes.

10
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: July 30, 2019, 08:12:19 am »
Just retested with Lars latest USB drivers installed again.

ArcaOS 5.04.  Moved the BASEDEV=USBD.SYS before the other basedev drivers as the way 5.04 does.

BASEDEV=USBD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBHID.SYS

Rebooted and the mouse does not work.  Note: the USB mouse did work with the USB drivers installed with ArcaOS 5.04 when using the above ordered config.sys.

Switched BASEDEV=USBD.SYS back to the order done in earlier versions of ArcaOS.

BASEDEV=USBOHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBD.SYS
BASEDEV=USBHID.SYS

rebooted and the mouse works with Lars drivers.

If you can get me a private email address, I can send you updated USB?HCD.SYS test drivers that no longer rely on a specific config.sys ordering regarding USBD.SYS. You'll never have to touch your config.sys again :-)
It works here, once I know that it works for you I can release a new set of drivers.

Lars

11
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: July 30, 2019, 08:10:48 am »
In fact the Linux "guys" had full support from some Intel lady which eventually implemented (or led implementation of) the USB 3 driver for Linux.
Implementing an USB host controller driver is trial and error.

12
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: July 29, 2019, 02:54:01 pm »
Currently USBxHCD.SYS HC drivers try to register with USBD.SYS already on INIT. That will only succeed if USBD.SYS loads BEFORE these drivers (if USBD.SYS is first in config.sys). Therefore USBxHCD.SYS will try to register with USBD.SYS also on INIT_COMPLETE if the registration failed on INIT. That covers the case that USBD.SYS loads AFTER these drivers because INIT_COMPLETE will be called once ALL drivers have loaded (gone through INIT).
Obviously, the system does not seem to like it if the HC drivers already register on INIT. I will try and remove the registration already on INIT. Then, the HC drivers will register with USBD.SYS only if ALL drivers (regardless of config.sys ordering) have already loaded which would make the load ordering in config.sys irrelevant.
The code comments implied that all that was relevant if you boot from a USB floppy drive / CD-ROM. I just take it for granted that my drivers would then possibly no longer allow to boot from USB.

13
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: July 29, 2019, 09:27:03 am »
sorry, but I don't understand.
If you are using the 12.1 driver stack then you do not use my USB drivers I suppose.
And if you use my USB drivers there is no need to change the config.sys USBD.SYS ordering (but I think you can do so without any negative effect but I will need to try out).
As far as USBAUDIO.SYS and USBAUD2.SYS and potentially USBMSD.ADD goes, there is no need to change anything in config.sys. They are in no way affected by the USBD.SYS ordering in config.sys.

14
Hardware / Re: USBDRV 10.225 - full support for USB audio
« on: July 28, 2019, 03:10:14 pm »
I now uploaded usbdrv228 to hobbes. It contains all of Wim's changes regarding USBAUDIO and USBAUD2 plus changes to USBWAV.

15
Programming / Re: SOMOBJ.H syntax errors
« on: July 25, 2019, 08:56:01 am »
Looks like structure "som3InitCtrl" is not recognized which in turn means that some other header file is not included or does not contain this structure definition but it should.
You should do a tree search of all header files and find the file that contains "som3InitCtrl" structure definition. you should then check why it is not included. You should check if the structure definition is bracketed by some define and if yes, why that define is not set or set it manually from the compiler command line.
Beware, there are header files that DO NOT end with the .h extension. For example I seem to remember a header file with an .api file extension.

"som3InitCtrl" is defined in somapi.h which should be included by top-level som.h (which also includes somobj.h) . You should check why this does not happen for you. You might only have one file somobj.h but you might have multiple files som.h. You might also need to run a different version of sc.exe (preferably the one from the OS/2 toollkit).

Pages: [1] 2 3 ... 27