What hardware does your OS support?

[glauxosdever]

Hi,


Based on a recent idea, I initiate this topic. It would be nice if moderators could make it sticky.

Let me start:

• My first kernel (the one in assembly) had poor support for EHCI. ATA/AHCI were attempted, although they never went far.
• My second kernel (the one in C) had almost full PS/2 support. Most things supported in the first kernel were not supported here.
• My third kernel is actually still in design phase, but I predict it will most likely be a microkernel, so it can support as much hardware as possible without me intervening.

So, what is your hardware support?


Regards,
glauxosdever

[Octacone]

Basic OS: Second Revision (Current Version)

32-Bit i386 Processors
Keyboard Support + 2 Keyboard Layouts
Mouse Support
BIOS Compatible
Up To 4GiB Of RAM
Default 80x25 Fully Working Shell
"BGA" Graphics Mode + Any Given Resolution
Compatible BIOS Font
Uses GRUB 2
PIT

"Basic OS" is a name of my Operating System.

[BrightLight]

xOS supports:

• 32-bit x86 CPUs (and soon 64-bit).
• PS/2 keyboard and mouse.
• VESA BIOS Extensions, entirely resolution independent.
• ATA read-only driver, write access coming soon.
• PCI scanning (by vendors/devices and class).
• ACPI shutdown.
• Cooperative multitasking.

I have implemented as well, but not in xOS, drivers for VGA, I/O APIC, local APIC, SMP, BGA, PCI Express and ACPI reset.

[heat]

Spartix currently supports:

• x86_64 CPUs
• PS/2 Keyboards
• ATA Drives
• PCI
• VESA Graphics Modes
• 8259 PIC
• PIT

I'll implement AHCI and RTC soon, but I'm focusing on user-space/VFS changes right now.

[Ch4ozz]

My OS (x86 only) supports:

• Bios calls via realmode switch
• CMOS and PIT (mainly used for timers)
• PS/2
• PCI
• Full AHCI SATA support (HDD, CDROM, ..)
• VESA (Full working window manager)
• EDID
• AC97 (Mid working audio server)
• AMD PCNet Fast III (Full working Networkstack)
• ACPI
• SSE/MMX

[glauxosdever]

Hi,

AMD PCNet Fast III (Full working Networkstack)

AC97 (Mid working audio server)

Full AHCI SATA support (HDD, CDROM, ..)

That's some nice hardware to support.

However, it seems several have also listed basic hardware in their hardware support list. I could populate my list further; PIC and PIT are also supported.


Regards,
glauxosdever

[shmx]

Old kernel (С):
CPU: PM32, paging, multitasking, v86
System: PIT, PIC, PCI, CMOS
Storage: IDE (Compatible, Enhanced mode, only HDD), AHCI, USB mass storag class (not fully), FDD
Video: VBE, Hardware cursor (only some Amd, Intel), video mode switching (R600 - R700 family), experimental 2D accel (old Radeons < R600, Intel)
USB Host: UHCI, EHCI (only bulk transactions)
Keyboard/Mouse: PS/2, USB
Sound: AC97 VT82XX, ESS3, HDA (no compatibility for all codecs)

New kernel (С++):
CPU: PM32, SMP, paging, multitasking, LAPIC
System: IOAPIC, PIC, HPET, ACPI (not fully)
Video: VBE
Time not enough

[tsdnz]

Hi, my Cloud Operating environment has multiple OSes:

Basic OS support:

• x64
• 255 cores, although only allowing 64, for best performance is 16 cores
• Unlimited memory
• Unlimited storage (To be designed)
• SSE
• AVX
• SAS
• SATA
• Maximum 16 x 10GB NIC
• 4,096 to 16,384 ticks per second per core
• Maximum 32,768 threads per core
• Maximum 40 million TX + 40 million RX @ 64 byte NIC packets, have to drop this down to 30 million RX + 30 million TX as the PCIe load is bias towards the RX, looks like NIC internals
• User-space processing around 7 million packets per core

Overall design support:

• 65,536 servers per data-centre
• 65,536 data-centres
• Distributed storage (to be designed)
• Distributed cores
• Distributed memory (to be designed)
• Maximum 4,187,904 cores per data center
• Maximum 100 million accounts
• Unlimited Apps/Programs

[max]

Heyho,

mine features:

• x86 processors
• multicore via SMP
• BIOS via VM8086 monitor
• SSE/SSE2/MMX
• PS/2 Mouse & Keyboard
• VESA
• ACPI
• GRUB2
• naturally core system things like PIC/PIT/IOAPIC

I don't focus too much on supporting a wide variety of hardware because I want to make something usable first.

Greets

[Kevin]

tyndur has all of the CDI drivers and some additional old drivers that have never been ported, plus of course the usual core stuff in the kernel. Which means in detail:

• i386 CPUs
• PIC, PIT, CMOS, PCI
• PS/2 keyboard and mouse
• ISA DMA
• Storage: IDE, AHCI, Floppy
• File systems: ext2, FAT, iso9660
• Network: e1000, ne2k, pcnet, rtl8139, rtl8168b, sis900
• Sound: AC97, hdaudio
• Serial port
• VESA (using VM86)
• A little bit of UHCI and USB-MSD

[wichtounet]

Hi

Thor OS support:

• x86_64 CPU
• PS/2 Keyboard / Mouse
• PCI (basic)
• RTL8163 network card
• ATA (read/write)
• RTC / PIT / HPET
• ACPI (via ACPICA)
• Serial (only for Qemu debugging)
• VESA (not really hardware)

[sleephacker]

Lithik currently supports:

• x86 CPUs (except some really old ones)
  PS/2 (but very limited)
  VGA
  VBE/VESA (any mode with at least 8bpp)
  Multithreading (funtional, but not complete)
  8254x network cards
  Floppy Disk Controller
  FAT12 (Except for one critical feature: file loading)

It also "supports" a few features of some other things like PCI, PIC, DMA, but only in a very limited way.
Writing this made me realize how many things in my OS still need work, "TODO" shows up 81 times in the code...

[mariuszp]

Glidix so far supports only the x86_64 architecture (and I'm not seriously planning porting it to anything else). The hardware supported is:

[*]Basic hardware: PCI, VGA text mode, PIT, APIC (including timer). This is implmeneted in the kernel itself; all the things below are implemented as separate modules.
[*]Storage devices: IDE and AHCI; with AHCI being limited to ATA only (no ATAPI support yet).
[*]Graphics: BGA (not actually real hardware)
[*]Input devices: PS/2 mouse and keyboard
[*]Ethernet cards: NE2000, Intel 8254x (only PRO/1000 MT Desktop is listed in the driver as supported but it'd probably work for the other ones too), and broken support for VirtIO net (i probably will NOT fix that )

So not bad so far

[onlyonemac]

Mine supports hardly any hardware. It's goal is not to support the widest possible range of hardware, but to provide a from-the-ground-up object-oriented and modular design. Drivers will be written as userspace functions/libraries just like anything else (except storage device drivers which are still, nevertheless, self-contained modules that can easily be added later).

[BrightLight]

Let's add something to my hardware support list. I've recently added native support for SATA drives using AHCI.
Up next is HPET and some other modern stuff, but I'll implement a file system first and implement loading programs from disk.