Re: [PATCHv2 1/2] crypto: updates omap sham device related platform code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 8 Apr 2010, Dmitry Kasatkin wrote:

> Hi,
> 
> BTW..
> 
> How will it work if those resource structures anyway conditionally compiled
> for OMAP2 or 3 or 4?
> only one structure will be compiled at once.

Hi Dmitry,

it is possible to build a kernel that will run on both OMAP2 and OMAP3 
(for example).  We call these kernels 'multi-OMAP' kernels.  In such a 
case, there will be multiple CONFIG_ARCH_OMAP* symbols defined, so 
multiple structure records will be included in the kernel image.  Also 
when this happens, the 'cpu_is_omap*' macros will be defined to something 
that is evaluated at kernel run-time, rather than compile-time (as would 
be the case with single-OMAP kernels). So then the appropriate structure 
can be passed at run-time to some device registration code.


- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux