* RE: Compiling Linux Kernel for ML403
@ 2007-02-24 13:03 Mohammad Sadegh Sadri
2007-02-24 15:46 ` Grant Likely
0 siblings, 1 reply; 4+ messages in thread
From: Mohammad Sadegh Sadri @ 2007-02-24 13:03 UTC (permalink / raw)
To: Magnus Hjorth; +Cc: Linux PPC Linux PPC
well
Then, if what you say is correct, We should do almost all of the job by han=
d, ... this is very difficult and time cosuming....
What is the role of xmake tcl script in generated linux bsp?=20
I renamed all of ML40x to ML403 in all of the files of the generated bsp, b=
ut still I encounter this error while compiling the kernel using xmake:
arch/ppc/platforms/4xx/virtex.c:20: error: array type has incomplete elemen=
t type
arch/ppc/platforms/4xx/virtex.c:60: error: field name not in record or unio=
n initializer
arch/ppc/platforms/4xx/virtex.c:60: error: (near initialization for 'core_o=
cp')
make[1]: *** [arch/ppc/platforms/4xx/virtex.o] Error 1
make: *** [arch/ppc/platforms/4xx] Error 2
any body knows the reason for this error message?
----------------------------------------
> Date: Sat, 24 Feb 2007 13:38:11 +0100
> From: mh@omnisys.se
> To: mamsadegh@hotmail.com
> CC: linuxppc-embedded@ozlabs.org
> Subject: Re: Compiling Linux Kernel for ML403
>=20
> Hi Mohammad,
>=20
> The files that are in generated in the BSP are for an older mvista kernel=
(based on 2.6.14 I think) and some things have changed since then. In part=
icular some tables in virtex.c and xilinx_ml403.c are different. It's proba=
bly easier to fix these files manually than to copy the files from the BSP.=
=20
>=20
> You should rename the xparameters_ml40x.h in the BSP to xparameters_ml403=
.h. You may also need to add some #defines for constants that have changed =
names, which you will discover when you try to compile the kernel.=20
>=20
> You need to manually edit Kconfig files to get menuconfig entries, and yo=
u will need to edit some Makefiles to get it all to be compiled in. It coul=
d be easier in mvista, I don't know... Good luck!
>=20
> Best regards,
> Magnus
>=20
> On Sat, 24 Feb 2007 09:44:33 +0000
> Mohammad Sadegh Sadri wrote:
>=20
> >=20
> > Hi all,
> >=20
> > Again , I have some questions:
> >=20
> > I downloaded the linux kernel from both of source.mvista.com ( 2.6.19 I=
think ) and kernel.org ( 2.6.20 ) , and I did the following tests on both =
of them:
> >=20
> > 1- Using EDK 8.2.02 , generated my base system for ml403. EDK generated=
BSP files.=20
> > 2- I copied the linux-2.6.20.tar.bz2 into proper location in eldk direc=
tory and extracted there, Then I copied all of the BSP files into the root =
folder of my kernel source.
> > 3- Editted the Makefile and set the ARCH and CROSS_COMPILE variables , =
also I set all of the env variables needed by edk.=20
> >=20
> > 4- ( First Question ) looking the BSP files generated by EDK I see that=
/arch/ppc/platforms/4xx/xparameters contains two files: xparameteres.h and=
xparameters_ml40x.h=20
> > However when I look at the same folder in kernel source tree I see that=
the file name is different, it is xparameters_ml403.h=20
> > Is this OK? I think that I should rename the file?
> >=20
> > 5- ( Second Question ) Although I have copied the BSP files into the my=
kernel source tree completely, nothing changes in the menuconfig. I mean t=
he menuconfig ( menus and configs ) is the same as before, for example , n=
o special option is added for gigabit ethernet support ( hard temac )
> > Is this ok? I expected to see some changes in menuconfig when I copied =
the files into kernel source.=20
> >=20
> > 6- ( Third Question ) Now, I do the needed primary configurations and t=
hen I type : make, to begin the build process. Obviously, It generates some=
error messages, Is this kind of behaviour natural? I was not expecting to=
see syntax errors in kernel source tree ? ( Of course, when I build the ke=
rnel without Xilinx BSP every thing is OK )
> >=20
> > ( The above descriptions are true for both of mvista and kernel.org, )
> >=20
> > thanks
> >=20
> >=20
> >=20
> > _________________________________________________________________
> > Explore the seven wonders of the world
> > http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=
=3DQBRE
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
> --=20
>=20
> Magnus Hjorth, M.Sc.
> Omnisys Instruments AB
> Gruvgatan 8
> SE-421 30 V=E4stra Fr=F6lunda, SWEDEN
> Phone: +46 31 734 34 09
> Fax: +46 31 734 34 29
> http://www.omnisys.se=20
_________________________________________________________________
Connect to the next generation of MSN Messenger=A0
http://imagine-msn.com/messenger/launch80/default.aspx?locale=3Den-us&sourc=
e=3Dwlmailtagline=
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Compiling Linux Kernel for ML403
2007-02-24 13:03 Compiling Linux Kernel for ML403 Mohammad Sadegh Sadri
@ 2007-02-24 15:46 ` Grant Likely
0 siblings, 0 replies; 4+ messages in thread
From: Grant Likely @ 2007-02-24 15:46 UTC (permalink / raw)
To: Mohammad Sadegh Sadri; +Cc: Linux PPC Linux PPC
On 2/24/07, Mohammad Sadegh Sadri <mamsadegh@hotmail.com> wrote:
>
>
> well
>
> Then, if what you say is correct, We should do almost all of the job by hand, ... this is very difficult and time cosuming....
>
> What is the role of xmake tcl script in generated linux bsp?
>
The EDK <--> Linux kernel interactions is.... messy... at best. I'm
not at all a fan of the BSP generation approach that EDK uses. I
understand from the Xilinx folks that they are working to get their
driver code into mainline, but in the meantime you need to do stuff
manually unless you're using the exact kernel source version that the
EDK code generation works with.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
^ permalink raw reply [flat|nested] 4+ messages in thread
* Compiling Linux Kernel for ML403
@ 2007-02-24 9:44 Mohammad Sadegh Sadri
2007-02-24 12:38 ` Magnus Hjorth
0 siblings, 1 reply; 4+ messages in thread
From: Mohammad Sadegh Sadri @ 2007-02-24 9:44 UTC (permalink / raw)
To: Linux PPC Linux PPC
Hi all,
Again , I have some questions:
I downloaded the linux kernel from both of source.mvista.com ( 2.6.19 I thi=
nk ) and kernel.org ( 2.6.20 ) , and I did the following tests on both of t=
hem:
1- Using EDK 8.2.02 , generated my base system for ml403. EDK generated BSP=
files.=20
2- I copied the linux-2.6.20.tar.bz2 into proper location in eldk directory=
and extracted there, Then I copied all of the BSP files into the root fold=
er of my kernel source.
3- Editted the Makefile and set the ARCH and CROSS_COMPILE variables , also=
I set all of the env variables needed by edk.=20
4- ( First Question ) looking the BSP files generated by EDK I see that /ar=
ch/ppc/platforms/4xx/xparameters contains two files: xparameteres.h and xpa=
rameters_ml40x.h=20
However when I look at the same folder in kernel source tree I see that the=
file name is different, it is xparameters_ml403.h=20
Is this OK? I think that I should rename the file?
5- ( Second Question ) Although I have copied the BSP files into the my ker=
nel source tree completely, nothing changes in the menuconfig. I mean the m=
enuconfig ( menus and configs ) is the same as before, for example , no sp=
ecial option is added for gigabit ethernet support ( hard temac )
Is this ok? I expected to see some changes in menuconfig when I copied the =
files into kernel source.=20
6- ( Third Question ) Now, I do the needed primary configurations and then =
I type : make, to begin the build process. Obviously, It generates some err=
or messages, Is this kind of behaviour natural? I was not expecting to see=
syntax errors in kernel source tree ? ( Of course, when I build the kernel=
without Xilinx BSP every thing is OK )
( The above descriptions are true for both of mvista and kernel.org, )
thanks
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=3DQ=
BRE=
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Compiling Linux Kernel for ML403
2007-02-24 9:44 Mohammad Sadegh Sadri
@ 2007-02-24 12:38 ` Magnus Hjorth
0 siblings, 0 replies; 4+ messages in thread
From: Magnus Hjorth @ 2007-02-24 12:38 UTC (permalink / raw)
To: Mohammad Sadegh Sadri; +Cc: Linux PPC Linux PPC
Hi Mohammad,
The files that are in generated in the BSP are for an older mvista kernel (=
based on 2.6.14 I think) and some things have changed since then. In partic=
ular some tables in virtex.c and xilinx_ml403.c are different. It's probabl=
y easier to fix these files manually than to copy the files from the BSP.=20
You should rename the xparameters_ml40x.h in the BSP to xparameters_ml403.h=
. You may also need to add some #defines for constants that have changed na=
mes, which you will discover when you try to compile the kernel.=20
You need to manually edit Kconfig files to get menuconfig entries, and you =
will need to edit some Makefiles to get it all to be compiled in. It could =
be easier in mvista, I don't know... Good luck!
Best regards,
Magnus
On Sat, 24 Feb 2007 09:44:33 +0000
Mohammad Sadegh Sadri <mamsadegh@hotmail.com> wrote:
>=20
> Hi all,
>=20
> Again , I have some questions:
>=20
> I downloaded the linux kernel from both of source.mvista.com ( 2.6.19 I t=
hink ) and kernel.org ( 2.6.20 ) , and I did the following tests on both of=
them:
>=20
> 1- Using EDK 8.2.02 , generated my base system for ml403. EDK generated B=
SP files.=20
> 2- I copied the linux-2.6.20.tar.bz2 into proper location in eldk directo=
ry and extracted there, Then I copied all of the BSP files into the root fo=
lder of my kernel source.
> 3- Editted the Makefile and set the ARCH and CROSS_COMPILE variables , al=
so I set all of the env variables needed by edk.=20
>=20
> 4- ( First Question ) looking the BSP files generated by EDK I see that /=
arch/ppc/platforms/4xx/xparameters contains two files: xparameteres.h and x=
parameters_ml40x.h=20
> However when I look at the same folder in kernel source tree I see that t=
he file name is different, it is xparameters_ml403.h=20
> Is this OK? I think that I should rename the file?
>=20
> 5- ( Second Question ) Although I have copied the BSP files into the my k=
ernel source tree completely, nothing changes in the menuconfig. I mean the=
menuconfig ( menus and configs ) is the same as before, for example , no =
special option is added for gigabit ethernet support ( hard temac )
> Is this ok? I expected to see some changes in menuconfig when I copied th=
e files into kernel source.=20
>=20
> 6- ( Third Question ) Now, I do the needed primary configurations and the=
n I type : make, to begin the build process. Obviously, It generates some e=
rror messages, Is this kind of behaviour natural? I was not expecting to s=
ee syntax errors in kernel source tree ? ( Of course, when I build the kern=
el without Xilinx BSP every thing is OK )
>=20
> ( The above descriptions are true for both of mvista and kernel.org, )
>=20
> thanks
>=20
>=20
>=20
> _________________________________________________________________
> Explore the seven wonders of the world
> http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=
=3DQBRE
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
--=20
Magnus Hjorth, M.Sc.
Omnisys Instruments AB
Gruvgatan 8
SE-421 30 V=E4stra Fr=F6lunda, SWEDEN
Phone: +46 31 734 34 09
Fax: +46 31 734 34 29
http://www.omnisys.se=20
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-02-24 15:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-24 13:03 Compiling Linux Kernel for ML403 Mohammad Sadegh Sadri
2007-02-24 15:46 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2007-02-24 9:44 Mohammad Sadegh Sadri
2007-02-24 12:38 ` Magnus Hjorth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).