[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: oskit-mach: device_write
From: |
Roland McGrath |
Subject: |
Re: oskit-mach: device_write |
Date: |
Fri, 8 Mar 2002 04:12:50 -0500 (EST) |
> ds_net_write_inband makes first a sanity check for the given paramenters.
> If this fails it just returns without setting bytes_written to 0.
That is as it should be. I thought you were talking about a successful call.
The out parameters are not examined when the return value is nonzero,
so it is correct to leave them unset.
> I'm still trying to figure out what I see:
-305 is MIG_NO_REPLY. This is what it should be with the ds_routines.c
change I put in to fix the original bug you found. The stub is behaving
fine. The reply message should already have been sent by the
ds_device_write_error_reply call in ds_device_write. What is the actual
failure mode now?
- oskit-mach: device_write, Daniel Wagner, 2002/03/02
- Re: oskit-mach: device_write, Daniel Wagner, 2002/03/03
- Re: oskit-mach: device_write, Roland McGrath, 2002/03/04
- Re: oskit-mach: device_write, Roland McGrath, 2002/03/04
- Re: oskit-mach: device_write, Roland McGrath, 2002/03/04
- Re: oskit-mach: device_write, Daniel Wagner, 2002/03/05
- Re: oskit-mach: device_write, Roland McGrath, 2002/03/05
- Re: oskit-mach: device_write, Daniel Wagner, 2002/03/06
- Re: oskit-mach: device_write, Roland McGrath, 2002/03/06
- Re: oskit-mach: device_write, Daniel Wagner, 2002/03/07
- Re: oskit-mach: device_write,
Roland McGrath <=
- Re: oskit-mach: device_write, Daniel Wagner, 2002/03/09
- Re: oskit-mach: device_write, Thomas Bushnell, BSG, 2002/03/10