Date: Wed, 7 Sep 2005 12:45:40 +0200 (METDST)
From: Esben Nielsen <simlo@phys.au.dk>
To: Valdis.Kletnieks@vt.edu
Cc: "Budde, Marco" <budde@telos.de>, Jesper Juhl <jesper.juhl@gmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: kbuild & C++ 
In-Reply-To: <200509070958.j879w4p0017726@turing-police.cc.vt.edu>
Message-Id: <Pine.OSF.4.05.10509071243410.21532-100000@da410.phys.au.dk>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1084
Lines: 31

On Wed, 7 Sep 2005 Valdis.Kletnieks@vt.edu wrote:

> On Wed, 07 Sep 2005 11:13:24 +0200, "Budde, Marco" said:
> 
> > E.g. in my case the Windows source code has got more than 10 MB.
> > Nobody will convert such an amount of code from C++ to C.
> > This would take years.
> 
> Do you have any *serious* intent to drop 10 *megabytes* worth of driver
> into the kernel??? (Hint - *everything* in drivers/net/wireless *totals*
> to only 2.7M).
> 

For a special perpose embedded application, doing it all in kernel space
would be the first, effective hack. 

> A Linux device driver isn't the same thing as a Windows device driver - much of
> a Windows driver is considered "userspace" on Linux, and you're free to do that
> in C++ if you want.
> 

Yes, moving stuff to user-space would be the way to go - unless it kills
performance! 

Esben

-
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/