| | 449 | |
| | 450 | = Creating your own defconfig. |
| | 451 | |
| | 452 | The config files contained in the Gateworks kernel repos generally enable nearly everything or almost nothing. This can be inconvenient if you're looking for a config that represents what's minimally needed while enabling what's necessary for the board to function as it's intended. |
| | 453 | |
| | 454 | For Buildroot we have: [http://dev.gateworks.com/buildroot/ventana/minimal/gwventana_minimal_kernel_defconfig gwventana_minimal_kernel_defconfig] (for Ventana) |
| | 455 | |
| | 456 | This config can be adapted to be used with Ubuntu by disabling CPIO and enabling module support. With this done other features can be added that are specific to your application such as radio or modem support. Configuring the kernel can be an iterative process making it beneficial to create a defconfig once the essential features required have been enabled. |
| | 457 | |
| | 458 | 1. Make the changes required by your application using "make menuconfig", save and exit. |
| | 459 | 1. Execute "make savedefconfig", this will create the file "./defconfig". |
| | 460 | 1. Copy or move this file to "arch/arm/configs" or whatever is appropriate for your platform. |
| | 461 | 1. Rename the file so the filename ends in "_defconfig", for example "filename_defconfig". |
| | 462 | 1. When this config is required, "make distclean" to wipe out the old config and any patches, then "make <filename_defconfig>" |
| | 463 | 1. If required use "make menuconfig" to make additional changes then save. If no changes are required proceed with your build as normal. |
| | 464 | |
| | 465 | == Make HELP |
| | 466 | |
| | 467 | Executing "make help" will provide a complete list of available targets with explanations. This list will also include available defconfigs. |
| | 468 | |
| | 469 | |
