Message-ID: <4396FD4A.5070009@argo.co.il>
Date: Wed, 07 Dec 2005 17:18:34 +0200
From: Avi Kivity <avi@argo.co.il>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
To: Hannu Savolainen <hannu@opensound.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: Linux in a binary world... a doomsday scenario
References: <1133779953.9356.9.camel@laptopd505.fenrus.org> <20051205121851.GC2838@holomorphy.com> <20051206011844.GO28539@opteron.random> <200512061426.37287.vda@ilport.com.ua> <Pine.LNX.4.61.0512061707370.23913@zeus.compusonic.fi>
In-Reply-To: <Pine.LNX.4.61.0512061707370.23913@zeus.compusonic.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 30

Hannu Savolainen wrote:

>
>Or why not to include an embedded version of gcc/binutils in the kernel
>LKM interface. In this way all drivers can only be distributed in source 
>code which effectively makes all forms of binary only drivers impossible. 
>After that all the EXPORT_SYMBOL_GPL nonsense can be removed and a proper 
>DDI layer can be implemented for Linux. This makes it possible to ship 
>"outside the kernel build" drivers without a risk of major 
>incompatibility problems in the next kernel version. No, I'm not 100% 
>serious but just 50%.
>
>  
>
char mydriver[] = { 0x90, 0xf3, 0xa4, ... };
struct { unsigned long offset; void* symbol; } fixups[] = { { 79, 
schedule }, ... };

module_init() { link(mydriver, fixups); ((void (*)())mydriver)(); }

:)

-- 
error compiling committee.c: too many arguments to function

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/