mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ryan C. Gordon" <icculus@icculus.org>
To: Jeremy Fitzhardinge <jeremy@goop.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 20:31:16 -0400 (EDT)	[thread overview]
Message-ID: <alpine.OSX.1.10.0910232026080.2186@caridad.icculuslan> (raw)
In-Reply-To: <4AE22D04.50708@goop.org>



On Fri, 23 Oct 2009, Jeremy Fitzhardinge wrote:

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

Yes, absolutely. I agree.

But even for mainline drivers, there's a compelling use-case for this, 
even for a Linux distribution that's 100% Free Software.

Those that want to play outside the sandbox still have all the misery of 
having to keep up with kernel interface changes and supporting multiple 
kernel releases. That's the hard part for them, and I'm happy to continue 
to make it uncomfortable in that regard. How the kernel module gets loaded 
is probably not of great importance compared to the engineering resources 
they probably devote to just keeping up.

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

If the OSABI version doesn't change, they can't use FatELF to pack 
together multiple drivers for different kernel versions. fatelf-glue 
refuses to merge them, and the kernel will pick the first one, and if it 
fails to load, tough luck.

I think this should resolve the concern from a technical standpoint. They 
still have the same problems.

--ryan.


  reply	other threads:[~2009-10-24  0:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:41 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
2009-10-24  0:31       ` Ryan C. Gordon [this message]
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=alpine.OSX.1.10.0910232026080.2186@caridad.icculuslan \
    --to=icculus@icculus.org \
    --cc=jeremy@goop.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 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®