Author Topic: Hardware Compatibility Wishlist for 2022  (Read 22153 times)

Lars

  • Hero Member
  • *****
  • Posts: 1268
  • Karma: +65/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #15 on: January 21, 2022, 10:00:21 am »
Yes, but how does the video (and audio) stream get to an application such as a web browser? And how does the application control the camera (perhaps focus for example), get capabilities and such? It does look like Mozilla will handle the transcoding and likely the muxing
Guess I could enable webrtc and see where the compile breaks.
Yes, we need an application that actually uses libuvc. As to controls, the libuvc example app schedules an irq in transfer in addition to the iso in transfers for the video data. The irq endpoint then delivers a message when you pres/release the camera button (at least it does for my camera). The application will need to decode that message to find out if a button has been pressed or released (2 different messages) and if yes, which one in case there are more buttons than one (I hope this is standardized).

As far as I understood BWW, the new browser (which is currently on hold) will use libuvc to get data and send over www and hopefully display received data in a browser tab (?) but maybe I got that wrong.

But it would be great if we could port webrtc to work on our platform.
« Last Edit: January 21, 2022, 10:22:35 am by Lars »

Roderick Klein

  • Hero Member
  • *****
  • Posts: 653
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #16 on: January 21, 2022, 03:50:37 pm »
Browser development is going to pickup again. We have collect SOME funding, but we need more.

Roderick Klein
OS/2 VOICE

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4775
  • Karma: +99/-1
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #17 on: January 21, 2022, 05:25:42 pm »
But it would be great if we could port webrtc to work on our platform.

Well, QT5's web engine also supports webrtc, which I guess is what BWW is planning on enabling. For Mozilla, it would require someone who knows what they're doing. Hopefully BWW will solve the remaining problems with the new browser.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4696
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Hardware Compatibility Wishlist for 2022
« Reply #18 on: January 21, 2022, 06:07:34 pm »
Hi

Just trying to organize the ideas without any order or weights we have:

- Audio and Camera support for a Videoconference tool.
- Bluetooth support for Keyboard and Mouse.
- GPT support for large disks.
- 2.5 Gigabit Ethernet PCI Express.
- Intel Wifi support.
- Dual Screen Support
   - Intel HD dual screen support. (To mirror screen or extend screen)
   - Easier Hot plug to projectors. (To mirror screen or extend screen)

I think I would like to add to the list:
- Hibernate support for PCs  / Laptops.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Roderick Klein

  • Hero Member
  • *****
  • Posts: 653
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #19 on: January 21, 2022, 06:46:47 pm »
Hi

Just trying to organize the ideas without any order or weights we have:

- Audio and Camera support for a Videoconference tool.
- Bluetooth support for Keyboard and Mouse.
- GPT support for large disks.
- 2.5 Gigabit Ethernet PCI Express.
- Intel Wifi support.
- Dual Screen Support
   - Intel HD dual screen support. (To mirror screen or extend screen)
   - Easier Hot plug to projectors. (To mirror screen or extend screen)

I think I would like to add to the list:
- Hibernate support for PCs  / Laptops.

Regards

That large hard disc support with GPT is already working. See the readme file of the AHCI driver of Arca Noae.
http://trac.netlabs.org/ahci/browser/trunk/src/os2ahci/ReadMe.txt
Added support for 48/64 bit LBA operations.

But it seems you need the GPT filter driver for this to work which is included in ArcaOS 5.1.0. beta.

Roderick

Roderick Klein

  • Hero Member
  • *****
  • Posts: 653
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #20 on: January 21, 2022, 06:50:17 pm »
- 2.5 Gigabit Ethernet PCI Express.

Best I can tell this requires no special support. If somebody has such a chipset is not supported open a ticket at Arca Noae if you have such a chipset,
https://www.arcanoae.com/wiki/multimac/

"These drivers exist and are included in the MultiMac distribution because someone needed them and requested a driver.  MultiMac drivers are typically very easy to create. If you have a specific network adapter that is not supported by an existing MultiMac driver and you need a driver for it, please open a ticket and request a new driver. Make sure you attach a TestLog log file to your ticket."

Roderick

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #21 on: January 22, 2022, 02:03:13 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Roderick Klein

  • Hero Member
  • *****
  • Posts: 653
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #22 on: January 22, 2022, 03:22:54 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Discussed in this forum before plenty of times. Maybe the os/4 team can comment.
My technicall estimate to get this in current os/2 kernel.
Well not going happen...

Putting in this support will require big big changes.


Roderick

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #23 on: January 22, 2022, 03:40:43 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Maybe the os/4 team can comment.
My technicall estimate to get this in current os/2 kernel.
Well not going happen...

Roderick

OS/4 uses PSE-36 for quite a long. But for ram drive only.
To use PSE-36 or PAE for general propose memory   requires   totally  rewrite kernel component "Pager" and all PDD at least.  So "Well not going happen... (С)".

Roderick Klein

  • Hero Member
  • *****
  • Posts: 653
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #24 on: January 22, 2022, 04:27:14 pm »
I have another one: Support up to 4 GB RAM for the system with addition of Physical Address Extension.

Maybe the os/4 team can comment.
My technicall estimate to get this in current os/2 kernel.
Well not going happen...

Roderick

OS/4 uses PSE-36 for quite a long. But for ram drive only.
To use PSE-36 or PAE for general propose memory   requires   totally  rewrite kernel component "Pager" and all PDD at least.  So "Well not going happen... (С)".

Thanks for the technical clarification.

Roderick

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #25 on: January 22, 2022, 05:17:48 pm »
Thanks, OS4User. RAM disk is not an option, when only 1 GB or less is recognized for the system. AMD systems suffer since a longer time from this, with 1.5 - 2 GB. According to Sigurd, newer Intel (i7) systems have that problem, too.

Virtualization seems to be the only option then.

Are there any newer systems that support 3 GB?

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #26 on: January 22, 2022, 05:25:32 pm »
RAM disk is not an option, when only 1 GB or less is recognized for the system.

OS/4 PSE-36 RamDrive  uses mem above 4Gb,  so 1Gb recognized by the system   is  for system :)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4775
  • Karma: +99/-1
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #27 on: January 22, 2022, 06:24:44 pm »
Thanks, OS4User. RAM disk is not an option, when only 1 GB or less is recognized for the system. AMD systems suffer since a longer time from this, with 1.5 - 2 GB. According to Sigurd, newer Intel (i7) systems have that problem, too.

Virtualization seems to be the only option then.

Are there any newer systems that support 3 GB?

Even with only 1.5GB of actual ram recognized by the system, you still should have about 3.5 GB of memory space, it'll just swap and the swap file can go on the ram disk.
At one point I was using a system with 1.5GB's of ram installed, linking xul.dll required VIRTUALADDRESSLIMIT set to 3072 to avoid running out of memory, the swap file would grow to close to 2 GB (occasionally over which killed the system with a swap file full error, there seems to be a 2GB limit), things would be slow but work.
With 1.5 GB of ram under normal usage you should only see light swapping.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #28 on: January 22, 2022, 11:42:00 pm »
Here are 2 GB recognized. When the Mozilla browser eats up all memory and the system has started to swap (SSD), it becomes unstable. I guess that's rather a browser problem with newer Web pages.

Sometimes, to be sure, I close the browser before starting VAC 3, just for to release its memory.

I don't try to use AOO and Mozilla simultaneously, because of the negative experience on my previous system (2.5 GB, HDD). 2.5 GB hasn't lasted for both, maybe due to the slow HDD.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4775
  • Karma: +99/-1
    • View Profile
Re: Hardware Compatibility Wishlist for 2022
« Reply #29 on: January 23, 2022, 01:47:04 am »
Somewhat surprising, my T42 with 1GB of ram is quite stable, takes forever to start SeaMonkey but once running, it's fine.
One thing is to set the size of the swap file as fairly large (1GB?) as growing it can cause problems.
The other day I had to reboot as cpp (the preprocessor) was dying trying to allocate 64 KB's of memory, SeaMonkey was still stable.