• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 502 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Where's top level point to configure kernel?

Helmut Forren
Mastermind 6805 points
Other Parts Discussed in Thread: TVP5147

I've been advised that it's OK for me to directly modify git/arch/arm/configs/davinci_dm646x_1ghz_defconfig in spite of the fact that the top of this file reads "Automatically generated make config: don't edit".  Well, I could modify it directly, but I'd much rather know where the very top level entry point is intended to be for configuring a kernel.  Obviously, I don't know enough about linux admin to know this already!  As you may have partially deduced, this is for the DM6467T EVM and later my own custom derivation, where I need to include the ADV7170 driver (for ADV7171 NTSC video output) as well as TVP514X driver (for TVP5147 for NTSC video input).

Thanks very much,

Helmut

  • 0
    TI__Mastermind 18260 points

    As I understand it, but not from direct experience...

    The ultimate configuration comes from the .config file at the top level of the kernel source.  When you say, for instance:
        % make davinci_dm646x_1ghz_defconfig
    'make' uses that file (in arch/arm/configs) as the "source" of the config, and after this command the .config file will reflect the configuration in davinci_dm646x_1ghz_defconfig.

    If you want to change it, you run:
        % make menuconfig
    which brings up a curses-based terminal "GUI" for selecting configuration elements.  It probably takes the current .config and renders it in the menuconfig, then you make your changes, and they get saved to .config.  If you want this new configuration to be a "defconfig", you simply copy it to the arch/arm/configs/davinci_dm646x_1ghz_defconfig file.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Mastermind 6805 points

    Rob,

    Thanks for the info.  (I'm suspicious on who's in charge, .config or davinci_dm646x_1ghz_defconfig, but I can figure that out).

    More importantly, I get the error below.  Any advice on how to install ncurses?  It may have come with my git and all I need to do is the correct "make".  It's not "make ncurses" or "make ncurses-devel", however.  Or perhaps it came with the dvsdk?  Not likely.  So, any further advice please?

    Thanks,

    Helmut

     

     *** Unable to find the ncurses libraries or the

     *** required header files.

     *** 'make menuconfig' requires the ncurses libraries.

     *** 

     *** Install ncurses (ncurses-devel) and try again.

     *** 

    make[1]: *** [scripts/kconfig/dochecklxdialog] Error 1

    make: *** [menuconfig] Error 2

  • 0 in reply to Helmut Forren
    TI__Mastermind 18260 points

    Helmut Forren said:

    Thanks for the info.  (I'm suspicious on who's in charge, .config or davinci_dm646x_1ghz_defconfig, but I can figure that out).

    I share your suspicion, since I have in the past modified a defconfig file in arch/arm/configs but failed to see this modification take affect.  I believe I even tried hand-editing .config to no affect, but had success with menuconfig.

    Helmut Forren said:

    More importantly, I get the error below.  Any advice on how to install ncurses?  It may have come with my git and all I need to do is the correct "make".  It's not "make ncurses" or "make ncurses-devel", however.  Or perhaps it came with the dvsdk?  Not likely.  So, any further advice please?

    The ncurses interface is a user-level interface, so it won't be present in your Linux kernel distribution.  However, I'm accustomed to it just "being there" on my development system.  If it's not there, you will need to download and "install" it from the web (and I would expect it to be easy to find).  In this case, the ncurses library is part of your development tools, not part of the target system.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Mastermind 6805 points

    Robert Tivy said:

    Thanks for the info.  (I'm suspicious on who's in charge, .config or davinci_dm646x_1ghz_defconfig, but I can figure that out).

     

    I share your suspicion, since I have in the past modified a defconfig file in arch/arm/configs but failed to see this modification take affect.  I believe I even tried hand-editing .config to no affect, but had success with menuconfig.

    [/quote]

    I have modified the davinci_dm646x_1ghz_defconfig and seen a change.  I've never modified anything else.  I would assume .config comes from davinci_dm646x_1ghz_defconfig, and so davinci_dm646x_1ghz_defconfig "is in charge" between those two.  Then it seems menuconfig "is in charge" of it all, by directly modifying davinci_dm646x_1ghz_defconfig.  I'm just guessing, of course.

    I'll go get ncurses per your suggestion.  (Didn't want to do that until someone else suggested it, just in case it was actually already hiding somewhere.)

    -Helmut