mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: crash77a@allvantage.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Converting kernel modules from 2.4 to 2.6/Suggested new driver
Date: Tue, 5 Oct 2004 18:27:16 -0700	[thread overview]
Message-ID: <20041005182716.2f3f52c0.rddunlap@osdl.org> (raw)
In-Reply-To: <416345C0.4050500@allvantage.com>

On Tue, 05 Oct 2004 21:09:20 -0400 Kenny Bentley wrote:

| Hello.
| 
| Does anyone know if there is a detailed guide on how to convert kernel 
| modules for 2.4 kernels to modules for 2.6 kernels?  I know very little 
| about kernel module programming and haven't done any programming for a 
| long time, although I do have a programming background, and I have 
| drivers for HSF modems and Riptide sound cards that I want to convert 
| from 2.4 modules to 2.6 modules, which shouldn't be too hard.  But I'll 
| need a detailed guide to do it.

http://lwn.net/Articles/driver-porting/

| Or since I've never done any kernel programming, I have a better idea.  
| I want to recommend the drivers for inclusion into the official kernel 
| tree.  The drivers were released open-source by Linuxant or the 
| manufacturer, I don't remember which one for sure.  But they're not 
| being developed any further, and the Riptide sound card driver only 
| supports OSS, and doesn't support ALSA.  Also, there are things in the 

OSS is deprecated.  It needs an ALSA driver.

| drivers that need fixing that surely a lot of you can do much better 
| than me.  I can help test the revised modules and I know how to put them 
| in the kernel tree, so I can do those parts.  But many of you can do the 
| programming better than I can.

You can recommend them for inclusion, but the developer or maintainer
of them needs to either submit them or at least approve their
submission for inclusion.

| I can't afford new hardware right now, and I had to search the net for 
| hours and maybe even days just to find these drivers, and almost gave up 
| hope of being able to use GNU/Linux as my primary OS.  I wouldn't want 
| others to have to go through that or settle for mediocre drivers.  If 
| there are any takers out there, just send me an E-mail and I'll send you 
| the drivers so you can hack away.  But at the very least I'd like to 
| know where I can find a detailed guild on how to convert kernel modules 
| from 2.4 to 2.6.

How about posting their web locations (wherever you found them)
in case someone is interested..?

--
~Randy

  reply	other threads:[~2004-10-06  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06  1:09 Kenny Bentley
2004-10-06  1:27 ` Randy.Dunlap [this message]
2004-10-06  1:53   ` J. Bruce Fields
2004-10-06  4:13     ` Kenny Bentley
2004-10-06  2:19   ` Lee Revell
2004-10-06  4:02   ` Kenny Bentley
2004-10-06 12:51     ` John Carlson

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=20041005182716.2f3f52c0.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=crash77a@allvantage.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®