• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 442 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.

Can't find first base to configure kernel

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

A week or so ago I successfully changed a file to read "CONFIG_VIDEO_TVP514X=y" and got NTSC capture working on my DM6467T EVM.  Today, I can't remember how to do it and I discover my notes to be incomplete.  Searching today, I find reference to the file "davinci_dm646x_1ghz_defconfig" as well as ".config".  I remember making with a "davinci_dm646x_1ghz_defconfig" parameter, and I believe that's the file I changed.  However, it says at the top not to change it by hand but to use some other tool.  Meanwhile, a post I made here earlier says I changed by ".config" file.  Furthermore, I find references to "make menuconfig", which won't run (yet?) on my Ubuntu because ncurses is not installed.

So, please advise me as to where the TOP LEVEL entry point is for properly causing a change to [I believe "davinci_dm646x_1ghz_defconfig"] so that I can selectively choose the TVP5147 for NTSC composite or the TVP7002 for HD component.

Thanks very much,

Helmut

  • 0
    Mastermind 9310 points

    If you want to make a temporary change to your kernel's config, then you can directly edit your ".config" file and rebuild. If you want this change to be part of the default configuration of your platform then you should edit "davinci_dm646x_1ghz_defconfig" which should be located under "arch/arm/configs/".

    The mention on top of ".config" saying that this file has been automatically generated means that is was created by one of the following command : make menuconfig, make xconfig, make XXXX_defconfig, and some others. It means that if you make a permanent change to your config, it is ok to edit  "davinci_dm646x_1ghz_defconfig" and generate ".config" using the command:

    make  davinci_dm646x_1ghz_defconfig

  • 0 in reply to Adeneo Embedded support team
    Mastermind 6805 points

    Thanks for the "it is ok to edit" comment.  

    Note the mention to which I was referring, about the file being automatically generated, was not on the top of the .config file, but on the top of the davinci_dm646x_1ghz_defconfig file.  But you said it's ok to edit it, so I will.  I'll make it my top level source, and keep a backup in case it gets trashed later by accident from some higher top level.

    I see my notes already have "make ARCH=arm davinci_dm646x_1ghz_defconfig" in them, and this worked, so I'll stick with that.  My notes follow with "make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage".  This means I was never 'temporarily' editing .config, but 'permanently' editing davinci_dm646x_1ghz_defconfig.  I can live with this method.

    By the way, where does that .config file live, anyway?  I've been unable to find it.  (Even though I have no need to edit, view, or otherwise use it directly.)

    Thanks again,

    Helmut

     

  • 0 in reply to Helmut Forren
    Mastermind 9310 points

    .config live in your build root directory, basically from where you type the "make" command. It is not present on clean sources, it only gets copied here when you call "make XXXXX_defconfig", make menuconfig, and so on...

    Note that XXX_defconfig files usually get created from a ".config" file, this is probably why you got the "do not edit" mention in your defconfig file.