From: Darren Hart <dvhart@linux.intel.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Do we have a package that installs the kernel headers and config into the target?
Date: Thu, 05 Apr 2012 23:07:26 -0700 [thread overview]
Message-ID: <4F7E881E.1000106@linux.intel.com> (raw)
In-Reply-To: <A25F549E4D43CD42B4C02DF47A1913230FCFD49B@SHSMSX102.ccr.corp.intel.com>
On 04/05/2012 09:41 PM, Cui, Dexuan wrote:
> Darren Hart wrote on 2012-04-06:
>> On 04/05/2012 08:20 PM, Cui, Dexuan wrote:
>>> In a typical Linux distribution, there is a build link(or directory)
>>> that specifies the directory where the kernel headers and kernel config
>>> are put.
>>>
>>> E.g. in my Ubuntu 11.04, a package linux-headers-2.6.38-8-generic
>> installs .config, include/ and Kconfig into
>> /usr/src/linux-headers-2.6.38-8-generic/ and makes a link
>> /lib/modules/2.6.38-8-generic/build to point to the directory.
>>>
>>> However, looks in Yocto, we don't have such a package? Do we have a
>>> plan to add it?
>>>
>>> I'm asking the question because in the ESDC contest, the students found in
>> Yocto they couldn't build the wifi driver's source code that was
>> downloaded from realtek.com:
>> http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PFid=4
>> 8&Level=5&Conn=4&ProdID=226&DownTypeID=3&GetDown=false&Downloads =true
>>> In Ubuntu, they can build the driver fine.
>>
>> There is an open bug:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1614
>
> Glad to know this is a know bug.
> I personally think it would be pretty nice if we can fix this bug soon
> since the students are being frustrated by this...
>
> And, in the Build Appliance (self-hosted-image) work, we want to
> enable the vmware guest's VMware Tools. This also requires the ability
> to build kernel module in the target.
>
While I understand there are valid use cases, I think this is generally
contrary to workflow of the project. We build the OS, it runs on the
target. This is building a general purpose OS, and then having it build
itself out more. It doesn't feel like an embedded workflow.
That said, there are valid use cases, but I don't consider this a
particularly high priority at the moment. I'm happy to hear other
thoughts on why this should be bumped in prio though.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-04-06 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 3:20 Do we have a package that installs the kernel headers and config into the target? Cui, Dexuan
2012-04-06 3:55 ` Darren Hart
2012-04-06 4:41 ` Cui, Dexuan
2012-04-06 6:07 ` Darren Hart [this message]
2012-04-06 7:48 ` Cui, Dexuan
2012-04-06 11:12 ` Cui, Dexuan
2012-04-06 16:07 ` Darren Hart
2012-04-06 14:11 ` Steve Sakoman
2012-04-06 16:23 ` Darren Hart
2012-04-09 6:43 ` Cui, Dexuan
-- strict thread matches above, loose matches on Subject: below --
2012-04-06 18:03 Daniel Lazzari
2012-04-09 6:48 ` Cui, Dexuan
2012-04-09 9:10 ` Maksym Parkachov
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=4F7E881E.1000106@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=dexuan.cui@intel.com \
--cc=openembedded-core@lists.openembedded.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.