Build standalone kernel - where are the defconfig's?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Build standalone kernel - where are the defconfig's?

ソリューションへジャンプ
8,563件の閲覧回数
manoweb
Contributor II

I am following the i.MX Porting Guide to build a Linux kernel in standalone environment.

https://www.nxp.com/docs/en/user-guide/IMX_PORTING_GUIDE.pdf section 2.1.1 page 10 indicates:

 

git clone https://source.codeaurora.org/external/imx/linux-imx
cd linux-imx
git checkout -b lf-5.15.32-2.0.0

make imx_v8_defconfig

Unfortunately I get the error:

*** 
*** Can't find default configuration "arch/arm/configs/imx_v8_defconfig"!
***
make[1]: *** [/home/alesan/linux-imx/scripts/kconfig/Makefile:96: imx_v8_defconfig] Error 1
make: *** [Makefile:493: imx_v8_defconfig] Error 2

 

It's obvious because directory arch/arm/configs/ does not have any imx* file (actually there is imx_v4_v5_defconfig which i do not believe is correct). I tried also other tags and I have not found any relevant defconfig. It seems I am doing something very wrong, as the manual clearly states something that I cannot find. Can somebody help me out? Thanks

 

 

ラベル(1)
0 件の賞賛
返信
1 解決策
8,529件の閲覧回数
manoweb
Contributor II

OK I see the problem now: I was stupidly copying and pasting from the PDF manual that only shows a somewhat misleading invocation of git checkout to bring out the correct tag. The manual suggests:

The git cloned repository contains all the NXP releases. To work with a different release, the git tag command shows
available releases and
git checkout <tag name> is used to move to that version.
lf-5.15.32-2.0.0

For example, choose lf-5.15.32-2.0.0 snapshot:
$ git checkout -b lf-5.15.32-2.0.0

 

Well, any competent git user knows that it should be:

git checkout tags/lf-5.15.32-2.0.0 

 

after I started using brain to type the correct git command, everything is nominal.

元の投稿で解決策を見る

0 件の賞賛
返信
3 返答(返信)
8,530件の閲覧回数
manoweb
Contributor II

OK I see the problem now: I was stupidly copying and pasting from the PDF manual that only shows a somewhat misleading invocation of git checkout to bring out the correct tag. The manual suggests:

The git cloned repository contains all the NXP releases. To work with a different release, the git tag command shows
available releases and
git checkout <tag name> is used to move to that version.
lf-5.15.32-2.0.0

For example, choose lf-5.15.32-2.0.0 snapshot:
$ git checkout -b lf-5.15.32-2.0.0

 

Well, any competent git user knows that it should be:

git checkout tags/lf-5.15.32-2.0.0 

 

after I started using brain to type the correct git command, everything is nominal.

0 件の賞賛
返信
8,554件の閲覧回数
kef2
Senior Contributor V

I think you should specify architecture every time.

make ARCH=arm64 imx_v8_defconfig

arm64 configs are in arch/arm64/configs. Unless arm64 default compiler is installed, in addition to ARCH you may need to specify CROSS_COMPILE. 

0 件の賞賛
返信
8,535件の閲覧回数
manoweb
Contributor II

OK so something was wrong as in I did not specify the correct architecture. However, there is no arch/arm64 directory! Which branch should I use? See below:

 

~/linux-imx/arch$ git status 
On branch lf-5.15.32-2.0.0
nothing to commit, working tree clean

~/linux-imx/arch$ ls
alpha  arm  avr32  blackfin  c6x  cris  frv  h8300  hexagon  ia64  Kconfig  m32r  m68k  microblaze  mips  mn10300  openrisc  parisc  powerpc  s390  score  sh  sparc  tile  um  unicore32  x86  xtensa

~/linux-imx/arch$ cat ../.git/config  
[core]
       repositoryformatversion = 0
       filemode = true
       bare = false
       logallrefupdates = true
[remote "origin"]
       url = https://source.codeaurora.org/external/imx/linux-imx
       fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
       remote = origin
       merge = refs/heads/master

 

 

0 件の賞賛
返信