Hi,
Björn Döbel wrote:
I won't apply this patch to ORe, though, exactly because we don't want to mess with the imported drivers.
I agree. That makes good sense.
There is another workaround for the issue. I've just discovered it here http://www.nabble.com/Possible-bug-in-e1000-driver-from-ORe-package-td223096.... If you use it you don't have to change original driver.
When you'd like to use ORe from L4Linux with Intel e1000 series NIC you can circumvent the problem with stub driver wrong IRQ requested by giving additional options to L4Linux command line (this cmd line is in .cfg file that you load by grub). Like these one: "l4ore.oredev=DEV l4ore.irqnum=IRQ", where DEV is attached device name discovered by ORe (e.g. lo, eth0, eth1 and so on) and IRQ is irq number assigned by BIOS to this particular DEV (BIOS usually prints irq assignment during boot). E.g. in my case I could add to command line: "l4ore.oredev=eth0 l4ore.irqnum=11" Effectively these options force the stub driver to override device name and irq returned by ORe server with specified one.
I didn't try it by myself but judging from ORe stub driver source code it should work.
Regards, Alexander Valitov