search for: _bl

...verify against These three components can come as files to be directly loaded. However for the current GR firmware we took the approach of splitting the bl, code and data sections into their own files, and building the image and descriptor on-the-fly, as you can see from gm200/gr: gm200/gr/fecs_bl.bin gm200/gr/fecs_data.bin gm200/gr/fecs_inst.bin gm200/gr/fecs_sig.bin The bl, data, and inst files are loaded and combined into an image while the corresponding descriptor is built. This is done in the ls_ucode_img_build() function. The main reason for doing this is there is that for a given...

...n come as files to be directly loaded. However for >> the current GR firmware we took the approach of splitting the bl, code and >> data sections into their own files, and building the image and descriptor >> on-the-fly, as you can see from gm200/gr: >> >> gm200/gr/fecs_bl.bin >> gm200/gr/fecs_data.bin >> gm200/gr/fecs_inst.bin >> gm200/gr/fecs_sig.bin >> >> The bl, data, and inst files are loaded and combined into an image while the >> corresponding descriptor is built. This is done in the ls_ucode_img_build() >> function. &...

...t;>> the current GR firmware we took the approach of splitting the bl, code >>>> and >>>> data sections into their own files, and building the image and descriptor >>>> on-the-fly, as you can see from gm200/gr: >>>> >>>> gm200/gr/fecs_bl.bin >>>> gm200/gr/fecs_data.bin >>>> gm200/gr/fecs_inst.bin >>>> gm200/gr/fecs_sig.bin >>>> >>>> The bl, data, and inst files are loaded and combined into an image while >>>> the >>>> corresponding descriptor is bui...

...ing the bl, code >>>>>> and >>>>>> data sections into their own files, and building the image and >>>>>> descriptor >>>>>> on-the-fly, as you can see from gm200/gr: >>>>>> >>>>>> gm200/gr/fecs_bl.bin >>>>>> gm200/gr/fecs_data.bin >>>>>> gm200/gr/fecs_inst.bin >>>>>> gm200/gr/fecs_sig.bin >>>>>> >>>>>> The bl, data, and inst files are loaded and combined into an image >>>>>> while >...

...three components can come as files to be directly loaded. However for > the current GR firmware we took the approach of splitting the bl, code and > data sections into their own files, and building the image and descriptor > on-the-fly, as you can see from gm200/gr: > > gm200/gr/fecs_bl.bin > gm200/gr/fecs_data.bin > gm200/gr/fecs_inst.bin > gm200/gr/fecs_sig.bin > > The bl, data, and inst files are loaded and combined into an image while the > corresponding descriptor is built. This is done in the ls_ucode_img_build() > function. > > The main reason for...

...>>> for >>> the current GR firmware we took the approach of splitting the bl, code >>> and >>> data sections into their own files, and building the image and descriptor >>> on-the-fly, as you can see from gm200/gr: >>> >>> gm200/gr/fecs_bl.bin >>> gm200/gr/fecs_data.bin >>> gm200/gr/fecs_inst.bin >>> gm200/gr/fecs_sig.bin >>> >>> The bl, data, and inst files are loaded and combined into an image while >>> the >>> corresponding descriptor is built. This is done in the >...

...k the approach of splitting the bl, code >>>>> and >>>>> data sections into their own files, and building the image and >>>>> descriptor >>>>> on-the-fly, as you can see from gm200/gr: >>>>> >>>>> gm200/gr/fecs_bl.bin >>>>> gm200/gr/fecs_data.bin >>>>> gm200/gr/fecs_inst.bin >>>>> gm200/gr/fecs_sig.bin >>>>> >>>>> The bl, data, and inst files are loaded and combined into an image >>>>> while >>>>> the &gt...

...r=3D"#888888"><div>Nigel=A0</div></font><div><div>= </div><div class=3D"h5"><div><br></div><div>On Mar 15, 2010, at 12:08 PM, &= quot;<a href=3D"mailto:ozemale at ozemail.com.au" target=3D"_blank">ozemale at oz= email.com.au</a>&quot; &lt;<a href=3D"mailto:ozemale at ozemail.com.au" target= =3D"_blank">ozemale at ozemail.com.au</a>&gt; wrote:<br> <br></div><div></div><blockquote type=3D"cite&...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking