Date: Wed, 20 Apr 2005 12:45:36 +0400 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Bill Paul <wpaul@FreeBSD.ORG> Cc: freebsd-current@freebsd.org Subject: Re: New driver loading scheme for Project Evil, need input Message-ID: <1113986736.1162.6.camel@localhost> In-Reply-To: <20050420052240.7EFAD16A4CF@hub.freebsd.org> References: <20050420052240.7EFAD16A4CF@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D3=D2, 20/04/2005 =D7 05:22 +0000, Bill Paul =D0=C9=DB=C5=D4: > > > You still end up needing the C compiler, objcopy, ndiscvt and (option= ally) > > > iconv, but the script automates the use of all these tooks and explai= ns > > > to the user what's going on while it's working. > >=20 > > It's certainly simpler than the current state of afairs and unless the = kernel=20 > > NDIS grows the ability to directly read .sys & .inf files from your dis= k=20 > > (which would be very cool :) it's about a simple as it's going to get.. >=20 > 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 ?=20 > -Bill --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1113986736.1162.6.camel>