On Mon, Sep 28, 2009 at 21:59, graff.yang wrote: > On Mon, 2009-09-28 at 15:17 -0400, Mike Frysinger wrote: >> On Mon, Sep 28, 2009 at 05:21, <[email protected]> wrote: >> > Revision 7489 Author gyang Date 2009-09-28 05:21:51 -0400 (Mon, 28 Sep >> > 2009) >> > >> > Log Message >> > >> > seperate defines about l1 code/cache and code only sram >> >> why ? the entire point was that treating it as one contiguous blob > > Task [#4788], dsp-bridge may write code to l1, it's dangerous, if there > is a gap between COREB_L1_CODE_START to COREB_L1_CODE_START + > L1_CODE_LENGTH.
then the code trying to do the write is broken. writing to that hole doesnt cause the hardware to blow up afaik. plus, i'm not sure the kernel should be managing any resources on Core B (like cache). you've added a bunch of CONFIG_xxx options that dont exist in Kconfig. -mike _______________________________________________ Linux-kernel-commits mailing list [email protected] https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
