Re: linux-omap-psp-2.6.32 breaks iscsi-target

[Philip Balister <philip@balister.org>]

On 08/30/2010 01:47 PM, Frans Meulenbroeks wrote:
> The current beagleboard angstrom and minimal distro's (and maybe
> others) use the linux-omap-psp_2.6.32.bb recipe to build the kernel.

What is iscsi and why would I need it on the Beagleboard?

Philip

>
> This one says:
> # This is the v2.6.32_OMAPPSP_03.00.01.06 branch
> SRCREV = "a6bad4464f985fdd3bed72e1b82dcbfc004d7869"
>
> # The main PR is now using MACHINE_KERNEL_PR, for omap3 see
> conf/machine/include/omap3.inc
> MACHINE_KERNEL_PR_append = "+gitr${SRCREV}"
>
> SRC_URI = "git://arago-project.org/git/people/sriram/ti-psp-omap.git;protocol=git;branch=master
> \
>
> Building it creates:
> linux-omap-psp-2.6.32-r88+gitra6bad4464f985fdd3bed72e1b82dcbfc004d7869
>
> However this is not a sound 2.6.32 tree. It contains this patch
> http://arago-project.org/git/people/?p=sriram/ti-psp-omap.git;a=commit;h=c720c7e8383aff1cb219bddf474ed89d850336e3
> which was not in the mainstream kernel in 2.6.32
>
> (compare
> http://arago-project.org/git/people/?p=sriram/ti-psp-omap.git;a=blob;f=include/net/inet_sock.h;hb=c720c7e8383aff1cb219bddf474ed89d850336e3
> with
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=blob;f=include/net/inet_sock.h;h=47004f35cc7eaf6f2b3cac2779ea7b7ccd5d9c1f;hb=HEAD
> ).
>
> The patch mentioned above was integrated in a 2.6.33 rc version.
>
> iscsi-utils uses the inet_sock struct, and contains code to access the
> daddr field of this struct. For versions<= .32 daddr is used. for
> higher versions inet_daddr is used.
> However the omap-psp kernel from arago does contain this patch  but
> reports as a .32 kernel causing a compiler errir when compiling
> iscsi_target (as the name the recipe expects is not there).
>
> Not sure how to fix it. Changing the test in iscsi-target is not an
> option as then it does not work for official .32 kernels.
> Probably the best way to fix this is to use the above patch to revert
> the change.
>
> anyone a better solution?
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>