Re: [PATCH] make NatFeat drivers bool, not tristate

[Thorsten Glaser <tg@mirbsd.de>]

Thorsten Glaser <tg <at> mirbsd.de> writes:

> Andreas Schwab dixit:
> 
> >The problem is that aranym expects the parameters of the natfeat calls
> >to be physical addresses.  The nf_get_id calls use literal strings as
> >parameters which only works when the drivers are builtin because phys ==
> >virt then.
> 
> Ah, right, there was that issue… so this patch should probably go in?

At first, anyway.

Maybe if CONFIG_NATFEAT is selected (it’s bool), some bounce buffer could
be allocated and memlocked, which the other NF* drivers can then use.
(If NatFeat is not found during boot, no memory should be allocated.)

Especially if we had more NF* drivers in the future (hostfs could be made
into something, maybe with something like umsdos on top for Unix file
permissions? And I’m hoping for a bidirectional “virtio/serial” console…)
this could be useful sharing, and not needing to have everything else
in the kernel statically.

Well, if someone has time and wants to write this.

bye,
//mirabilos