In the latest kernels, most ethernet drivers are broken.
The only drivers (wich i'm aware of) that still works are the RTL8139 and RTL8029.
This was so in all latest kernels since Serge merged the flat kernel (no offence)
I cannot find out why bu i gues it has something to do with memory map...
The stack could use a lot of improvements too.
I'm going to try to make it better, but i like to know how you guys think about how it should be...
I'll try to make external ethernet drivers first, maybe add irq support for some drivers too. (irq support for rtl8139 is practically done)
give me all your idea's
Current status of the network stack/network drivers
hidnplayr
The improvement of the network part kernel Kolibri will very good idea. This is a single part kernel, which does not develop already much long ago.
The restrictions in the manner of simultaneous access to network only 2 applications too more essential defect.
The division of the driver of the network card from kernel - good idea.
Good luck.
The improvement of the network part kernel Kolibri will very good idea. This is a single part kernel, which does not develop already much long ago.
The restrictions in the manner of simultaneous access to network only 2 applications too more essential defect.
The division of the driver of the network card from kernel - good idea.
Good luck.
I have some questions about the drivers.
As first: why can a driver only be loaded once? Is it supposed to handle multiple devices?
(for example: i have two NIC's rtl8139, but the driver may only be loaded once, so the driver must handle both cards?)
Can i unload the driver when i want to?
Can i start/stop the driver?
How does a program communicate with the driver ? (for knowing the status of the driver)
I hope somebody can help me with this....
As first: why can a driver only be loaded once? Is it supposed to handle multiple devices?
(for example: i have two NIC's rtl8139, but the driver may only be loaded once, so the driver must handle both cards?)
Can i unload the driver when i want to?
Can i start/stop the driver?
How does a program communicate with the driver ? (for knowing the status of the driver)
I hope somebody can help me with this....
Who is online
Users browsing this forum: No registered users and 37 guests