All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: Ray Wells <mvc@midcoast.com.au>
Cc: linux-hams@vger.kernel.org
Subject: Re: 6PACK - Another question
Date: Wed, 2 Nov 2005 09:13:57 +0000	[thread overview]
Message-ID: <20051102091357.GA2703@linux-mips.org> (raw)
In-Reply-To: <4368510E.7090006@midcoast.com.au>

On Wed, Nov 02, 2005 at 04:39:26PM +1100, Ray Wells wrote:

> In the documentation /.../6pack.txt, the author says the driver has only 
> been tested as a module and not built-in to the kernel.
> 
> Has anyone on this list used the 6pack driver in the built-in version 
> with kernel 2.2.20?

Linux 2.2, that's extremly old - ages from before I took over it's
maintainership.  But the code actually looks okay.  Sure you don't want
to upgrade to a piece of software from this decade?

> I always opt for built-in drivers for stuff I know I'll use and maybe 
> this has been my downfall in this case :-(

For custom kernels that will save a tiny amount of memory and give a small,
almost unmeassurable performance gain.  You lose the advantage of for
example being able to re-initialize a subsystem by unloading and reloading
it's module.

Given all that what learned about problems with the 2.2 module loader we
can probably declare it a buggy horror trip from today's perspective.

> No drama, of course, to recompile the kernel with the driver as a module 
> but I may as well test the waters first :-)

The 2.2 6pack driver looks ok, certainly up to the standards of those days
and I wouldn't expect any problems with it from linking it.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21

  reply	other threads:[~2005-11-02  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02  5:39 6PACK - Another question Ray Wells
2005-11-02  9:13 ` Ralf Baechle DL5RB [this message]
2005-11-03  2:54   ` Ray Wells

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=20051102091357.GA2703@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=mvc@midcoast.com.au \
    /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.