On 10 Apr 2012, at 22:28, Bob Cochran wrote:
> On 04/10/2012 04:40 PM, Chris Tapp wrote:
>> I think this is a summary of the steps needed to reconfigure the
>> kernel,based on the instructions in the 6.0.1 dev manual:
>>
>> 1) bitbake linux-yocto -c clean
>> 2) bitbake linux-yocto -c menuconfig
On 04/10/2012 04:40 PM, Chris Tapp wrote:
I think this is a summary of the steps needed to reconfigure the kernel,based
on the instructions in the 6.0.1 dev manual:
1) bitbake linux-yocto -c clean
2) bitbake linux-yocto -c menuconfig
3) bitbake linux-yocto -c compile -f
4) bitbake linux-yocto
On 10 Apr 2012, at 21:50, Bruce Ashfield wrote:
> On 12-04-10 04:40 PM, Chris Tapp wrote:
>> I think this is a summary of the steps needed to reconfigure the
>> kernel,based on the instructions in the 6.0.1 dev manual:
>>
>> 1) bitbake linux-yocto -c clean
>> 2) bitbake linux-yocto -c menuconfig
On 12-04-10 04:40 PM, Chris Tapp wrote:
I think this is a summary of the steps needed to reconfigure the kernel,based
on the instructions in the 6.0.1 dev manual:
1) bitbake linux-yocto -c clean
2) bitbake linux-yocto -c menuconfig
3) bitbake linux-yocto -c compile -f
4) bitbake linux-yocto
Ho
I think this is a summary of the steps needed to reconfigure the kernel,based
on the instructions in the 6.0.1 dev manual:
1) bitbake linux-yocto -c clean
2) bitbake linux-yocto -c menuconfig
3) bitbake linux-yocto -c compile -f
4) bitbake linux-yocto
However, the bzimage in tmp/deploy/images is