On Tue, Aug 22, 2006 at 04:05:30PM +0300, Constantine Kousoulos wrote:
> Ok. So there are as many device_xxx() routines as the types of
> drivers that mach supports.
>
> How does mach choose the correct device_xxx() routine from the
> many available? Let's say that mach needs to acces the floppy
O/H Richard Braun έγραψε:
Actually, there is only one interface, the device_xxx() routines...
Ok. So there are as many device_xxx() routines as the types of
drivers that mach supports.
How does mach choose the correct device_xxx() routine from the
many available? Let's say that mach needs t
On Tue, Aug 22, 2006 at 01:49:01PM +0300, Constantine Kousoulos wrote:
> Hello,
>
> As it seems, mach has a "dual" device interface. Firstly, there
> is the native device interface (device_open, device_close etc).
> Secondly, there is the linux emulation device interface (again
> device_open, devi
Hello,
As it seems, mach has a "dual" device interface. Firstly, there
is the native device interface (device_open, device_close etc).
Secondly, there is the linux emulation device interface (again
device_open, device_close, etc in seperate files) that glues linux
drivers with mach.
How does mac
On Fri, Aug 18, 2006 at 05:07:16PM +0200, Samuel Thibault wrote:
> Hi,
>
> Richard Braun, le Mon 14 Aug 2006 22:55:15 +0200, a écrit :
> > extern struct task_struct *current_set[NR_CPUS];
> > #define current (0+current_set[smp_processor_id()]) /* Current on this
> > processor */
> > The symbo
