RE: CML2-MTD-JFFS2
[email protected] Tue, 8 Apr 2003 14:12:44 +0900
| Newsgroups | gmane.linux.qplus.devel |
|---|---|
| Message-ID | <8470181DABD5D511B3E700D0B7A8AC4A9CD6FD@cms3> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2FD8D.7C9327B0 Content-Type: text/plain; charset="iso-2022-kr" > > Hi, > Uptill now I am compiling my kernel considering CRAMFS > as target fs. Then I had enabled JFFS2 support in > kernel. I had enabled options for JFFS2 and MTD > devices options too. As JFFS2 using it internally. > Then I have saved it to config.out file. > > While building the kernel it gave me error in linking > fs.o with vmlinux that it is unable to find > __get_mtd_device which was used by jffs2 driver. > > Latter on I came to know that all the options (like > CONFIG_MTD, CONFIG_MTD_CFI_ADV etc) I have selected > are saved in config.out but not written in .config, > due to that it had not compiled mtdcore module. I > have tried above procedure to compile the kernel again > but it is unable to write MTD options in .config file. > > Well, in fact, TB run "make oldconfig" with config.out file and produce .config file. What It meas is that TB run legacy configuration script which is defined in Config.in. (see kernelsystem.py for more details). This is intended for compatiblity. Ideally, configtrans.py script translate config.out (CML2 output) to .config (CML1 output) but if CML2 rules are incorrect, this can break actual dependency. So I decided to re-run make oldconfig to make sure that .config file doesn't break real kernel dependency. As for your case, I think there's are mismatch between CML2 description and legacy CML1 Config.in description. So TB reports that there are mismatch. > > Do you want my .config and config.out files? > > guess: > May there are dependencies which restricts MTD options > to write in to .config file. ? > > What is meaning of this message? > > ".config produced by oldconfig differ from that was > produced by configtrans.py". Is it indicator of any > side-effects.? Regards Heechul. - HeeChul Yun, Embedded S/W Team at ETRI phone: +82-42-860-1673 ------_=_NextPart_001_01C2FD8D.7C9327B0 Content-Type: text/html; charset="iso-2022-kr" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-2022-kr"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>RE: [Qplus-devel] CML2-MTD-JFFS2</TITLE> </HEAD> <BODY> <BR> <P><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Hi,</FONT> <BR><FONT SIZE=3D2>> Uptill now I am compiling my kernel considering = CRAMFS</FONT> <BR><FONT SIZE=3D2>> as target fs. Then I had enabled JFFS2 support = in</FONT> <BR><FONT SIZE=3D2>> kernel. I had enabled options for JFFS2 = and MTD</FONT> <BR><FONT SIZE=3D2>> devices options too. As JFFS2 using it = internally.</FONT> <BR><FONT SIZE=3D2>> Then I have saved it to config.out file.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> While building the kernel it gave me error in = linking</FONT> <BR><FONT SIZE=3D2>> fs.o with vmlinux that it is unable to = find</FONT> <BR><FONT SIZE=3D2>> __get_mtd_device which was used by jffs2 = driver.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Latter on I came to know that all the options = (like</FONT> <BR><FONT SIZE=3D2>> CONFIG_MTD, CONFIG_MTD_CFI_ADV etc) I have = selected</FONT> <BR><FONT SIZE=3D2>> are saved in config.out but not written in = .config,</FONT> <BR><FONT SIZE=3D2>> due to that it had not compiled mtdcore module. = I </FONT> <BR><FONT SIZE=3D2>> have tried above procedure to compile the = kernel again</FONT> <BR><FONT SIZE=3D2>> but it is unable to write MTD options in = .config file.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> </FONT> </P> <P><FONT SIZE=3D2>Well, in fact, TB run "make = oldconfig" with config.out file and produce .config file. What It = meas is that TB run legacy configuration script which is defined in = Config.in. (see kernelsystem.py for more details). This is intended for = compatiblity. Ideally, configtrans.py script translate config.out (CML2 = output) to .config (CML1 output) but if CML2 rules are incorrect, this = can break actual dependency. So I decided to re-run make oldconfig to = make sure that .config file doesn't break real kernel dependency. = </FONT></P> <P><FONT SIZE=3D2>As for your case, I think there's are mismatch = between CML2 description and legacy CML1 Config.in description. So TB = reports that there are mismatch. </FONT></P> <P><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> Do you want my .config and config.out = files?</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> guess:</FONT> <BR><FONT SIZE=3D2>> May there are dependencies which restricts MTD = options</FONT> <BR><FONT SIZE=3D2>> to write in to .config file. ?</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> What is meaning of this message?</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> ".config produced by oldconfig differ from = that was</FONT> <BR><FONT SIZE=3D2>> produced by configtrans.py". Is it = indicator of any</FONT> <BR><FONT SIZE=3D2>> side-effects.?</FONT> </P> <BR> <P><FONT SIZE=3D2>Regards</FONT> <BR><FONT SIZE=3D2>Heechul. </FONT> </P> <P><FONT SIZE=3D2>-</FONT> <BR><FONT SIZE=3D2>HeeChul = Yun, </FONT> <BR><FONT SIZE=3D2>Embedded S/W Team at ETRI</FONT> <BR><FONT SIZE=3D2>phone: +82-42-860-1673</FONT> </P> </BODY> ------_=_NextPart_001_01C2FD8D.7C9327B0-- ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/