export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]?
Agreed. -Original Message- From: Kumar Gala [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 8:52 AM To: Rowan, Chad Cc: hs at denx.de; linuxppc-embedded at ozlabs.org Subject: Re: export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]? On Jul 20, 2006, at 8:38 AM, Rowan, Chad wrote: > Why should this be taken off list? Is it because it's Denx > specific? Or > because it's 2.4 specific? There is active 5200 development on the > 2.4 > kernel at Denx and it seems relevant to this list. Because its Denx specific, I believe the tree you are taking about is maintained only by Denx and not a community tree. - k > -Original Message- > From: Kumar Gala [mailto:galak at kernel.crashing.org] > Sent: Thursday, July 20, 2006 8:12 AM > To: hs at denx.de > Cc: linuxppc-embedded at ozlabs.org; Chad.Rowan at thyssenkrupp.com > Subject: Re: export-objs in spi Makefile broke in latest > linuxppc_2_4_deve l > [r eposted]? > > > On Jul 19, 2006, at 11:55 PM, Heiko Schocher wrote: > >> Hello Chad >> >>> linuxppc_2_4_devel is alive and well. >>> >>> http://www.denx.de/cgi-bin/gitweb.cgi? >>> p=linuxppc_2_4_devel.git;a=shortlog >> >> You speak from the DENX linuxppc_2_4_devel Kernel? If so, I think >> you are right. >> I had the same problem, some days ago. I made a SPI bitbanging >> algorithm, but >> I dont know, if this goes in the git repository from DENX ... >> Wolfgang? > > I think this issue should be taken off list. > > - k
export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]?
Why should this be taken off list? Is it because it's Denx specific? Or because it's 2.4 specific? There is active 5200 development on the 2.4 kernel at Denx and it seems relevant to this list. -Original Message- From: Kumar Gala [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 8:12 AM To: hs at denx.de Cc: linuxppc-embedded at ozlabs.org; Chad.Rowan at thyssenkrupp.com Subject: Re: export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]? On Jul 19, 2006, at 11:55 PM, Heiko Schocher wrote: > Hello Chad > >> linuxppc_2_4_devel is alive and well. >> >> http://www.denx.de/cgi-bin/gitweb.cgi? >> p=linuxppc_2_4_devel.git;a=shortlog > > You speak from the DENX linuxppc_2_4_devel Kernel? If so, I think > you are right. > I had the same problem, some days ago. I made a SPI bitbanging > algorithm, but > I dont know, if this goes in the git repository from DENX ... > Wolfgang? I think this issue should be taken off list. - k
export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]?
linuxppc_2_4_devel is alive and well. http://www.denx.de/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git;a=shortlog -Original Message- From: Kumar Gala [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 19, 2006 4:17 PM To: Rowan, Chad Cc: linuxppc-embedded at ozlabs.org Subject: Re: export-objs in spi Makefile broke in latest linuxppc_2_4_devel [r eposted]? On Jul 19, 2006, at 2:13 PM, Rowan, Chad wrote: > Shouldn't export-objs in drivers/spi be: > > export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5xxx-psc.o \ > spi-iti5200.o spi-eval.o > > instead of: > > export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5200psc.o \ > spi-iti5200.o spi-eval.o > > I believe the spi-algo-mpc5200psc.o should be spi-algo-mpc5xxx-psc.o, > correct? Are you really serious about linuxppc_2_4_devel? I can't believe linuxppc_2_4_devel has changed in months (if not over a year). - k
export-objs in spi Makefile broke in latest linuxppc_2_4_devel [r eposted]?
Shouldn't export-objs in drivers/spi be: export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5xxx-psc.o \ spi-iti5200.o spi-eval.o instead of: export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5200psc.o \ spi-iti5200.o spi-eval.o I believe the spi-algo-mpc5200psc.o should be spi-algo-mpc5xxx-psc.o, correct? Excuse the previous post. Office, hosed the format.
export-objs in spi Makefile broke in latest linuxppc_2_4_devel?
Shouldn't export-objs in drivers\spi be: export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5xxx-psc.o \ spi-iti5200.o spi-eval.o instead of: export-objs := spi-core.o spi-algo-mpc5xxx.o spi-algo-mpc5200psc.o \ spi-iti5200.o spi-eval.o -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060719/7e511dda/attachment.htm
Lite5200 MTD partitions in 2.6 build
In the 2.4 build I had to modify icecube.c in /linux/drivers/mtd/maps/ to specify the u-boot, kernel image, and root fs partitions. Icecube.c doesn't exist in the 2.6 drop. I got the top of the tree from the denx git yesterday. How do you config the partitions for the 2.6 kernel? Thanks, Chad -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060627/4f462f81/attachment.htm
