From: Darren Hart <dvhart@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: kernel manual seems to make no mention of "defconfig"
Date: Mon, 07 Jan 2013 08:25:01 -0800 [thread overview]
Message-ID: <50EAF6DD.1050508@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212240629520.5826@oneiric>
On 12/24/2012 04:30 AM, Robert P. J. Day wrote:
> On Sun, 23 Dec 2012, Bruce Ashfield wrote:
>
>>
>>
>>
>> On Sun, Dec 23, 2012 at 11:10 PM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>>
>>
>>
>> On Sun, Dec 23, 2012 at 12:26 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>>
>> poking around kern-tools for purpose of documenting some stuff and
>> ran across this in "updateme":
>>
>> split_command_line_objects() {
>> command_line_values=$@
>>
>> for v in $command_line_values; do
>> v_base=`basename $v`
>> case $v_base in
>> *.scc) migrate_feature $v
>> ;;
>> *.cfg) migrate_cfg $v
>> ;;
>> *.patch|*.diff) migrate_patch $v
>> ;;
>> defconfig) migrate_cfg $v;;
>> *) ;;
>> esac
>> done
>> }
>>
>> AFAICT, there is no mention of a possible "defconfig" entry anywhere
>> in the current yocto kernel manual.
>>
>>
>> You won't find it there because it isn't specific to the kern-tools,
>> what you see there is a small wrapper on top of the kernel.bbclass
>> defconfig handling, with the same end result. So standard
>> yocto/oe-core docs apply here.
>>
>> I also forgot to mention that Darren did cover defconfigs in the
>> yocto kernel docs that were put together for the 1.4 release (I
>> think they were posted here), so there's better / additional
>> coverage upcoming!
>
> ah, i will go back and check those out, thanks. just trying to
> catch up on several days of not reading the list.
They are in the process of being edited by our tech writer as well as
being converted from ascii to docbook. You can see the current state of
them here:
http://www.yoctoproject.org/docs/hart/kernel-dev/kernel-dev.html
See Section 2.2.2 and the sections that follow.
Keep in mind these are being actively worked on, so there are some rough
edges we're working through still.
Thanks,
Darren
>
> rday
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-01-07 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 16:26 kernel manual seems to make no mention of "defconfig" Robert P. J. Day
2012-12-24 3:10 ` Bruce Ashfield
2012-12-24 3:22 ` Bruce Ashfield
2012-12-24 12:30 ` Robert P. J. Day
2013-01-07 16:25 ` Darren Hart [this message]
2013-01-07 19:21 ` Rifenbark, Scott M
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EAF6DD.1050508@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.