|
Yes, I already checked compat-wireless
project.
However, as you see from their page, they support
down to 2.6.24. As you remember from my 1st post, my kernel version is
2.6.12.5
I also have RALINK and Realtek sources, however
they also need the kernel source tree to compile their modules, and my current
kernel also does not have enough header files to compile their source ( at least
ralink)
But anyway, I will try to find a way to communicate
with these people, and lets see if they can do a favour for a very old kernel (
2.6.12.5).
Thank you again.
----- Original Message -----
Sent: Sunday, June 10, 2012 5:52 AM
Subject: Re: New kernel for Chipbox
That is better approach.
u can try compat-wireless. It supports wide
range of kernel version. What wifi are u using, ralink or others? Each wifi
has source, u can compile against ur kernel to build module. U need to enable
wireless support in ur kernel.
On 10 Jun 2012 00:36, "Sertac TULLUK" < sertac@xxxxxxxxxxxxxxxxx>
wrote:
Dear Javier,
Sorry for late reply, but thank
you.
I also searched for many things on the net, read a lot of
documentation, but it seems almost impossible thing to do... (That is shame,
where is the power of linux? :) Just kidding )
Is there any way to do
backporting ? For example, adding CIFS or USB WIFI support to my current
kernel?
If so, what are the steps for it?
Best
Regards
Sertac
----- Original Message ----- From: "Javier
Martinez Canillas" <martinez.javier@xxxxxxxxx>
To: "Sertac TULLUK"
<sertac@xxxxxxxxxxxxxxxxx>
Cc: "Harishkumar V" <harishpresent@xxxxxxxxx>; <kernelnewbies@kernelnewbies.org>
Sent:
Friday, June 08, 2012 3:16 PM
Subject: Re: New kernel for
Chipbox
On Thu, Jun 7, 2012 at 1:53 PM, Sertac TULLUK <sertac@xxxxxxxxxxxxxxxxx> wrote:
Dear Harishkumar;
I already know how to find
the changes, please see my 1st e-mail below.
The problem is,
those changes are more than thousands of lines of code, and
hundreds
of files are added or modified.
I wonder, how can I apply those
thousands of changes to new kernel source
quickly and
easily?
The bad news is that there isn't a quickly
and easily way to do it.
The kernel doesn't have an stable API
(read
Documentation/stable_api_nonsense.txt) and the ARM part of
the kernel
is one of the most fast changing lately. So probably most of
the
drivers and SoC enablement platform code won't work with
newer
kernels.
So, this isn't a trivial task.
Best
regards,
--
Javier Martínez Canillas
(+34) 682 39 81
69
Barcelona,
Spain
_______________________________________________
Kernelnewbies
mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies
mailing
list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
|
