Re: socketCan build fails

[Wolfgang Grandegger <wg@grandegger.com>]

Hi Steffen,

On 02/27/2012 10:12 AM, Steffen Rose wrote:
> Hi,
> 
>> The content of the kernel/2.6 directory is mainly needed for older Kernels
>> that do not have SocketCAN support (which was introduced in 2.6.25).
> 
> differ the kernel socketCAN path from our used socketCAN?

Yes, if "our used socketCAN" means the out-of-tree "SocketCAN
repository" (formerly at BerliOS and now at gitorious.rog).

> Of course, I know, this both are different repositories. But I was the meaning, 
> that at the first the changes comes in our repository and later our patches are 
> copied to the kernel.

Unfortunately, that's not the case. The main focus is on providing
support for the mainline kernel. The intention is that patches/fixes are
backported from the kernel tree but also that did not always happen.
Both trees are not in full sync, sorry.

> Additional question:
> Are there a Kernel list with information, which socketCAN feature is included 
> (e.g. 3.2 - gateway functionality)?

"$ git log drivers/net/can" should provide that information.

> Is there a "TAG" in our repository to see, which software state was copied to 
> which kernel version?

No, see above.

Wolfgang.