All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ryan C. Gordon" <icculus@icculus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 2/2] binfmt_elf: FatELF support for kernel modules.
Date: Fri, 23 Oct 2009 15:24:04 -0700	[thread overview]
Message-ID: <4AE22D04.50708@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0910200043200.18342@andre.icculuslan>

On 10/19/09 21:54, Ryan C. Gordon wrote:
> I can understand that concern, but I worry about refusing to take steps 
> that would aid free software developers in case it might help the 
> closed-source people, too.
>   

Any open source driver should be encouraged to be merged with mainline
Linux so there's no need to distribute them separately.  With the
staging/ tree, that's easier than ever.

I don't see much upside in making it "easier" to distribute binary-only
open source drivers separately.  (It wouldn't help that much, in the
end; the modules would still be compiled for some finite set of kernels,
and if the user wants to use something else they're still stuck.)

> Those that will behave badly will do so regardless of file formats, but 
> distros shipping nothing but GPL'd software and in-tree drivers would 
> benefit from this more than another misguided company that probably 
> doesn't care about multiple CPU architectures anyhow.
>   

Well, ideally a fat module would allow modules for multiple kernels to
be bundled together (same and/or different architectures), which is
primarily useful for 3rd-party binary distributions.


    J

  reply	other threads:[~2009-10-23 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:41 [RFC][PATCH 2/2] binfmt_elf: FatELF support for kernel modules Ryan C. Gordon
2009-10-20  0:12 ` Jeremy Fitzhardinge
2009-10-20  4:54   ` Ryan C. Gordon
2009-10-23 22:24     ` Jeremy Fitzhardinge [this message]
2009-10-24  0:31       ` Ryan C. Gordon
2009-10-24 11:14       ` Alan Cox
2009-10-26 19:14         ` Jeremy Fitzhardinge
2009-10-26 19:59           ` Alan Cox
2009-10-30  2:25           ` Ryan C. Gordon
2009-10-30 10:32             ` Alan Cox
2009-10-30 14:19               ` Ryan C. Gordon
2009-10-20  8:33 ` Américo Wang
2009-10-21  8:06   ` Ryan C. Gordon

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=4AE22D04.50708@goop.org \
    --to=jeremy@goop.org \
    --cc=icculus@icculus.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.