Kernel: Choosing the correct Network Drivers

[kkarhan]

As for the "CORE" Version of OS/1337, basic Ethernet [TCP / IPv4] will be necessary to have some basic connectivity and being able to run stuff like wget / [tiny] curl, dropbear [SSH] client (aka. dbclient) and maybe even a fully-featured dropbear or lynx as browser.

It'll also be used to "install" bigger "Editions" by downloading an image file, holding it in ramdisk and then DD'ing it onto a drive.

AFAICT, the most common for any "retro" / old machines are:

• 3Com
• AMD [PCnet / PC-FAST]
• Intel [also being used in VMs]
• VIA ["Rhine" NICs are common in Thin-Clients based off VIA C3/C7 Chips].

It's vital to keep the kernel as small as possible.

• We can pretty much deduct all NICs that ain't ISA and/or PCI connected tho...
  • espechally PCIe, USB and/or multi-GBit - NICs.

[kkarhan]

This is intertwined with #6

[kkarhan]

As of now I'm considering to yeet all but integrated and ISA-based NICs to save space and only leave 3com, AMD, Intel and VIA NICs in that are integrated into the Chipset/SoC or connected via ISA.

PCI, PCIe and CardBus support had to be sacrificed as per issue #6...

[kkarhan]

This created the following issues:

• BUG: no detection of network interfaces and/or cards in VirtualBox #13
• BUG: Kernel: socket driver missing #15

[kkarhan]

I am confident that my current selection is a good balance given the expected hardware and the space constraints - tho I'd be willing to change those if need be.

ISA & PCI Ethernet NICs
-> 3Com
-> AMD
-> Intel
-> VIA

[kkarhan]

Problem as of now: Kernel Size is at ~ 1,15MB (!!!)
Need to slim that down

• see Kernel: Minimize size of bzImage [kernel] file #6

[kkarhan]

As per #13 I can't do more...
#13