On Sun, 1 May 2005, Mike Smith wrote:
>
> On Apr 30, 2005, at 6:57 AM, John Dalgliesh wrote:
>
> > Excellent, thankyou. I should have just tried passing in NULL! I've
> > now
> > got my firmware-file-reading code working again - once I realised
> > that the
> > vnode lock shouldn't be taken when doing a read - and released a new
> > version of my driver package.
>
> Please don't do this. Load your firmware as part of the kext and
> then drop it,
> or load it with a startup item, but please don't make any assumptions
> about
> the state of the filesystem inside your kext.
So KUNCExecute is out too? It uses the filesystem. This just gets better
and better.
> This conversation contains far too much deja-vu.
Maybe that is because there isn't a good solution to it yet? I know that
on linux, drivers only stopped reading files in the kernel when the
hotplug system was introduced.
Actually, I always thought I was doing the right thing by not tying down
wired pages with rarely-used firmware data.
And I was only using APIs in ways that other parts of the kernel were.
The other thread describes why I can't compile it into a kext (no
permission from copyright owner) and why a startup item is inappropriate
(PCMCIA cards; also PCI cards only activated/initialised on demand).
> = Mike
{P^/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-drivers/email@hidden
This email sent to email@hidden
