linux-kernel - Re: [PATCH] Backport of Sierra Wireless USB serial driver from 2.6 to kernel 2.4.37

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 19 Jan 2010 20:41:59 +0100
From:	David Holm <dholmster@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux@...rrawireless.com, klloyd@...rrawireless.com
Subject: Re: [PATCH] Backport of Sierra Wireless USB serial driver from 2.6 to 
	kernel 2.4.37

On Tue, Jan 19, 2010 at 8:26 PM, Greg KH <greg@...ah.com> wrote:
[snip]

> Minor complaint, your email client wrapped the patch, so it would have
> to be edited by hand in order to apply it.

I made it available on my webserver, if nothing else for posterity.
http://www.dholm.com/files/sierra-2.4_1.7.16-1.patch

> Main question though is, why did you do this?  Is there some reason you
> are stuck with such an old, and unsupported kernel version that you
> required this driver?  What is keeping you from moving to a 2.6 kernel
> on this hardware platform, and can we help you out with that in any way?

The platform we are working on is no longer supported by the vendor
(which I would prefer not to name) and they only supplied GCC 2.95.3
(with a coupld of ARM-specific patches) and a choice between Linux
2.4.22 or 2.4.26. On a couple of occasions I made some half-assed
attempts at upgrading GCC to 3.x and 4.x using vanilla releases but I
could never get them to produce stable binaries.

If I had more time I would do the work but since I'm the only one who
knows the low level stuff like the back of my hand I rarely have any
time to spare on such a project. As it stands we are getting by on the
toolchain we have and there have only been a few roadblocks along the
way which have since been removed.

> Otherwise, looks fine at first glance, but I don't know what to do with
> the patch as no one is doing 2.4 work upstream anymore except for
> security and other minor bugfixes.

I was afraid of that but posted it anyway hoping someone forced to
work in a similar environment as us to find it useful.

Thanks for getting back to me so fast. Hopefully I will be able to
work on never kernels in the not so distant future and come up with
more interesting patches. :)

Sincerely,
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/