On Sun, 2006-12-31 at 12:30 +0100, Samuel Thibault wrote:
> Hi,
>
> There's something I don't understand in
> i386/i386at/i386at_ds_routines.c:ds_notify()
>
> dev = (device_t) ns->not_header.msgh_remote_port;
>
> How a port can be a device_t?
A device_t is just a mach_port_t that is expec
On Sun, Dec 31, 2006 at 05:33:21PM +0100, Samuel Thibault wrote:
> Well, I actually don't know much details about mach ports :)
>
> More specifically, I'm talking about an ipc_port_t, as used for instance
> in linux/dev/glue/block.c in device_open()
>
> bd->port = ipc_port_alloc_kernel ();
>
>
Richard Braun, le Sun 31 Dec 2006 17:11:55 +0100, a écrit :
> On Sun, Dec 31, 2006 at 12:30:24PM +0100, Samuel Thibault wrote:
> > There's something I don't understand in
> > i386/i386at/i386at_ds_routines.c:ds_notify()
> >
> > dev = (device_t) ns->not_header.msgh_remote_port;
> >
> > How a
On Sun, Dec 31, 2006 at 12:30:24PM +0100, Samuel Thibault wrote:
> There's something I don't understand in
> i386/i386at/i386at_ds_routines.c:ds_notify()
>
> dev = (device_t) ns->not_header.msgh_remote_port;
>
> How a port can be a device_t?
In include/mach/message.h:
typedef struct {
.
Hi,
There's something I don't understand in
i386/i386at/i386at_ds_routines.c:ds_notify()
dev = (device_t) ns->not_header.msgh_remote_port;
How a port can be a device_t?
And when looking at device drivers, what is put here is really a port,
not a device_t...
Samuel
_
