--l+goss899txtYvYf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 24, 2006 at 10:42:46AM +0100, Filka Michal wrote:
> Yes, this seems like thing I was looking for.=20
>=20
> I have one more question. The last parameter of NDINIT is described as
> "the calling process.". However, if I call it from my driver I needn't
> to be in any process context ... So, is NULL allowed or should I use any
> "kernel process identifier"?

I'd recommend not doing it that way. I think you'll do better to either
move to a newer version of NetBSD, back-port the firmware(9) changes to
your version, or write a little program to call an ioctl on your driver
that does the load. You can have the program open the file and then either=
=20
pass the file descriptor into the kernel or read the firmware and pass the=
=20
address of the memory into the kernel.

It's a lot easier to change the file name if you pass it to a program than=
=20
if it's hard-coded in the kernel. :-)

Take care,

Bill

--l+goss899txtYvYf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFEJKaKWz+3JHUci9cRAmj7AJ9JosniK72w6RPwZ/3KnUUtutffwgCghRN7
XoYP+ELopuF9Jiekh4YQl3I=
=2U6u
-----END PGP SIGNATURE-----

--l+goss899txtYvYf--