Messages in this thread | | | Date | Wed, 2 Jun 2010 21:40:23 +0530 | Subject | Re: make ARM=arm menuconfig problem in mainline | From | Nobin Mathew <> |
| |
when I go to select ARM system type(OMAP, Davinci etc), I am not seeing any entries there in the pop up window. When I remove bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, >> S3C2442, S3C2443, S3C2450" it is working fine. I feel it is something to do with length of that string.
Is it possible to attach screenshots in this list?
Thanks Nobin
On Wed, Jun 2, 2010 at 9:27 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote: > On Wed, 2 Jun 2010 20:04:28 +0530 Nobin Mathew wrote: > >> adding linux-arm-kernel@lists.infradead.org >> >> Hi, >> >> The following entry creates problem in ARM System type menu. I am >> using a Fedora 12 system. > > What kind of problem does it create? > It seems to work for me (on f11, not f12). > Does it have something to do with F12 specifically? > > >> Length of bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, >> S3C2442, S3C2443, S3C2450" is the problem. How can I fix it. > > Describe the problem, please. > >> config ARCH_S3C2410 >> bool "Samsung S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, >> S3C2442, S3C2443, S3C2450" >> select GENERIC_GPIO >> select ARCH_HAS_CPUFREQ >> select HAVE_CLK >> select ARCH_USES_GETTIMEOFFSET >> help >> Samsung S3C2410X CPU based systems, such as the Simtec Electronics >> BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or >> the Samsung SMDK2410 development board (and derivatives). >> >> Note, the S3C2416 and the S3C2450 are so close that they even share >> the same SoC ID code. This means that there is no seperate machine >> directory (no arch/arm/mach-s3c2450) as the S3C2416 was first. > > > --- > ~Randy > *** Remember to use Documentation/SubmitChecklist when testing your code *** > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |