Menu
▾
▴
devil-linux-develop
|
From: Diego T. <dt...@co...> - 2003-10-22 05:53:11
|
Here goes a silly question. I want to compile dl for an epia motherboard. There is no option to choose from on the build menu. The only available options are 486,586 and 686. This option is for the linux kernel only or its also used as an argument to the gcc compile of every package? Currently i'd need to select the via c3-2 option (the one that shows on the kernel menuconfig), but there are also other options: - "CyrixIII" for VIA Cyrix III or VIA C3. . - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above). -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2003-10-22 13:13:03
|
> Here goes a silly question. I want to compile dl for an epia > motherboard. > > There is no option to choose from on the build menu. The only > available options are 486,586 and 686. If someone is going add options, please add "Athlon" too. Older AMD chipsets would be nice too (K6). > This option is for the linux kernel only or its also used as an > argument to the gcc compile of every package? I _think_ that gcc itself gets compiled with the option, so that arch is the default for everything compiled after that. > Currently i'd need to select the via c3-2 option (the one that shows > on the kernel menuconfig), but there are also other options: > > - "CyrixIII" for VIA Cyrix III or VIA C3. . > - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above). - BS |
|
From: Heiko Z. <he...@zu...> - 2003-10-22 14:57:08
|
>> Here goes a silly question. I want to compile dl for an epia >> motherboard. >> >> There is no option to choose from on the build menu. The only >> available options are 486,586 and 686. > > If someone is going add options, please add "Athlon" too. > Older AMD chipsets would be nice too (K6). Modifications have to be done to the following scripts: prepare linux settings A grep over the rest of the files should uncover the ones I forgott. ;-) >> This option is for the linux kernel only or its also used as an >> argument to the gcc compile of every package? > > I _think_ that gcc itself gets compiled with the option, so that arch is > the default for everything compiled after that. Yes this is correct. And just to make sure, we change the output of the uname command (done in the prepare script). -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Diego T. <dt...@co...> - 2003-10-23 00:45:00
|
On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: > Modifications have to be done to the following scripts: > prepare > linux > settings about the config_linux settings for the kernel: why is this configured: CONFIG_HIGHMEM4G=y CONFIG_HIGHMEM=y CONFIG_HIGHIO=y Support for highmem is only worth when the system has more than 4g, and then, there is a penalty for each page access. also, pages are bigger (so more memory can be dimensioned). This should be a more practical configuration: CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_HIGHMEM is not set -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-23 02:08:18
|
Diego Torres wrote: >On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: > > >>Modifications have to be done to the following scripts: >>prepare >>linux >>settings >> >> > >about the config_linux settings for the kernel: > >why is this configured: > >CONFIG_HIGHMEM4G=y >CONFIG_HIGHMEM=y >CONFIG_HIGHIO=y > >Support for highmem is only worth when the system has more than 4g, and then, there is a penalty for each page access. also, pages are bigger (so more memory can be dimensioned). > >This should be a more practical configuration: > >CONFIG_NOHIGHMEM=y ># CONFIG_HIGHMEM4G is not set ># CONFIG_HIGHMEM64G is not set ># CONFIG_HIGHMEM is not set > > > We need the highmem support for computers with >= 1 GB RAM, which is not so uncommon. cya Heiko |
|
From: Manu <ee...@fr...> - 2003-10-25 16:41:43
|
Heiko Zuerker a écrit: > Diego Torres wrote: > >> On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: >> >> >>> Modifications have to be done to the following scripts: >>> prepare >>> linux >>> settings >>> >> >> >> about the config_linux settings for the kernel: >> >> why is this configured: >> >> CONFIG_HIGHMEM4G=y >> CONFIG_HIGHMEM=y >> CONFIG_HIGHIO=y >> >> Support for highmem is only worth when the system has more than 4g, >> and then, there is a penalty for each page access. also, pages are >> bigger (so more memory can be dimensioned). >> >> This should be a more practical configuration: >> >> CONFIG_NOHIGHMEM=y >> # CONFIG_HIGHMEM4G is not set >> # CONFIG_HIGHMEM64G is not set >> # CONFIG_HIGHMEM is not set >> >> >> > We need the highmem support for computers with >= 1 GB RAM, which is > not so uncommon. Hi all, You've got too much money ;-) Do you really know lots of people who runs DL on a 1 Gb Ram Box as firewall ? Mine is K6-200 Mhz with 64 Mb ;-) I suggest keeping 4Gb for apache + mail + av Boxes, not for Fw as those old recycled PCs will probably suffer from page access overhead ... I think it should be in the menuconfig options ... Cya MaNU > > cya > Heiko > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN developer relations > Here's your chance to show off your extensive product knowledge > We want to know what you know. Tell us and you have a chance to win $100 > http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > |
|
From: Heiko Z. <he...@zu...> - 2003-10-25 22:26:25
|
Manu wrote: > > > Heiko Zuerker a écrit: > >> Diego Torres wrote: >> >>> On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: >>> >>> >>>> Modifications have to be done to the following scripts: >>>> prepare >>>> linux >>>> settings >>>> >>> >>> >>> >>> about the config_linux settings for the kernel: >>> >>> why is this configured: >>> >>> CONFIG_HIGHMEM4G=y >>> CONFIG_HIGHMEM=y >>> CONFIG_HIGHIO=y >>> >>> Support for highmem is only worth when the system has more than 4g, >>> and then, there is a penalty for each page access. also, pages are >>> bigger (so more memory can be dimensioned). >>> >>> This should be a more practical configuration: >>> >>> CONFIG_NOHIGHMEM=y >>> # CONFIG_HIGHMEM4G is not set >>> # CONFIG_HIGHMEM64G is not set >>> # CONFIG_HIGHMEM is not set >>> >>> >>> >> We need the highmem support for computers with >= 1 GB RAM, which is >> not so uncommon. > > > Hi all, > > You've got too much money ;-) > Do you really know lots of people who runs DL on a 1 Gb Ram Box as > firewall ? > Mine is K6-200 Mhz with 64 Mb ;-) > > I suggest keeping 4Gb for apache + mail + av Boxes, not for Fw as > those old recycled PCs will probably suffer from page access overhead ... > > I think it should be in the menuconfig options ... Anybody else thinks we should put it into menuconfig ? We could turn it off automatically, when the CPU type is i586 or lower. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-10-26 01:08:12
|
On Sat, Oct 25, 2003 at 06:21:52PM -0400, Heiko Zuerker wrote: > > > >I think it should be in the menuconfig options ... > > Anybody else thinks we should put it into menuconfig ? > We could turn it off automatically, when the CPU type is i586 or lower. if we are going to touch anything, the let it be fully configurable. Don't take automatic decisions. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-23 01:17:23
|
On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: > Modifications have to be done to the following scripts: I've added support for EPIA C3-2 CPUs to the build system. There are only two files modified: - configuration/prepare.config added a KERNEL tag to the menuconfig options, so now one could choose the cpu type for the linux kernel. This is completely independant from the CONFIG_CPU switch. So now we have: CONFIG_CPU : the command passed to gcc as -march=type CONFIG_KERNEL_CPU : the string appended to the linux .config file. - scripts/prepare one line modified, so $CONFIG_KERNEL_CPU is written to the .config file. So, as pointed on the kernel mailing list (see the link on prepare.config), for an epia c3-2 motherboard you have to choose CPU=686 and KERNEL=VIAC3-2. Adding support for athlons (etc) should be very easy... is everyone happy with this change? it works and it's simple :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-23 01:45:35
|
Diego Torres wrote: >On Wed, Oct 22, 2003 at 10:25:37AM -0400, Heiko Zuerker wrote: > > > >>Modifications have to be done to the following scripts: >> >> > >I've added support for EPIA C3-2 CPUs to the build system. > >There are only two files modified: > >- configuration/prepare.config >added a KERNEL tag to the menuconfig options, so now one could choose the cpu type for the linux kernel. > >This is completely independant from the CONFIG_CPU switch. So now we have: > >CONFIG_CPU : the command passed to gcc as -march=type >CONFIG_KERNEL_CPU : the string appended to the linux .config file. > >- scripts/prepare >one line modified, so $CONFIG_KERNEL_CPU is written to the .config file. > >So, as pointed on the kernel mailing list (see the link on prepare.config), for an epia c3-2 motherboard you have to choose CPU=686 and KERNEL=VIAC3-2. > >Adding support for athlons (etc) should be very easy... > >is everyone happy with this change? it works and it's simple :) > > > Should we keep it separated or rather have only one configuration parameter? I think 1 should be better. We could set then the other one within the scripts. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-10-26 13:39:11
|
On Wed, Oct 22, 2003 at 09:31:12PM -0400, Heiko Zuerker wrote: > Should we keep it separated or rather have only one configuration parameter? > > I think 1 should be better. We could set then the other one within the > scripts. Thats not so easy. I've tried to force one of the values relaying on the user choice, but it has to be validated by the user, selecting it. If the user doesn't select an option, it isn't written to the .config file. The other option is to force the value on every script, but thats not easy because of the order of execution. I'll checkin the option i liked most, and then anybody will be free to improve it :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2003-10-23 03:00:47
|
> This is completely independant from the CONFIG_CPU switch. So now we have: > > CONFIG_CPU : the command passed to gcc as -march=type > CONFIG_KERNEL_CPU : the string appended to the linux .config file. Why have two different options? Why not add CPU types to the existing option and compile everything for the same CPU? - BS |
|
From: Diego T. <dt...@co...> - 2003-10-24 02:06:58
|
On Wed, Oct 22, 2003 at 09:23:58PM -0400, Bruce Smith wrote: > > CONFIG_CPU : the command passed to gcc as -march=type > > CONFIG_KERNEL_CPU : the string appended to the linux .config file. > > Why have two different options? Why not add CPU types to the existing > option and compile everything for the same CPU? because they are two different things. the kernel cpu is for the ordering of instructions, cache size, etc. the config cpu is for using specific instructions for the architecture. With the via epia, you have to configure the kernel as VIAC3-2, and the executables as i686, *NOT AS C3*. I don't know the correct parameters for other archs. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-25 13:41:02
|
> On Wed, Oct 22, 2003 at 09:23:58PM -0400, Bruce Smith wrote: >> > CONFIG_CPU : the command passed to gcc as -march=type >> > CONFIG_KERNEL_CPU : the string appended to the linux .config file. >> >> Why have two different options? Why not add CPU types to the existing >> option and compile everything for the same CPU? > > because they are two different things. > > the kernel cpu is for the ordering of instructions, cache size, etc. > > the config cpu is for using specific instructions for the architecture. > > With the via epia, you have to configure the kernel as VIAC3-2, and the > executables as i686, *NOT AS C3*. > > I don't know the correct parameters for other archs. Then I would suggest modifying our build system this way: Select (1) CPU type in menuconfig and depending on this type we set the 2 parameters. example: i586: uname/gcc will use i586 and the Kernel also. VIAC3-2: uname/gcc will use i686 and the Kernel VIAC3-2 I think otherwise it get's to confusing. Can you do those changes and check it in ? -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Diego T. <dt...@co...> - 2003-10-26 01:08:34
|
On Fri, Oct 24, 2003 at 08:43:34AM -0400, Heiko Zuerker wrote: > i586: uname/gcc will use i586 and the Kernel also. > VIAC3-2: uname/gcc will use i686 and the Kernel VIAC3-2 > > I think otherwise it get's to confusing. > > Can you do those changes and check it in ? doesn't look complicate, i could try :) but what if more combinations arise? for example, for other kinds of cpu's? we should take care of all of them? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-26 02:22:50
|
Diego Torres wrote: >On Fri, Oct 24, 2003 at 08:43:34AM -0400, Heiko Zuerker wrote: > > >>i586: uname/gcc will use i586 and the Kernel also. >>VIAC3-2: uname/gcc will use i686 and the Kernel VIAC3-2 >> >>I think otherwise it get's to confusing. >> >>Can you do those changes and check it in ? >> >> > >doesn't look complicate, i could try :) but what if more combinations arise? for example, for other kinds of cpu's? we should take care of all of them? > > Shouldn't be hard, just add the stuff to the menuconfig part. Then modify the settings script, to set the correct values. cya Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-10-22 14:47:09
|
> Here goes a silly question. I want to compile dl for an epia motherboard. How are te EPIA motherboards ? I'm looking at them for quite a while now. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Diego T. <dt...@co...> - 2003-10-22 19:00:00
|
On Wed, Oct 22, 2003 at 10:22:34AM -0400, Heiko Zuerker wrote: > > Here goes a silly question. I want to compile dl for an epia motherboard. > > How are te EPIA motherboards ? > I'm looking at them for quite a while now. The new board (CL one) with two network interfaces is the perfect small motherboard. 2 ATA133/6 usb2.0/1 firewire/1Ghz/not-so-bad-AGP-VGA/crappy AC97 sound/very small form factor. I'm going to add a pci prism2.5 board and a little couple of hds (320Gb) so it would be my storage server :) I'll boot it from usb, with dl, of course. The problem with the cpu was that old motherboards didn't support xchg instructions, and many software (like openssl) will fail to run. Because of that, a proper entry has been added to the kernel cpu options. In old kernels, you should build them as 386. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-10-22 16:53:05
|
> > > Here goes a silly question. I want to compile dl for an epia motherboard. > > There is no option to choose from on the build menu. The only available > options are 486,586 and 686. > > This option is for the linux kernel only or its also used as an argument > to the gcc compile of every package? > > Currently i'd need to select the via c3-2 option (the one that shows on > the kernel menuconfig), but there are also other options: > > - "CyrixIII" for VIA Cyrix III or VIA C3. > . > - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above). Currently only the selection of Intel CPUs is possible. You can do the following trick: Let "make build" run until it comes to compiling GCC and then stop it. Go to build/tmp/linux-2.4.22 and change the value in the .config file. This will only change the Kernel, so I would suggest that you select in menuconfig 486. -- Regards Heiko Zuerker http://www.devil-linux.org |
