All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: jmerkey@wolfmountaingroup.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: ndiswrapper 1.54-2.6.27 released
Date: Tue, 25 Nov 2008 23:13:47 -0800	[thread overview]
Message-ID: <1227683627.3145.5.camel@LiNuX> (raw)
In-Reply-To: <46697.166.70.238.44.1227679338.squirrel@webmail.wolfmountaingroup.com>

On Tue, 2008-11-25 at 23:02 -0700, jmerkey@wolfmountaingroup.com wrote:
> 
> ndiswrapper with the 2.6.27 breakage corrected.  The current maintainers
> have not put out a release for 2.6.27 or later kernels, so I went ahead
> and fixed it for 2.6.27.
> 
> ftp://ftp.wolfmountaingroup.org/pub/ndiswrapper/ndiswrapper-1.54-2.6.27.7.tar.gz
> 
> Linux wireless drivers still do not work on most of my laptops and USB
> wireless devices due to lack of firmware drivers and other problems with
> native Linux wireless.  Anyone else with busted laptop wireless who need
> ndiswrapper might as well be able to get it since the maintainers have not
> posted recent releases for recent kernels.
> 
> 
> Jeff
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Cool; glad to see it working
with the latest kernel. 
BTW who is the author
of this patch?(this has baffled me for sometime);
http://www.slackware.com/~alien/slackbuilds/ndiswrapper/build/ndiswrapper_kernel_2.6.27.patch
(not to imped you in anyway);

regards;

-- 
Justin P. Mattock <Justinmattock@gmail.com>


  reply	other threads:[~2008-11-26  7:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  6:02 ndiswrapper 1.54-2.6.27 released jmerkey
2008-11-26  7:13 ` Justin P. Mattock [this message]
2008-11-26  7:53   ` jmerkey
2008-11-26  8:52     ` Justin P. Mattock
2008-11-27  0:03 ` Robert Hancock
2008-11-27 12:40   ` Mihai Donțu

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=1227683627.3145.5.camel@LiNuX \
    --to=justinmattock@gmail.com \
    --cc=jmerkey@wolfmountaingroup.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 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.