runtime kernel modules are plain kernel modules. the runtime particle is
added as an emphasis on the fact that they can be load/unload during
kernel runtime and not at boot.
cristi
At 05:55 PM 6/14/00 +0200, you wrote:
On Tue, 13 Jun 2000, Cristi wrote:
That is what I was actualy
He, I don't want any assembler code for this.
Of course I use gcc for this 8-bit micro controller. There is a
gcc port for the Atmel AVR which is now in the main stream. So you can
use the gcc-2.95.2 snapshot after 2000-05-01 .
Also gdb-4.18 exist for that target (quite in development).
I
That is what I was actualy reffering to. I see even the network adapter
drivers being implemented as kernel modules. of course if the kernel
load/unload module mechanism would take more than the actual driver the
solution is to have different kernels compiled for the particular
hardware.
I would rather wait for a solid kernel and then add networking. I think
networking should be a module as you don't need networking everywhere.
Biulding it modular you can deal with limited resources.
cristi
At 10:20 PM 6/12/00 -0400, Gregg C Levine wrote:
Hello from Gregg C Levine usually
On Tue, 13 Jun 2000, Cristi wrote:
I would rather wait for a solid kernel and then add networking. I think
networking should be a module as you don't need networking everywhere.
Biulding it modular you can deal with limited resources.
I think the origional plan was to have a user
Luke Farrar wrote:
On Tue, 13 Jun 2000, Cristi wrote:
I would rather wait for a solid kernel and then add networking. I think
networking should be a module as you don't need networking everywhere.
Biulding it modular you can deal with limited resources.
I think the origional
e 13, 2000 4:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Adding networking to the ELKS basic install kit
On 2000-06-12 [EMAIL PROTECTED] said to [EMAIL PROTECTED]
Hello from Gregg C Levine usually with Jedi Knight Computers
Just out of curiosity, has someone come up with the idea for
