From: Greg KH <gregkh@suse.de>
To: Alexander Huemer <alexander.huemer@sbg.ac.at>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: removal of strip driver from the linux kernel
Date: Thu, 7 Jan 2010 10:09:42 -0800 [thread overview]
Message-ID: <20100107180942.GA17642@suse.de> (raw)
In-Reply-To: <4B45E5B1.2040901@sbg.ac.at>
On Thu, Jan 07, 2010 at 02:46:25PM +0100, Alexander Huemer wrote:
> hi,
>
> i read in your blog that the driver "strip" for the metricom radios is
> going to be removed from the linux kernel.
> as you suggested, i am "speaking up" now, because i am using the driver.
> the driver should not be removed and could even be improved, actually
> in a very significant way.
> the current version (1.3) does not work for the last hardware revision
> of the radios which were the ones circulated in larger quantities.
> that may be the reason why the driver does (or did) have a quite small
> user base.
> these radios are available on eBay from time to time, very cheap.
> the difference in the hardware is mostly a different length of the
> hardware address.
>
> there is already a patch and documentation from alex belitis [1] for
> that, for linux-2.4.1. i also found a different patch [2] that might
> be of interest, for 2.5.46.
Are you able to refresh these patches for the latest kernel version and
send them to me so that we can help bring the code up-to-date?
> since the driver is quite small and the starmode concept is quite
> unique in wireless networking, i am planning to do some academic work
> on the concept during an OS and networking class at the university of
> salzburg.
> i am not (yet) an experienced kernel programmer and because of that
> have problems porting the patch from alex belitis to the current
> kernel versions. who could help me with this ?
What problems are you having?
> the git log lists a lot people plumbing on strip.c, so i am unsure
> whom to contact.
The linux-wireless mailing list (on the CC:), and the driverdevel list
are the best ones.
Anyone want to help out here?
> [1] http://phobos.illtel.denver.co.us/~abelits/metricom/
> [2] http://www.stillhq.com/linux/patches/2.5.46/cli_sti_removal-001
thanks,
greg k-h
parent reply other threads:[~2010-01-07 18:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4B45E5B1.2040901@sbg.ac.at>]
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=20100107180942.GA17642@suse.de \
--to=gregkh@suse.de \
--cc=alexander.huemer@sbg.ac.at \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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;
as well as URLs for NNTP newsgroup(s).