Re: New driver loading scheme for Project Evil, need input

From: Vladimir Grebenschikov <vova_at_fbsd.ru>
Date: Wed, 20 Apr 2005 12:45:36 +0400
В ср, 20/04/2005 в 05:22 +0000, Bill Paul пишет:
> > > You still end up needing the C compiler, objcopy, ndiscvt and (optionally)
> > > iconv, but the script automates the use of all these tooks and explains
> > > to the user what's going on while it's working.
> > 
> > It's certainly simpler than the current state of afairs and unless the kernel 
> > NDIS grows the ability to directly read .sys & .inf files from your disk 
> > (which would be very cool :) it's about a simple as it's going to get..
> 
> Putting a .INF parser in the kernel would not be cool at all. Kernels
> are for managing hardware and herding applications, not parsing text
> files.

Probably any parsing should be done in user-space utility, which will
load .SYS file into kernel.

# ndisload w22n51.inf w22n51.sys

It should parse .inf, load if_ndis/ndis if required and then supply them
binary data to use (via sysctl interface or like)

This can be alternative way (instead of compiling special .ko)
It is not so useful for mass-deploying, but more useful for day-to-day
life.

What do you think ? 

> -Bill

-- 
Vladimir B. Grebenchikov
vova_at_fbsd.ru
Received on Wed Apr 20 2005 - 06:45:40 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:32 UTC