lkml.org 
[lkml]   [2012]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [uclinux-dist-devel] blackfin: how is the I-pipe code supposed to be built?
Date
On Monday 11 June 2012 15:44:50 Paul Bolle wrote:
> On Sun, 2012-06-10 at 23:05 -0400, Zhang, Sonic wrote:
> > The IPIPE patch is part of the ADEOS real time kernel patch. The
> > common part of this patch hasn't been merged into mainline by the
> > maintainer Philippe Gerum, although the Blackfin architecture part
> > was. The relative Kbuild support and Kconfig symbols are defined in
> > the ADOES common patch.
>
> What's the point of having code in the mainline tree, for over three
> years, without any Kbuild or Kconfig support?

because the Blackfin team cares about keeping ADEOS active throughout the
rewrites/updates of core code. it isn't hurting keeping the code in the
arch/blackfin/ tree, and we're ok with any overhead it implies for the team.
-mike
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2012-06-12 04:01    [W:0.443 / U:0.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site