Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- Subject: Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- From: Karunakar Reddy G <email@hidden>
- Date: Tue, 9 Aug 2005 14:29:51 +0530
Thank you Andrew, Terry.
Can you give some example how to use of them, as I am facing problem using structures,
In my case structure pointer comes from the application to driver , previously I handled using void *.
How to handle now since I cannot convet them as user_addr_t to use for copyin() and copyout() functions.
Regards,
Karunakar
If you are using copyin()/copyout()/copyinstr() directly, rather than
using uiomove()/uiomove64(), then you will need to make changes to
your code.
The reason for the change to the parameters was to support copying in/
out data with 64 bit user space addresses for 64 bit processes.
Without the change, you would be limited to only passing data from
the first 4G of process memory into the kernel when using a 64 bit
process, and that wouldn't really be useful.
-- Terry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden