Re: File I/O in the kernel.
Re: File I/O in the kernel.
- Subject: Re: File I/O in the kernel.
- From: Dean Reece <email@hidden>
- Date: Wed, 24 May 2006 13:11:08 -0700
On May 24, 2006, at 12:32, Andrew Gallatin wrote:
Michael Smith writes:
On May 24, 2006, at 11:52 AM, Andrew Gallatin wrote:
Terry Lambert writes:
If you need to do file I/O to load firmware (as an example),
either put the firmware in a discardable section (vm_deallocate
() it after it's loaded in the card), or have a user space
daemon communicate the firmware to your driver via a series of
ioctl() calls to push the data *temporarily* into the kernel, so
it doesn't take up real or virtual memory in your driver.
This comes up over, and over, and over again here. Is there any
chance Apple can provide a centralized way to do this in the OS,
Yes. It's called a user-space process.
OK, what you mean is that it is called N user space process, a
different one for each driver, all re-inventing the same wheel with
different bugs.
Right - this request has come up several times, and I think it is
perfectly reasonable. Adding a KPI that allows a kext to read a file
from within it's bundle for the purposes of downloading firmware is
something we have considered, and will probably do at some point.
For anybody that cares, this enhancement request is being tracked
internally by Radar# 4487388 "Need KPI to read a file out of a kext
bundle (firmware download)"
This is not the same problem as general file I/O (which I don't think
kexts should be doing), nor is it the problem the original poster was
asking about...
- Dean
_______________________________________________
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