mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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++
Date: Wed, 7 Sep 2005 12:45:40 +0200 (METDST)	[thread overview]
Message-ID: <Pine.OSF.4.05.10509071243410.21532-100000@da410.phys.au.dk> (raw)
In-Reply-To: <200509070958.j879w4p0017726@turing-police.cc.vt.edu>

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


  reply	other threads:[~2005-09-07 10:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07  9:13 Budde, Marco
2005-09-07  9:57 ` Valdis.Kletnieks
2005-09-07 10:45   ` Esben Nielsen [this message]
2005-09-07 10:00 ` Bernd Petrovitsch
  -- strict thread matches above, loose matches on Subject: below --
2005-09-15 12:35 Budde, Marco
2005-09-18 18:41 ` Sam Ravnborg
2005-09-07 12:04 Budde, Marco
2005-09-07 12:58 ` Bernd Petrovitsch
2005-09-07 13:15 ` Nick Piggin
     [not found] <4JJOt-77X-9@gated-at.bofh.it>
2005-09-07 12:02 ` Bodo Eggert
2005-09-07 10:17 Budde, Marco
2005-09-07 18:52 ` Lee Revell
2005-09-06 11:23 Budde, Marco
2005-09-06 11:30 ` Bernd Petrovitsch
2005-09-06 21:08   ` Chris Frey
2005-09-07  6:39     ` Bernd Petrovitsch
2005-09-06 11:38 ` linux-os (Dick Johnson)
2005-09-06 21:20 ` Jesper Juhl
2005-09-06 22:20   ` Esben Nielsen
2005-09-06 22:22     ` Randy.Dunlap
2005-09-06 22:32     ` Jesper Juhl
2005-09-07  2:33     ` Valdis.Kletnieks
2005-09-07  9:21       ` Esben Nielsen
2005-09-07 10:11         ` Valdis.Kletnieks
2005-09-07 10:58           ` Esben Nielsen
2005-09-07 11:44         ` Bernd Petrovitsch
2005-09-06 21:41 ` Sam Ravnborg
2005-09-10 12:29 ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.OSF.4.05.10509071243410.21532-100000@da410.phys.au.dk \
    --to=simlo@phys.au.dk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=budde@telos.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®