Date   

Re: [PATCH 2/3] beagleboard: xserver-kdrive xorg.conf installation

Darren Hart <dvhart@...>
 

On 06/18/2011 08:09 AM, Koen Kooi wrote:

Op 18 jun 2011, om 17:02 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:05 AM, Koen Kooi wrote:

Op 18 jun 2011, om 02:35 heeft Darren Hart het volgende
geschreven:

Append xserver-kdrive to allow for BSP specific xorg.conf
files. This also appears to drag in a runtime dependency on
libhal, so add that to the bbappend's RDEPENDS_${PN} as well.
Since when does kdrive use xorg.conf?
This is my first use of xserver-kdrive. I was experimenting with
xorg.conf changes to resolve some USB input issues I was having...
it seemed to work. Should it be using something else?
AFAIK kdrive doesn't read xorg.conf, one of its design principles :)
That's we have all those x*-common scripts that start Xfbdev with a
gazillion commandline options.
Taking a closer look, I'm wondering if it is the xkeyboard-config
package that is reading xorg.conf. Installing this seems a bit at odds
with what I've been able to dig up about xserver-kdrive. I also noticed
the beagleboard.conf in meta-ti use xserver-xorg, not kdrive.

With that information, I'm building a new image using the XSERVER
preferences from the meta-ti beagleboard conf.

Any objections to moving beagleboard to xserver-xorg instead of kdrive?
I'd like us not to diverge from meta-ti without a very good reason.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Koen Kooi
 

Op 20 jun 2011, om 21:46 heeft Bruce Ashfield het volgende geschreven:

On 06/18/11 12:32, Koen Kooi wrote:

Op 18 jun 2011, om 18:09 heeft Bruce Ashfield het volgende geschreven:

On 11-06-18 11:13 AM, Koen Kooi wrote:

Op 18 jun 2011, om 17:10 heeft Koen Kooi het volgende geschreven:


Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart<dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)
Speaking of .39, is there a 'linux-yocto' type of tree for .39 mainline with a skeleton for machine support? If there is, I'd like to fork it to see if it can improve my current workflow which consist of self written scripts that emulate guilt.
I've got the linux-yocto-dev recipe in poky-extras, meta-kernel-dev
layer. That recipe tracked 2.6.39, and has now jumped to 3.0 (with
a minor cheat as I work through the 3.0 naming issues). The kernel
repo is hosted on git.yoctoproject.org as the linux-yocto-dev repo.

The repo is fast forward for a given version, and then is re-generated
when I jump it from version to version. I carry forward all the existing
patches and keep the qemu machines working. Although at the moment,
qemuppc is losing interrupts and can't get past init :)

That's also the repo where I'm testing out some changes to kern-tools
(but they are stable), which will show up shortly.
Thanks, I'll have a look at that. Is there already some doc out on how to create such a structure from scratch?
At the moment, they are carried forward from kernel version
to kernel version and then interpreted by the tools. But I
do have some notes and other information that describe how to
take upstream tree <foo>, feed it a kernel-cache (what you see
in the meta branch) and create a new kernel tree ready to
build.

I've got to get a bit of 3.0-rcX behind me, but I'm writing this
up and will contribute it, if that's what you are thinking
of here.
That's exactly what I'm thinking of!


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Bruce Ashfield <bruce.ashfield@...>
 

On 06/18/11 12:32, Koen Kooi wrote:

Op 18 jun 2011, om 18:09 heeft Bruce Ashfield het volgende geschreven:

On 11-06-18 11:13 AM, Koen Kooi wrote:

Op 18 jun 2011, om 17:10 heeft Koen Kooi het volgende geschreven:


Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart<dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)
Speaking of .39, is there a 'linux-yocto' type of tree for .39 mainline with a skeleton for machine support? If there is, I'd like to fork it to see if it can improve my current workflow which consist of self written scripts that emulate guilt.
I've got the linux-yocto-dev recipe in poky-extras, meta-kernel-dev
layer. That recipe tracked 2.6.39, and has now jumped to 3.0 (with
a minor cheat as I work through the 3.0 naming issues). The kernel
repo is hosted on git.yoctoproject.org as the linux-yocto-dev repo.

The repo is fast forward for a given version, and then is re-generated
when I jump it from version to version. I carry forward all the existing
patches and keep the qemu machines working. Although at the moment,
qemuppc is losing interrupts and can't get past init :)

That's also the repo where I'm testing out some changes to kern-tools
(but they are stable), which will show up shortly.
Thanks, I'll have a look at that. Is there already some doc out on how to create such a structure from scratch?
At the moment, they are carried forward from kernel version
to kernel version and then interpreted by the tools. But I
do have some notes and other information that describe how to
take upstream tree <foo>, feed it a kernel-cache (what you see
in the meta branch) and create a new kernel tree ready to
build.

I've got to get a bit of 3.0-rcX behind me, but I'm writing this
up and will contribute it, if that's what you are thinking
of here.

Cheers,

Bruce


Re: the yocto under archlinux

Yury Bushmelev <jay4mail@...>
 

2011/6/20 NiQingliang <niqingliang@...>:
Hello,

Is there someone using archlinux?
Under archlinux, the "env python" is pointing to python3, which result
in the bitbake's failure.

What I can do?

I want use "env python=python2", but it doesn't work.
I'm OpenEmbedded user but this case is similar.
OE wiki have solution on "OE and your distro" page, but seems OE
website is inaccessible now.

I'm just using lxc container with Debian 6.0 inside. This is more
stable solution :)

--
Yury Bushmelev


Re: configure optimization feature update

Esben Haabendal <eha@...>
 

Koen Kooi <koen@...> writes:

Yes. OE-lite: http://oe-lite.org

And it works so well, that I cannot understand why OE do not have a plan
for how to achieve the same.
So why not send a patch to make OE-core have per recipe staging?
Several good/bad reasons:

1. Communications so far has been rather clear that OE does not want
this kind of change, at least not at this point in time.

2. Implementing per recipe staging in OE-core, without dropping vital
features of OE (most prominently package feeds) requires additional work
that I do not have the manpower to do, nor any particular motivation
given that chances of acceptance seems so low.

So for now, all I can do is to raise attention to the benefits of doing
per recipe staging sometime in the future, hoping to inspire some people
to be willing to help get there.

Given the current community/project situation around OE, an undertaking
like this does not seem feasible within OE without YP behind it.

/Esben


Re: configure optimization feature update

Koen Kooi
 

Op 20 jun 2011, om 06:53 heeft Esben Haabendal het volgende geschreven:

On Sun, 2011-06-19 at 16:49 -0700, Khem Raj wrote:
On Sun, Jun 19, 2011 at 1:02 PM, Esben Haabendal
<eha@...> wrote:
On Wed, 2011-06-15 at 18:28 -0700, Khem Raj wrote:
On Wed, Jun 15, 2011 at 5:57 PM, Xu, Dongxiao <dongxiao.xu@...> wrote:
Hi Richard,

Recently I was doing the "configure optimization" feature and collecting data for it.

The main logic of this feature is straight forward:

1. Use the diff file as autoreconf cache. (I use command: "diff -ruN SOURCE-ORIG SOURCE", here "SOURCE-ORIG" is the source directory before running autoreconf, while "SOURCE" is the directory after running autoreconf).
2. Add SRC_URI checksum for all patches of the source code.
3. Tag each autoreconf cache file with ${PN} and the SRC_URI checksum of source code and all patches.
4. If the currently SRC_URI checksum matches the cached checksum, then we can patch the cache instead of running "autoreconf" stage.
The autoconf'ing is sort of arbitrary at the moment. Depending on what
is staged the results may vary.
Which can be properly fixed by using per-recipe (per-workdir) staging.
you seem to be stuck in this tight while(1) loop
per recipe staging is not panacea
Well, panacea is a very strong work. But per recipe staging does
improve build reproducability and reliability quite a bit. As for what
it is not, I think you might want to try it before speaking to strongly
against it.

Do you have some prototypes ?
Yes. OE-lite: http://oe-lite.org

And it works so well, that I cannot understand why OE do not have a plan
for how to achieve the same.
So why not send a patch to make OE-core have per recipe staging?


the yocto under archlinux

niqingliang
 

Hello,

Is there someone using archlinux?
Under archlinux, the "env python" is pointing to python3, which result
in the bitbake's failure.

What I can do?

I want use "env python=python2", but it doesn't work.

THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@...
BLOG: http://niqingliang2003.wordpress.com


Re: configure optimization feature update

Esben Haabendal <eha@...>
 

On Sun, 2011-06-19 at 16:49 -0700, Khem Raj wrote:
On Sun, Jun 19, 2011 at 1:02 PM, Esben Haabendal
<eha@...> wrote:
On Wed, 2011-06-15 at 18:28 -0700, Khem Raj wrote:
On Wed, Jun 15, 2011 at 5:57 PM, Xu, Dongxiao <dongxiao.xu@...> wrote:
Hi Richard,

Recently I was doing the "configure optimization" feature and collecting data for it.

The main logic of this feature is straight forward:

1. Use the diff file as autoreconf cache. (I use command: "diff -ruN SOURCE-ORIG SOURCE", here "SOURCE-ORIG" is the source directory before running autoreconf, while "SOURCE" is the directory after running autoreconf).
2. Add SRC_URI checksum for all patches of the source code.
3. Tag each autoreconf cache file with ${PN} and the SRC_URI checksum of source code and all patches.
4. If the currently SRC_URI checksum matches the cached checksum, then we can patch the cache instead of running "autoreconf" stage.
The autoconf'ing is sort of arbitrary at the moment. Depending on what
is staged the results may vary.
Which can be properly fixed by using per-recipe (per-workdir) staging.
you seem to be stuck in this tight while(1) loop
per recipe staging is not panacea
Well, panacea is a very strong work. But per recipe staging does
improve build reproducability and reliability quite a bit. As for what
it is not, I think you might want to try it before speaking to strongly
against it.

Do you have some prototypes ?
Yes. OE-lite: http://oe-lite.org

And it works so well, that I cannot understand why OE do not have a plan
for how to achieve the same. I hope you are able to accept this
pointers to when per-recipe staging would help you in a positive manner.
But if OE community and YP as a whole would rather not hear anymore
about it, just say so.

where you can control what staging is presented
and its like beaning coffee when it comes to autoconf options.
I am not sure about the coffee part, but as it specifically creates a
staging dir in each workdir, autoconf results is not influenced by
anything else than the recipe meta-data and it's dependencies. There is
no shared "state" between recipes/builds.

/Esben


Re: configure optimization feature update

Khem Raj
 

On Sun, Jun 19, 2011 at 1:02 PM, Esben Haabendal
<eha@...> wrote:
On Wed, 2011-06-15 at 18:28 -0700, Khem Raj wrote:
On Wed, Jun 15, 2011 at 5:57 PM, Xu, Dongxiao <dongxiao.xu@...> wrote:
Hi Richard,

Recently I was doing the "configure optimization" feature and collecting data for it.

The main logic of this feature is straight forward:

1. Use the diff file as autoreconf cache. (I use command: "diff -ruN SOURCE-ORIG SOURCE", here "SOURCE-ORIG" is the source directory before running autoreconf, while "SOURCE" is the directory after running autoreconf).
2. Add SRC_URI checksum for all patches of the source code.
3. Tag each autoreconf cache file with ${PN} and the SRC_URI checksum of source code and all patches.
4. If the currently SRC_URI checksum matches the cached checksum, then we can patch the cache instead of running "autoreconf" stage.
The autoconf'ing is sort of arbitrary at the moment. Depending on what
is staged the results may vary.
Which can be properly fixed by using per-recipe (per-workdir) staging.
you seem to be stuck in this tight while(1) loop per recipe staging is
not panacea
Do you have some prototypes ? where you can control what staging is presented
and its like beaning coffee when it comes to autoconf options.


/Esben


Re: configure optimization feature update

Esben Haabendal <eha@...>
 

On Wed, 2011-06-15 at 18:28 -0700, Khem Raj wrote:
On Wed, Jun 15, 2011 at 5:57 PM, Xu, Dongxiao <dongxiao.xu@...> wrote:
Hi Richard,

Recently I was doing the "configure optimization" feature and collecting data for it.

The main logic of this feature is straight forward:

1. Use the diff file as autoreconf cache. (I use command: "diff -ruN SOURCE-ORIG SOURCE", here "SOURCE-ORIG" is the source directory before running autoreconf, while "SOURCE" is the directory after running autoreconf).
2. Add SRC_URI checksum for all patches of the source code.
3. Tag each autoreconf cache file with ${PN} and the SRC_URI checksum of source code and all patches.
4. If the currently SRC_URI checksum matches the cached checksum, then we can patch the cache instead of running "autoreconf" stage.
The autoconf'ing is sort of arbitrary at the moment. Depending on what
is staged the results may vary.
Which can be properly fixed by using per-recipe (per-workdir) staging.

/Esben


Yocto weekly bug trend charts -- WW25

Xu, Jiajun <jiajun.xu@...>
 

Hi all,
The open bug number of last week increased to 221. And the weight number of all open bugs increased to 887. QA recovered weekly testing for upstream. Bug status of WW25 could be found on https://wiki.pokylinux.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Koen Kooi
 

Op 18 jun 2011, om 18:09 heeft Bruce Ashfield het volgende geschreven:

On 11-06-18 11:13 AM, Koen Kooi wrote:

Op 18 jun 2011, om 17:10 heeft Koen Kooi het volgende geschreven:


Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart<dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)
Speaking of .39, is there a 'linux-yocto' type of tree for .39 mainline with a skeleton for machine support? If there is, I'd like to fork it to see if it can improve my current workflow which consist of self written scripts that emulate guilt.
I've got the linux-yocto-dev recipe in poky-extras, meta-kernel-dev
layer. That recipe tracked 2.6.39, and has now jumped to 3.0 (with
a minor cheat as I work through the 3.0 naming issues). The kernel
repo is hosted on git.yoctoproject.org as the linux-yocto-dev repo.

The repo is fast forward for a given version, and then is re-generated
when I jump it from version to version. I carry forward all the existing
patches and keep the qemu machines working. Although at the moment,
qemuppc is losing interrupts and can't get past init :)

That's also the repo where I'm testing out some changes to kern-tools
(but they are stable), which will show up shortly.
Thanks, I'll have a look at that. Is there already some doc out on how to create such a structure from scratch?


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Bruce Ashfield <bruce.ashfield@...>
 

On 11-06-18 11:13 AM, Koen Kooi wrote:

Op 18 jun 2011, om 17:10 heeft Koen Kooi het volgende geschreven:


Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart<dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)
Speaking of .39, is there a 'linux-yocto' type of tree for .39 mainline with a skeleton for machine support? If there is, I'd like to fork it to see if it can improve my current workflow which consist of self written scripts that emulate guilt.
I've got the linux-yocto-dev recipe in poky-extras, meta-kernel-dev
layer. That recipe tracked 2.6.39, and has now jumped to 3.0 (with
a minor cheat as I work through the 3.0 naming issues). The kernel
repo is hosted on git.yoctoproject.org as the linux-yocto-dev repo.

The repo is fast forward for a given version, and then is re-generated
when I jump it from version to version. I carry forward all the existing
patches and keep the qemu machines working. Although at the moment,
qemuppc is losing interrupts and can't get past init :)

That's also the repo where I'm testing out some changes to kern-tools
(but they are stable), which will show up shortly.

Cheers,

Bruce




Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Koen Kooi
 

Op 18 jun 2011, om 17:10 heeft Koen Kooi het volgende geschreven:


Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart <dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)
Speaking of .39, is there a 'linux-yocto' type of tree for .39 mainline with a skeleton for machine support? If there is, I'd like to fork it to see if it can improve my current workflow which consist of self written scripts that emulate guilt.


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Koen Kooi
 

Op 18 jun 2011, om 17:08 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart <dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.
The .37 isn't used, developed or supported for beagleboard anymore, .39 is all the rage now :)


Re: [PATCH 2/3] beagleboard: xserver-kdrive xorg.conf installation

Koen Kooi
 

Op 18 jun 2011, om 17:02 heeft Darren Hart het volgende geschreven:



On 06/18/2011 01:05 AM, Koen Kooi wrote:

Op 18 jun 2011, om 02:35 heeft Darren Hart het volgende geschreven:

Append xserver-kdrive to allow for BSP specific xorg.conf files. This also
appears to drag in a runtime dependency on libhal, so add that to the
bbappend's RDEPENDS_${PN} as well.
Since when does kdrive use xorg.conf?
This is my first use of xserver-kdrive. I was experimenting with
xorg.conf changes to resolve some USB input issues I was having... it
seemed to work. Should it be using something else?
AFAIK kdrive doesn't read xorg.conf, one of its design principles :) That's we have all those x*-common scripts that start Xfbdev with a gazillion commandline options.


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Darren Hart <dvhart@...>
 

On 06/18/2011 01:11 AM, Koen Kooi wrote:

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart <dvhart@...>

The following commits have been pulled in from the meta-ti
linux-omap_2.6.37 recipe, with the exception of: USB: ehci: remove
structure packing from ehci_def which hails from mainline and
should be applied to yocto/base, while the rest should be applied
to yocto/standard/beagleboard.

Fixes [YOCTO #764] Fixes [YOCTO #765] Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37
recipe and significantly improves Beagleboard support in
linux-yocto. As there are 115 patches in total, and none of them
are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from
37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So
basically leave out the patches in the 'linus' directory.
There were about 200 patches in total, I've removed all those that
reverse applied and failed do to a conflict that was obviously a merge
of a very similar patch. That accounted for most of the 37-rc[78] to 37
patches from the linus directory.

The camera
interface also doesn't work, so the 'media' directory can be left out
as well.
The goal was to stay as close to the meta-ti/linux-omap_2.6.37 recipe as
possible with the linux-yocto kernel repository. Will you be removing
all of the media directory from there as well? I don't want to remove
them from here if you'll be *adding* to them there. However, if you'll
be sure to just be replacing them there, then I can drop them here.

--
Darren



The following changes since commit
9cb5c3fb1634e541cacceeb8c8cabe88afa5b080:

Merge branch 'yocto/standard/base' into yocto/standard/beagleboard
(2011-06-06 10:35:20 -0400)

are available in the git repository at:

git://git.yoctoproject.org/linux-yocto-2.6.37-contrib
dvhart/yocto/standard/beagleboard
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/yocto/standard/beagleboard


Alexander Holler (1):
arm: omap3: beagle: Ensure msecure is mux'd to be able to set the
RTC

Antti Koskipaa (1): v4l: v4l2_subdev userspace crop API

Arik Nemtsov (1): wl12xx: Read MAC address from NVS file on HW
startup

Darren Hart (2): board-omap3beagle: whitespace cleanup
board-omap3beagle: allow for building without wl1271

Eliad Peller (1): wl1271: set wl->vif only if add_interface
succeeded.

Florian Westphal (1): bridge: stp: ensure mac header is set

Jesper Juhl (1): ISDN, Gigaset: Fix memory leak in
do_disconnect_req()

Juuso Oikarinen (1): wl12xx: Unset bssid filter, ssid and bssid
from firmware on disassoc

Kevin Hilman (1): OMAP: CPUfreq: ensure policy is fully
initialized

Koen Kooi (10): omap3: beaglexm: fix DVI reset GPIO omap3:
beaglexm: fix power on of DVI ARM: OMAP: beagleboard: Add
infrastructure to do fixups based on expansionboard name passed by
u-boot ARM: OMAP: beagleboard: pre-export GPIOs to userspace when
using a Tincantools trainerboard modedb.c: add proper 720p60 mode
ARM: OMAP: add omap_rev_* macros omap3: beagleboard: add WIP
support for beagleboardtoys WL12xx board beagleboard: hack in
support from xM rev C omap3: allow 1GHz mpurates BeagleBoard:
Adjust USER button pin for xM

Laurent Pinchart (35): v4l: Share code between video_usercopy and
video_ioctl2 v4l: subdev: Don't require core operations v4l:
subdev: Merge v4l2_i2c_new_subdev_cfg and v4l2_i2c_new_subdev v4l:
subdev: Add device node support v4l: subdev: Uninline the
v4l2_subdev_init function v4l: subdev: Control ioctls support
media: Media device node support media: Media device media:
Entities, pads and links media: Entity use count media: Media
device information query media: Entities, pads and links
enumeration media: Links setup media: Pipelines and media streams
v4l: Add a media_device pointer to the v4l2_device structure v4l:
Make video_device inherit from media_entity v4l: Make v4l2_subdev
inherit from media_entity v4l: Move the media/v4l2-mediabus.h
header to include/linux v4l: Replace enums with fixed-sized fields
in public structure v4l: Rename V4L2_MBUS_FMT_GREY8_1X8 to
V4L2_MBUS_FMT_Y8_1X8 v4l: Group media bus pixel codes by types and
sort them alphabetically v4l: subdev: Add a new file operations
class v4l: v4l2_subdev pad-level operations v4l: v4l2_subdev
userspace format API v4l: v4l2_subdev userspace frame interval API
v4l: subdev: Generic ioctl support v4l: Add subdev sensor
g_skip_frames operation v4l: Include linux/videodev2.h in
media/v4l2-ctrls.h v4l: Fix a use-before-set in the control
framework v4l: Add 8-bit YUYV on 16-bit bus and SGRBG10 media bus
pixel codes v4l: Add remaining RAW10 patterns w DPCM pixel code
variants v4l: Add missing 12 bits bayer media bus formats v4l: Add
12 bits bayer pixel formats omap3: Add function to register
omap3isp platform device structure OMAP3 ISP driver

Lennert Buytenhek (1): ARM: pxa: PXA_ESERIES depends on FB_W100.

Manjunatha Halli (7): drivers:media:radio: wl128x: FM Driver common
header file drivers:media:radio: wl128x: FM Driver V4L2 sources
drivers:media:radio: wl128x: FM Driver Common sources
drivers:media:radio: wl128x: FM driver RX sources
drivers:media:radio: wl128x: FM driver TX sources
drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driver
drivers:media:radio: Update Kconfig and Makefile for wl128x FM
driver.

Nishanth Menon (2): omap3|4: opp: make omapx_opp_init non-static
OMAP3: beagle xm: enable upto 1GHz OPP

Pavan Savoy (2): drivers:misc:ti-st: change protocol parse logic
Bluetooth: btwilink driver

Peter 'p2' De Schrijver (1): OMAP: CPUfreq: ensure driver
initializes after cpufreq framework and governors

Rabin Vincent (1): USB: ehci: remove structure packing from
ehci_def

Rajendra Nayak (1): OMAP3 PM: CPUFreq driver for OMAP3

Robert Nelson (2): omap: Beagle: detect new xM revision B xM audio
fix from Ashok

Sakari Ailus (2): v4l: subdev: Events support media: Entity graph
traversal

Sanjeev Premi (1): omap3: Add basic support for 720MHz part

Sergio Aguirre (2): omap3: Remove unusued ISP CBUFF resource omap2:
Fix camera resources for multiomap

Shahar Levi (3): wl1271: 11n Support, Add Definitions wl1271: 11n
Support, ACX Commands wl1271: 11n Support, functionality and
configuration ability

Silesh C V (1): OMAP: PM: CPUFREQ: Fix conditional compilation

Stanimir Varbanov (1): v4l: Create v4l2 subdev file handle
structure

Steve Sakoman (18): mmc: don't display single block read console
messages MTD: silence ecc errors on mtdblock0 OMAP: DSS2: enable
hsclk in dsi_pll_init for OMAP36XX drivers: net: smsc911x: return
ENODEV if device is not found drivers: input: touchscreen: ads7846:
return ENODEV if device is not found ASoC: enable audio capture by
default for twl4030 MFD: enable madc clock MFD: add twl4030 madc
driver ARM: OMAP: Add twl4030 madc support to Overo ARM: OMAP: Add
twl4030 madc support to Beagle OMAP: DSS2: Add support for Samsung
LTE430WQ-F0C panel OMAP: DSS2: Add support for LG Philips LB035Q02
panel OMAP: DSS2: add bootarg for selecting svideo or composite for
tv output ARM: OMAP2: mmc-twl4030: move clock input selection prior
to vcc test RTC: add support for backup battery recharge ARM: OMAP:
automatically set musb mode in platform data based on CONFIG
options OMAP: DSS2: check for both cpu type and revision, rather
than just revision OMAP: DSS2: Add DSS2 support for Overo

Thara Gopinath (13): OMAP3: PM: Adding T2 enabling of smartreflex
OMAP: Introduce a user list for each voltage domain instance in
the voltage driver. OMAP: Introduce API in the OPP layer to find
the opp entry corresponding to a voltage. OMAP: Introduce API to
register a device with a voltagedomain OMAP: Introduce device
specific set rate and get rate in omap_device structure OMAP:
Voltage layer changes to support DVFS. OMAP: Introduce dependent
voltage domain support. OMAP: Introduce device scale OMAP: Disable
smartreflex across DVFS OMAP3: Introduce custom set rate and get
rate APIs for scalable devices OMAP3: Update cpufreq driver to use
the new set_rate API OMAP3: Introduce voltage domain info in the
hwmod structures. OMAP3: Add voltage dependency table for VDD1.

Thomas Weber (1): OMAP: Enable Magic SysRq on serial console ttyOx

Tuukka Toivonen (1): ARM: OMAP3: Update Camera ISP definitions for
OMAP3630

Documentation/ABI/testing/sysfs-bus-media | 6 +
Documentation/DocBook/Makefile | 5 +-
Documentation/DocBook/media-entities.tmpl | 50 +
Documentation/DocBook/media.tmpl | 3 +
Documentation/DocBook/v4l/dev-subdev.xml | 307 +++
Documentation/DocBook/v4l/media-controller.xml | 89 +
Documentation/DocBook/v4l/media-func-close.xml | 59 +
Documentation/DocBook/v4l/media-func-ioctl.xml | 116 +
Documentation/DocBook/v4l/media-func-open.xml | 94 +
.../DocBook/v4l/media-ioc-device-info.xml | 133 ++
.../DocBook/v4l/media-ioc-enum-entities.xml | 308 +++
Documentation/DocBook/v4l/media-ioc-enum-links.xml | 207 ++
Documentation/DocBook/v4l/media-ioc-setup-link.xml | 93 +
Documentation/DocBook/v4l/subdev-formats.xml | 2467
++++++++++++++++++++ Documentation/DocBook/v4l/v4l2.xml
| 7 + Documentation/DocBook/v4l/vidioc-streamon.xml | 9
+ .../v4l/vidioc-subdev-enum-frame-interval.xml | 146 ++
.../DocBook/v4l/vidioc-subdev-enum-frame-size.xml | 148 ++
.../DocBook/v4l/vidioc-subdev-enum-mbus-code.xml | 113 +
Documentation/DocBook/v4l/vidioc-subdev-g-crop.xml | 149 ++
Documentation/DocBook/v4l/vidioc-subdev-g-fmt.xml | 174 ++
.../DocBook/v4l/vidioc-subdev-g-frame-interval.xml | 135 ++
Documentation/media-framework.txt | 353 +++
Documentation/video4linux/v4l2-framework.txt | 129 +-
arch/arm/mach-omap2/board-omap3beagle.c | 409 ++++-
arch/arm/mach-omap2/board-overo.c | 247 ++-
arch/arm/mach-omap2/clock.h | 14 +-
arch/arm/mach-omap2/clock34xx.c | 2 +
arch/arm/mach-omap2/control.h | 7 +
arch/arm/mach-omap2/devices.c | 64 +-
arch/arm/mach-omap2/devices.h | 17 +
arch/arm/mach-omap2/hsmmc.c | 14 +-
arch/arm/mach-omap2/id.c | 10 +
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 3 +
arch/arm/mach-omap2/omap_twl.c | 16 +
arch/arm/mach-omap2/opp3xxx_data.c | 66 +-
arch/arm/mach-omap2/opp4xxx_data.c | 3 +-
arch/arm/mach-omap2/pm.c | 110 +
arch/arm/mach-omap2/voltage.c | 369 +++-
arch/arm/mach-pxa/Kconfig | 1 +
arch/arm/plat-omap/clock.c | 2 +-
arch/arm/plat-omap/cpu-omap.c | 38 +-
arch/arm/plat-omap/include/plat/cpu.h | 57 +
arch/arm/plat-omap/include/plat/omap34xx.h | 16 +-
arch/arm/plat-omap/include/plat/omap_device.h | 12 +-
arch/arm/plat-omap/include/plat/voltage.h | 20 +
arch/arm/plat-omap/omap_device.c | 139 ++
block/blk-core.c | 7 +-
drivers/base/power/opp.c | 28 +
drivers/bluetooth/Kconfig | 10 +
drivers/bluetooth/Makefile | 1 +
drivers/bluetooth/btwilink.c | 397 ++++
drivers/input/touchscreen/ads7846.c | 13 +-
drivers/isdn/gigaset/capi.c | 1 +
drivers/media/Kconfig | 22 +
drivers/media/Makefile | 10 +-
drivers/media/media-device.c | 382 +++
drivers/media/media-devnode.c | 321 +++
drivers/media/media-entity.c | 536 +++++
drivers/media/radio/Kconfig | 3 +
drivers/media/radio/Makefile | 1 +
drivers/media/radio/radio-si4713.c | 2 +-
drivers/media/radio/wl128x/Kconfig | 17 +
drivers/media/radio/wl128x/Makefile | 6 +
drivers/media/radio/wl128x/fmdrv.h | 244 ++
drivers/media/radio/wl128x/fmdrv_common.c | 1677
+++++++++++++ drivers/media/radio/wl128x/fmdrv_common.h |
402 ++++ drivers/media/radio/wl128x/fmdrv_rx.c | 847
+++++++ drivers/media/radio/wl128x/fmdrv_rx.h | 59
+ drivers/media/radio/wl128x/fmdrv_tx.c | 425 ++++
drivers/media/radio/wl128x/fmdrv_tx.h | 37 +
drivers/media/radio/wl128x/fmdrv_v4l2.c | 580 +++++
drivers/media/radio/wl128x/fmdrv_v4l2.h | 33 +
drivers/media/video/Kconfig | 13 +
drivers/media/video/Makefile | 4 +-
drivers/media/video/cafe_ccic.c | 11 +-
drivers/media/video/davinci/vpfe_capture.c | 2 +-
drivers/media/video/davinci/vpif_capture.c | 2 +-
drivers/media/video/davinci/vpif_display.c | 2 +-
drivers/media/video/isp/Makefile | 13 +
drivers/media/video/isp/cfa_coef_table.h | 601 +++++
drivers/media/video/isp/gamma_table.h | 90 +
drivers/media/video/isp/isp.c | 2221
++++++++++++++++++ drivers/media/video/isp/isp.h
| 427 ++++ drivers/media/video/isp/ispccdc.c |
2280 ++++++++++++++++++ drivers/media/video/isp/ispccdc.h
| 223 ++ drivers/media/video/isp/ispccp2.c | 1189
++++++++++ drivers/media/video/isp/ispccp2.h |
101 + drivers/media/video/isp/ispcsi2.c | 1332
+++++++++++ drivers/media/video/isp/ispcsi2.h |
169 ++ drivers/media/video/isp/ispcsiphy.c | 247
++ drivers/media/video/isp/ispcsiphy.h | 74 +
drivers/media/video/isp/isph3a.h | 117 +
drivers/media/video/isp/isph3a_aewb.c | 374 +++
drivers/media/video/isp/isph3a_af.c | 429 ++++
drivers/media/video/isp/isphist.c | 520 ++++
drivers/media/video/isp/isphist.h | 40 +
drivers/media/video/isp/isppreview.c | 2120
+++++++++++++++++ drivers/media/video/isp/isppreview.h
| 214 ++ drivers/media/video/isp/ispqueue.c | 1136
+++++++++ drivers/media/video/isp/ispqueue.h | 185
++ drivers/media/video/isp/ispreg.h | 1589
+++++++++++++ drivers/media/video/isp/ispresizer.c |
1710 ++++++++++++++ drivers/media/video/isp/ispresizer.h
| 150 ++ drivers/media/video/isp/ispstat.c | 1100
+++++++++ drivers/media/video/isp/ispstat.h | 169
++ drivers/media/video/isp/ispvideo.c | 1264
++++++++++ drivers/media/video/isp/ispvideo.h |
202 ++ drivers/media/video/isp/luma_enhance_table.h | 154
++ drivers/media/video/isp/noise_filter_table.h | 90 +
drivers/media/video/ivtv/ivtv-i2c.c | 11 +-
drivers/media/video/mt9m001.c | 2 +-
drivers/media/video/mt9v022.c | 4 +-
drivers/media/video/ov6650.c | 10 +-
drivers/media/video/s5p-fimc/fimc-capture.c | 2 +-
drivers/media/video/sh_mobile_csi2.c | 6 +-
drivers/media/video/sh_vou.c | 2 +-
drivers/media/video/soc_camera.c | 2 +-
drivers/media/video/soc_mediabus.c | 2 +-
drivers/media/video/v4l2-common.c | 22 +-
drivers/media/video/v4l2-ctrls.c | 2 +-
drivers/media/video/v4l2-dev.c | 76 +-
drivers/media/video/v4l2-device.c | 66 +-
drivers/media/video/v4l2-ioctl.c | 216 +--
drivers/media/video/v4l2-subdev.c | 346 +++
drivers/mfd/Kconfig | 21 +
drivers/mfd/Makefile | 1 +
drivers/mfd/twl-core.c | 8 +
drivers/mfd/twl4030-madc.c | 537 +++++
drivers/misc/ti-st/st_core.c | 355 +--
drivers/misc/ti-st/st_kim.c | 56 +-
drivers/mmc/card/block.c | 4 +-
drivers/mtd/nand/nand_ecc.c | 2 +-
drivers/net/smsc911x.c | 4 +-
drivers/net/wireless/wl12xx/Kconfig | 10 +
drivers/net/wireless/wl12xx/wl1271.h | 11 +-
drivers/net/wireless/wl12xx/wl1271_acx.c | 83 +
drivers/net/wireless/wl12xx/wl1271_acx.h | 86 +
drivers/net/wireless/wl12xx/wl1271_main.c | 161 +-
drivers/net/wireless/wl12xx/wl1271_rx.c | 6 +
drivers/net/wireless/wl12xx/wl1271_tx.c | 11 +
drivers/rtc/rtc-twl.c | 25 +
drivers/serial/omap-serial.c | 4 +
drivers/video/modedb.c | 4 +
drivers/video/omap2/displays/Kconfig | 12 +
drivers/video/omap2/displays/Makefile | 2 +
.../omap2/displays/panel-lgphilips-lb035q02.c | 244 ++
.../omap2/displays/panel-samsung-lte430wq-f0c.c | 154 ++
drivers/video/omap2/dss/dispc.c | 4 +-
drivers/video/omap2/dss/dpi.c | 7 +-
drivers/video/omap2/dss/venc.c | 22 +
drivers/video/omap2/omapfb/omapfb-main.c | 10 +-
fs/buffer.c | 3 +-
include/linux/Kbuild | 4 +
include/linux/i2c/twl.h | 1 +
include/linux/i2c/twl4030-madc.h | 130 +
include/linux/media.h | 132 ++
include/linux/omap3isp.h | 631 +++++
include/linux/opp.h | 8 +
include/linux/ti_wilink_st.h | 40 +-
include/linux/usb/ehci_def.h | 6 +-
include/linux/v4l2-mediabus.h | 108 +
include/linux/v4l2-subdev.h | 141 ++
include/linux/videodev2.h | 4 +
include/media/media-device.h | 95 +
include/media/media-devnode.h | 97 +
include/media/media-entity.h | 147 ++
include/media/soc_mediabus.h | 3 +-
include/media/v4l2-common.h | 18 +-
include/media/v4l2-ctrls.h | 1 +
include/media/v4l2-dev.h | 25 +-
include/media/v4l2-device.h | 4 +
include/media/v4l2-ioctl.h | 3 +
include/media/v4l2-mediabus.h | 61 +-
include/media/v4l2-subdev.h | 120 +-
net/bridge/br_stp_bpdu.c | 2 +
sound/soc/codecs/twl4030.c | 4 +-
sound/soc/omap/omap-mcbsp.c | 3 + 178
files changed, 37220 insertions(+), 745 deletions(-) create mode
100644 Documentation/ABI/testing/sysfs-bus-media create mode 100644
Documentation/DocBook/v4l/dev-subdev.xml create mode 100644
Documentation/DocBook/v4l/media-controller.xml create mode 100644
Documentation/DocBook/v4l/media-func-close.xml create mode 100644
Documentation/DocBook/v4l/media-func-ioctl.xml create mode 100644
Documentation/DocBook/v4l/media-func-open.xml create mode 100644
Documentation/DocBook/v4l/media-ioc-device-info.xml create mode
100644 Documentation/DocBook/v4l/media-ioc-enum-entities.xml create
mode 100644 Documentation/DocBook/v4l/media-ioc-enum-links.xml
create mode 100644
Documentation/DocBook/v4l/media-ioc-setup-link.xml create mode
100644 Documentation/DocBook/v4l/subdev-formats.xml create mode
100644
Documentation/DocBook/v4l/vidioc-subdev-enum-frame-interval.xml
create mode 100644
Documentation/DocBook/v4l/vidioc-subdev-enum-frame-size.xml create
mode 100644
Documentation/DocBook/v4l/vidioc-subdev-enum-mbus-code.xml create
mode 100644 Documentation/DocBook/v4l/vidioc-subdev-g-crop.xml
create mode 100644
Documentation/DocBook/v4l/vidioc-subdev-g-fmt.xml create mode
100644
Documentation/DocBook/v4l/vidioc-subdev-g-frame-interval.xml create
mode 100644 Documentation/media-framework.txt create mode 100644
arch/arm/mach-omap2/devices.h create mode 100644
drivers/bluetooth/btwilink.c create mode 100644
drivers/media/media-device.c create mode 100644
drivers/media/media-devnode.c create mode 100644
drivers/media/media-entity.c create mode 100644
drivers/media/radio/wl128x/Kconfig create mode 100644
drivers/media/radio/wl128x/Makefile create mode 100644
drivers/media/radio/wl128x/fmdrv.h create mode 100644
drivers/media/radio/wl128x/fmdrv_common.c create mode 100644
drivers/media/radio/wl128x/fmdrv_common.h create mode 100644
drivers/media/radio/wl128x/fmdrv_rx.c create mode 100644
drivers/media/radio/wl128x/fmdrv_rx.h create mode 100644
drivers/media/radio/wl128x/fmdrv_tx.c create mode 100644
drivers/media/radio/wl128x/fmdrv_tx.h create mode 100644
drivers/media/radio/wl128x/fmdrv_v4l2.c create mode 100644
drivers/media/radio/wl128x/fmdrv_v4l2.h create mode 100644
drivers/media/video/isp/Makefile create mode 100644
drivers/media/video/isp/cfa_coef_table.h create mode 100644
drivers/media/video/isp/gamma_table.h create mode 100644
drivers/media/video/isp/isp.c create mode 100644
drivers/media/video/isp/isp.h create mode 100644
drivers/media/video/isp/ispccdc.c create mode 100644
drivers/media/video/isp/ispccdc.h create mode 100644
drivers/media/video/isp/ispccp2.c create mode 100644
drivers/media/video/isp/ispccp2.h create mode 100644
drivers/media/video/isp/ispcsi2.c create mode 100644
drivers/media/video/isp/ispcsi2.h create mode 100644
drivers/media/video/isp/ispcsiphy.c create mode 100644
drivers/media/video/isp/ispcsiphy.h create mode 100644
drivers/media/video/isp/isph3a.h create mode 100644
drivers/media/video/isp/isph3a_aewb.c create mode 100644
drivers/media/video/isp/isph3a_af.c create mode 100644
drivers/media/video/isp/isphist.c create mode 100644
drivers/media/video/isp/isphist.h create mode 100644
drivers/media/video/isp/isppreview.c create mode 100644
drivers/media/video/isp/isppreview.h create mode 100644
drivers/media/video/isp/ispqueue.c create mode 100644
drivers/media/video/isp/ispqueue.h create mode 100644
drivers/media/video/isp/ispreg.h create mode 100644
drivers/media/video/isp/ispresizer.c create mode 100644
drivers/media/video/isp/ispresizer.h create mode 100644
drivers/media/video/isp/ispstat.c create mode 100644
drivers/media/video/isp/ispstat.h create mode 100644
drivers/media/video/isp/ispvideo.c create mode 100644
drivers/media/video/isp/ispvideo.h create mode 100644
drivers/media/video/isp/luma_enhance_table.h create mode 100644
drivers/media/video/isp/noise_filter_table.h create mode 100644
drivers/media/video/v4l2-subdev.c create mode 100644
drivers/mfd/twl4030-madc.c create mode 100644
drivers/video/omap2/displays/panel-lgphilips-lb035q02.c create mode
100644 drivers/video/omap2/displays/panel-samsung-lte430wq-f0c.c
create mode 100644 include/linux/i2c/twl4030-madc.h create mode
100644 include/linux/media.h create mode 100644
include/linux/omap3isp.h create mode 100644
include/linux/v4l2-mediabus.h create mode 100644
include/linux/v4l2-subdev.h create mode 100644
include/media/media-device.h create mode 100644
include/media/media-devnode.h create mode 100644
include/media/media-entity.h

_______________________________________________ yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: [PATCH 2/3] beagleboard: xserver-kdrive xorg.conf installation

Darren Hart <dvhart@...>
 

On 06/18/2011 01:05 AM, Koen Kooi wrote:

Op 18 jun 2011, om 02:35 heeft Darren Hart het volgende geschreven:

Append xserver-kdrive to allow for BSP specific xorg.conf files. This also
appears to drag in a runtime dependency on libhal, so add that to the
bbappend's RDEPENDS_${PN} as well.
Since when does kdrive use xorg.conf?
This is my first use of xserver-kdrive. I was experimenting with
xorg.conf changes to resolve some USB input issues I was having... it
seemed to work. Should it be using something else?


Ultimately we probably want an xserver independent xorgconf recipe that
enables installing BSP specific xorg.conf files for all the xservers. This
works for now.
Like xserver-xorg-conf in meta-oe?
Yes, just like that. I've opened a bug on this, I'll recommend using
this. Any objection to that becoming part of oe-core? However, if I
shouldn't be using xorg.conf for xserver-kdrive, then this might be
irrelevant.

--
Darren



Signed-off-by: Darren Hart <dvhart@...>
---
.../xserver-kdrive/beagleboard/xorg.conf | 34 ++++++++++++++++++++
.../xorg-xserver/xserver-kdrive_1.7.99.2.bbappend | 10 ++++++
2 files changed, 44 insertions(+), 0 deletions(-)
create mode 100644 meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
create mode 100644 meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend

diff --git a/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
new file mode 100644
index 0000000..0335e6a
--- /dev/null
+++ b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
@@ -0,0 +1,34 @@
+Section "Module"
+ Load "extmod"
+ Load "dbe"
+ Load "glx"
+ Load "freetype"
+ Load "type1"
+ Load "record"
+ Load "dri"
+EndSection
+
+Section "Monitor"
+ Identifier "Builtin Default Monitor"
+EndSection
+
+Section "Device"
+ Identifier "Builtin Default fbdev Device 0"
+ Driver "omapfb"
+EndSection
+
+Section "Screen"
+ Identifier "Builtin Default fbdev Screen 0"
+ Device "Builtin Default fbdev Device 0"
+ Monitor "Builtin Default Monitor"
+EndSection
+
+Section "ServerLayout"
+ Identifier "Builtin Default Layout"
+ Screen "Builtin Default fbdev Screen 0"
+EndSection
+
+Section "ServerFlags"
+ Option "DontZap" "0"
+ Option "AutoAddDevices" "False"
+EndSection
diff --git a/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend
new file mode 100644
index 0000000..cfa6c4f
--- /dev/null
+++ b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend
@@ -0,0 +1,10 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+RDEPENDS_${PN} += "libhal"
+SRC_URI += "file://xorg.conf"
+
+do_install_append() {
+ install -d ${D}/${sysconfdir}/X11
+ install -m 0644 ${WORKDIR}/xorg.conf ${D}/${sysconfdir}/X11/
+}
+
+
--
1.7.1

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: [PULL][linux-yocto] beagleboard: sync with meta-ti linux-omap_2.6.37

Koen Kooi
 

Op 18 jun 2011, om 01:18 heeft Darren Hart het volgende geschreven:

From: Darren Hart <dvhart@...>

The following commits have been pulled in from the meta-ti linux-omap_2.6.37
recipe, with the exception of:
USB: ehci: remove structure packing from ehci_def
which hails from mainline and should be applied to yocto/base, while the rest
should be applied to yocto/standard/beagleboard.

Fixes [YOCTO #764]
Fixes [YOCTO #765]
Fixes [YOCTO #767]

This brings linux-yocto in sync with the meta-ti linux-omap_2.6.37 recipe and
significantly improves Beagleboard support in linux-yocto. As there are 115
patches in total, and none of them are new, I have omitted them from the email.

You seem to be including the patches that patch the kernel from 37rc7 (or rc8, I forget) to .37 final, which shouldn't apply. So basically leave out the patches in the 'linus' directory. The camera interface also doesn't work, so the 'media' directory can be left out as well.


The following changes since commit 9cb5c3fb1634e541cacceeb8c8cabe88afa5b080:

Merge branch 'yocto/standard/base' into yocto/standard/beagleboard (2011-06-06 10:35:20 -0400)

are available in the git repository at:

git://git.yoctoproject.org/linux-yocto-2.6.37-contrib dvhart/yocto/standard/beagleboard
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/yocto/standard/beagleboard

Alexander Holler (1):
arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC

Antti Koskipaa (1):
v4l: v4l2_subdev userspace crop API

Arik Nemtsov (1):
wl12xx: Read MAC address from NVS file on HW startup

Darren Hart (2):
board-omap3beagle: whitespace cleanup
board-omap3beagle: allow for building without wl1271

Eliad Peller (1):
wl1271: set wl->vif only if add_interface succeeded.

Florian Westphal (1):
bridge: stp: ensure mac header is set

Jesper Juhl (1):
ISDN, Gigaset: Fix memory leak in do_disconnect_req()

Juuso Oikarinen (1):
wl12xx: Unset bssid filter, ssid and bssid from firmware on disassoc

Kevin Hilman (1):
OMAP: CPUfreq: ensure policy is fully initialized

Koen Kooi (10):
omap3: beaglexm: fix DVI reset GPIO
omap3: beaglexm: fix power on of DVI
ARM: OMAP: beagleboard: Add infrastructure to do fixups based on
expansionboard name passed by u-boot
ARM: OMAP: beagleboard: pre-export GPIOs to userspace when using a
Tincantools trainerboard
modedb.c: add proper 720p60 mode
ARM: OMAP: add omap_rev_* macros
omap3: beagleboard: add WIP support for beagleboardtoys WL12xx board
beagleboard: hack in support from xM rev C
omap3: allow 1GHz mpurates
BeagleBoard: Adjust USER button pin for xM

Laurent Pinchart (35):
v4l: Share code between video_usercopy and video_ioctl2
v4l: subdev: Don't require core operations
v4l: subdev: Merge v4l2_i2c_new_subdev_cfg and v4l2_i2c_new_subdev
v4l: subdev: Add device node support
v4l: subdev: Uninline the v4l2_subdev_init function
v4l: subdev: Control ioctls support
media: Media device node support
media: Media device
media: Entities, pads and links
media: Entity use count
media: Media device information query
media: Entities, pads and links enumeration
media: Links setup
media: Pipelines and media streams
v4l: Add a media_device pointer to the v4l2_device structure
v4l: Make video_device inherit from media_entity
v4l: Make v4l2_subdev inherit from media_entity
v4l: Move the media/v4l2-mediabus.h header to include/linux
v4l: Replace enums with fixed-sized fields in public structure
v4l: Rename V4L2_MBUS_FMT_GREY8_1X8 to V4L2_MBUS_FMT_Y8_1X8
v4l: Group media bus pixel codes by types and sort them
alphabetically
v4l: subdev: Add a new file operations class
v4l: v4l2_subdev pad-level operations
v4l: v4l2_subdev userspace format API
v4l: v4l2_subdev userspace frame interval API
v4l: subdev: Generic ioctl support
v4l: Add subdev sensor g_skip_frames operation
v4l: Include linux/videodev2.h in media/v4l2-ctrls.h
v4l: Fix a use-before-set in the control framework
v4l: Add 8-bit YUYV on 16-bit bus and SGRBG10 media bus pixel codes
v4l: Add remaining RAW10 patterns w DPCM pixel code variants
v4l: Add missing 12 bits bayer media bus formats
v4l: Add 12 bits bayer pixel formats
omap3: Add function to register omap3isp platform device structure
OMAP3 ISP driver

Lennert Buytenhek (1):
ARM: pxa: PXA_ESERIES depends on FB_W100.

Manjunatha Halli (7):
drivers:media:radio: wl128x: FM Driver common header file
drivers:media:radio: wl128x: FM Driver V4L2 sources
drivers:media:radio: wl128x: FM Driver Common sources
drivers:media:radio: wl128x: FM driver RX sources
drivers:media:radio: wl128x: FM driver TX sources
drivers:media:radio: wl128x: Kconfig & Makefile for wl128x driver
drivers:media:radio: Update Kconfig and Makefile for wl128x FM
driver.

Nishanth Menon (2):
omap3|4: opp: make omapx_opp_init non-static
OMAP3: beagle xm: enable upto 1GHz OPP

Pavan Savoy (2):
drivers:misc:ti-st: change protocol parse logic
Bluetooth: btwilink driver

Peter 'p2' De Schrijver (1):
OMAP: CPUfreq: ensure driver initializes after cpufreq framework and
governors

Rabin Vincent (1):
USB: ehci: remove structure packing from ehci_def

Rajendra Nayak (1):
OMAP3 PM: CPUFreq driver for OMAP3

Robert Nelson (2):
omap: Beagle: detect new xM revision B
xM audio fix from Ashok

Sakari Ailus (2):
v4l: subdev: Events support
media: Entity graph traversal

Sanjeev Premi (1):
omap3: Add basic support for 720MHz part

Sergio Aguirre (2):
omap3: Remove unusued ISP CBUFF resource
omap2: Fix camera resources for multiomap

Shahar Levi (3):
wl1271: 11n Support, Add Definitions
wl1271: 11n Support, ACX Commands
wl1271: 11n Support, functionality and configuration ability

Silesh C V (1):
OMAP: PM: CPUFREQ: Fix conditional compilation

Stanimir Varbanov (1):
v4l: Create v4l2 subdev file handle structure

Steve Sakoman (18):
mmc: don't display single block read console messages
MTD: silence ecc errors on mtdblock0
OMAP: DSS2: enable hsclk in dsi_pll_init for OMAP36XX
drivers: net: smsc911x: return ENODEV if device is not found
drivers: input: touchscreen: ads7846: return ENODEV if device is not
found
ASoC: enable audio capture by default for twl4030
MFD: enable madc clock
MFD: add twl4030 madc driver
ARM: OMAP: Add twl4030 madc support to Overo
ARM: OMAP: Add twl4030 madc support to Beagle
OMAP: DSS2: Add support for Samsung LTE430WQ-F0C panel
OMAP: DSS2: Add support for LG Philips LB035Q02 panel
OMAP: DSS2: add bootarg for selecting svideo or composite for tv
output
ARM: OMAP2: mmc-twl4030: move clock input selection prior to vcc test
RTC: add support for backup battery recharge
ARM: OMAP: automatically set musb mode in platform data based on
CONFIG options
OMAP: DSS2: check for both cpu type and revision, rather than just
revision
OMAP: DSS2: Add DSS2 support for Overo

Thara Gopinath (13):
OMAP3: PM: Adding T2 enabling of smartreflex
OMAP: Introduce a user list for each voltage domain instance in the
voltage driver.
OMAP: Introduce API in the OPP layer to find the opp entry
corresponding to a voltage.
OMAP: Introduce API to register a device with a voltagedomain
OMAP: Introduce device specific set rate and get rate in omap_device
structure
OMAP: Voltage layer changes to support DVFS.
OMAP: Introduce dependent voltage domain support.
OMAP: Introduce device scale
OMAP: Disable smartreflex across DVFS
OMAP3: Introduce custom set rate and get rate APIs for scalable
devices
OMAP3: Update cpufreq driver to use the new set_rate API
OMAP3: Introduce voltage domain info in the hwmod structures.
OMAP3: Add voltage dependency table for VDD1.

Thomas Weber (1):
OMAP: Enable Magic SysRq on serial console ttyOx

Tuukka Toivonen (1):
ARM: OMAP3: Update Camera ISP definitions for OMAP3630

Documentation/ABI/testing/sysfs-bus-media | 6 +
Documentation/DocBook/Makefile | 5 +-
Documentation/DocBook/media-entities.tmpl | 50 +
Documentation/DocBook/media.tmpl | 3 +
Documentation/DocBook/v4l/dev-subdev.xml | 307 +++
Documentation/DocBook/v4l/media-controller.xml | 89 +
Documentation/DocBook/v4l/media-func-close.xml | 59 +
Documentation/DocBook/v4l/media-func-ioctl.xml | 116 +
Documentation/DocBook/v4l/media-func-open.xml | 94 +
.../DocBook/v4l/media-ioc-device-info.xml | 133 ++
.../DocBook/v4l/media-ioc-enum-entities.xml | 308 +++
Documentation/DocBook/v4l/media-ioc-enum-links.xml | 207 ++
Documentation/DocBook/v4l/media-ioc-setup-link.xml | 93 +
Documentation/DocBook/v4l/subdev-formats.xml | 2467 ++++++++++++++++++++
Documentation/DocBook/v4l/v4l2.xml | 7 +
Documentation/DocBook/v4l/vidioc-streamon.xml | 9 +
.../v4l/vidioc-subdev-enum-frame-interval.xml | 146 ++
.../DocBook/v4l/vidioc-subdev-enum-frame-size.xml | 148 ++
.../DocBook/v4l/vidioc-subdev-enum-mbus-code.xml | 113 +
Documentation/DocBook/v4l/vidioc-subdev-g-crop.xml | 149 ++
Documentation/DocBook/v4l/vidioc-subdev-g-fmt.xml | 174 ++
.../DocBook/v4l/vidioc-subdev-g-frame-interval.xml | 135 ++
Documentation/media-framework.txt | 353 +++
Documentation/video4linux/v4l2-framework.txt | 129 +-
arch/arm/mach-omap2/board-omap3beagle.c | 409 ++++-
arch/arm/mach-omap2/board-overo.c | 247 ++-
arch/arm/mach-omap2/clock.h | 14 +-
arch/arm/mach-omap2/clock34xx.c | 2 +
arch/arm/mach-omap2/control.h | 7 +
arch/arm/mach-omap2/devices.c | 64 +-
arch/arm/mach-omap2/devices.h | 17 +
arch/arm/mach-omap2/hsmmc.c | 14 +-
arch/arm/mach-omap2/id.c | 10 +
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 3 +
arch/arm/mach-omap2/omap_twl.c | 16 +
arch/arm/mach-omap2/opp3xxx_data.c | 66 +-
arch/arm/mach-omap2/opp4xxx_data.c | 3 +-
arch/arm/mach-omap2/pm.c | 110 +
arch/arm/mach-omap2/voltage.c | 369 +++-
arch/arm/mach-pxa/Kconfig | 1 +
arch/arm/plat-omap/clock.c | 2 +-
arch/arm/plat-omap/cpu-omap.c | 38 +-
arch/arm/plat-omap/include/plat/cpu.h | 57 +
arch/arm/plat-omap/include/plat/omap34xx.h | 16 +-
arch/arm/plat-omap/include/plat/omap_device.h | 12 +-
arch/arm/plat-omap/include/plat/voltage.h | 20 +
arch/arm/plat-omap/omap_device.c | 139 ++
block/blk-core.c | 7 +-
drivers/base/power/opp.c | 28 +
drivers/bluetooth/Kconfig | 10 +
drivers/bluetooth/Makefile | 1 +
drivers/bluetooth/btwilink.c | 397 ++++
drivers/input/touchscreen/ads7846.c | 13 +-
drivers/isdn/gigaset/capi.c | 1 +
drivers/media/Kconfig | 22 +
drivers/media/Makefile | 10 +-
drivers/media/media-device.c | 382 +++
drivers/media/media-devnode.c | 321 +++
drivers/media/media-entity.c | 536 +++++
drivers/media/radio/Kconfig | 3 +
drivers/media/radio/Makefile | 1 +
drivers/media/radio/radio-si4713.c | 2 +-
drivers/media/radio/wl128x/Kconfig | 17 +
drivers/media/radio/wl128x/Makefile | 6 +
drivers/media/radio/wl128x/fmdrv.h | 244 ++
drivers/media/radio/wl128x/fmdrv_common.c | 1677 +++++++++++++
drivers/media/radio/wl128x/fmdrv_common.h | 402 ++++
drivers/media/radio/wl128x/fmdrv_rx.c | 847 +++++++
drivers/media/radio/wl128x/fmdrv_rx.h | 59 +
drivers/media/radio/wl128x/fmdrv_tx.c | 425 ++++
drivers/media/radio/wl128x/fmdrv_tx.h | 37 +
drivers/media/radio/wl128x/fmdrv_v4l2.c | 580 +++++
drivers/media/radio/wl128x/fmdrv_v4l2.h | 33 +
drivers/media/video/Kconfig | 13 +
drivers/media/video/Makefile | 4 +-
drivers/media/video/cafe_ccic.c | 11 +-
drivers/media/video/davinci/vpfe_capture.c | 2 +-
drivers/media/video/davinci/vpif_capture.c | 2 +-
drivers/media/video/davinci/vpif_display.c | 2 +-
drivers/media/video/isp/Makefile | 13 +
drivers/media/video/isp/cfa_coef_table.h | 601 +++++
drivers/media/video/isp/gamma_table.h | 90 +
drivers/media/video/isp/isp.c | 2221 ++++++++++++++++++
drivers/media/video/isp/isp.h | 427 ++++
drivers/media/video/isp/ispccdc.c | 2280 ++++++++++++++++++
drivers/media/video/isp/ispccdc.h | 223 ++
drivers/media/video/isp/ispccp2.c | 1189 ++++++++++
drivers/media/video/isp/ispccp2.h | 101 +
drivers/media/video/isp/ispcsi2.c | 1332 +++++++++++
drivers/media/video/isp/ispcsi2.h | 169 ++
drivers/media/video/isp/ispcsiphy.c | 247 ++
drivers/media/video/isp/ispcsiphy.h | 74 +
drivers/media/video/isp/isph3a.h | 117 +
drivers/media/video/isp/isph3a_aewb.c | 374 +++
drivers/media/video/isp/isph3a_af.c | 429 ++++
drivers/media/video/isp/isphist.c | 520 ++++
drivers/media/video/isp/isphist.h | 40 +
drivers/media/video/isp/isppreview.c | 2120 +++++++++++++++++
drivers/media/video/isp/isppreview.h | 214 ++
drivers/media/video/isp/ispqueue.c | 1136 +++++++++
drivers/media/video/isp/ispqueue.h | 185 ++
drivers/media/video/isp/ispreg.h | 1589 +++++++++++++
drivers/media/video/isp/ispresizer.c | 1710 ++++++++++++++
drivers/media/video/isp/ispresizer.h | 150 ++
drivers/media/video/isp/ispstat.c | 1100 +++++++++
drivers/media/video/isp/ispstat.h | 169 ++
drivers/media/video/isp/ispvideo.c | 1264 ++++++++++
drivers/media/video/isp/ispvideo.h | 202 ++
drivers/media/video/isp/luma_enhance_table.h | 154 ++
drivers/media/video/isp/noise_filter_table.h | 90 +
drivers/media/video/ivtv/ivtv-i2c.c | 11 +-
drivers/media/video/mt9m001.c | 2 +-
drivers/media/video/mt9v022.c | 4 +-
drivers/media/video/ov6650.c | 10 +-
drivers/media/video/s5p-fimc/fimc-capture.c | 2 +-
drivers/media/video/sh_mobile_csi2.c | 6 +-
drivers/media/video/sh_vou.c | 2 +-
drivers/media/video/soc_camera.c | 2 +-
drivers/media/video/soc_mediabus.c | 2 +-
drivers/media/video/v4l2-common.c | 22 +-
drivers/media/video/v4l2-ctrls.c | 2 +-
drivers/media/video/v4l2-dev.c | 76 +-
drivers/media/video/v4l2-device.c | 66 +-
drivers/media/video/v4l2-ioctl.c | 216 +--
drivers/media/video/v4l2-subdev.c | 346 +++
drivers/mfd/Kconfig | 21 +
drivers/mfd/Makefile | 1 +
drivers/mfd/twl-core.c | 8 +
drivers/mfd/twl4030-madc.c | 537 +++++
drivers/misc/ti-st/st_core.c | 355 +--
drivers/misc/ti-st/st_kim.c | 56 +-
drivers/mmc/card/block.c | 4 +-
drivers/mtd/nand/nand_ecc.c | 2 +-
drivers/net/smsc911x.c | 4 +-
drivers/net/wireless/wl12xx/Kconfig | 10 +
drivers/net/wireless/wl12xx/wl1271.h | 11 +-
drivers/net/wireless/wl12xx/wl1271_acx.c | 83 +
drivers/net/wireless/wl12xx/wl1271_acx.h | 86 +
drivers/net/wireless/wl12xx/wl1271_main.c | 161 +-
drivers/net/wireless/wl12xx/wl1271_rx.c | 6 +
drivers/net/wireless/wl12xx/wl1271_tx.c | 11 +
drivers/rtc/rtc-twl.c | 25 +
drivers/serial/omap-serial.c | 4 +
drivers/video/modedb.c | 4 +
drivers/video/omap2/displays/Kconfig | 12 +
drivers/video/omap2/displays/Makefile | 2 +
.../omap2/displays/panel-lgphilips-lb035q02.c | 244 ++
.../omap2/displays/panel-samsung-lte430wq-f0c.c | 154 ++
drivers/video/omap2/dss/dispc.c | 4 +-
drivers/video/omap2/dss/dpi.c | 7 +-
drivers/video/omap2/dss/venc.c | 22 +
drivers/video/omap2/omapfb/omapfb-main.c | 10 +-
fs/buffer.c | 3 +-
include/linux/Kbuild | 4 +
include/linux/i2c/twl.h | 1 +
include/linux/i2c/twl4030-madc.h | 130 +
include/linux/media.h | 132 ++
include/linux/omap3isp.h | 631 +++++
include/linux/opp.h | 8 +
include/linux/ti_wilink_st.h | 40 +-
include/linux/usb/ehci_def.h | 6 +-
include/linux/v4l2-mediabus.h | 108 +
include/linux/v4l2-subdev.h | 141 ++
include/linux/videodev2.h | 4 +
include/media/media-device.h | 95 +
include/media/media-devnode.h | 97 +
include/media/media-entity.h | 147 ++
include/media/soc_mediabus.h | 3 +-
include/media/v4l2-common.h | 18 +-
include/media/v4l2-ctrls.h | 1 +
include/media/v4l2-dev.h | 25 +-
include/media/v4l2-device.h | 4 +
include/media/v4l2-ioctl.h | 3 +
include/media/v4l2-mediabus.h | 61 +-
include/media/v4l2-subdev.h | 120 +-
net/bridge/br_stp_bpdu.c | 2 +
sound/soc/codecs/twl4030.c | 4 +-
sound/soc/omap/omap-mcbsp.c | 3 +
178 files changed, 37220 insertions(+), 745 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-media
create mode 100644 Documentation/DocBook/v4l/dev-subdev.xml
create mode 100644 Documentation/DocBook/v4l/media-controller.xml
create mode 100644 Documentation/DocBook/v4l/media-func-close.xml
create mode 100644 Documentation/DocBook/v4l/media-func-ioctl.xml
create mode 100644 Documentation/DocBook/v4l/media-func-open.xml
create mode 100644 Documentation/DocBook/v4l/media-ioc-device-info.xml
create mode 100644 Documentation/DocBook/v4l/media-ioc-enum-entities.xml
create mode 100644 Documentation/DocBook/v4l/media-ioc-enum-links.xml
create mode 100644 Documentation/DocBook/v4l/media-ioc-setup-link.xml
create mode 100644 Documentation/DocBook/v4l/subdev-formats.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-enum-frame-interval.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-enum-frame-size.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-enum-mbus-code.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-g-crop.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-g-fmt.xml
create mode 100644 Documentation/DocBook/v4l/vidioc-subdev-g-frame-interval.xml
create mode 100644 Documentation/media-framework.txt
create mode 100644 arch/arm/mach-omap2/devices.h
create mode 100644 drivers/bluetooth/btwilink.c
create mode 100644 drivers/media/media-device.c
create mode 100644 drivers/media/media-devnode.c
create mode 100644 drivers/media/media-entity.c
create mode 100644 drivers/media/radio/wl128x/Kconfig
create mode 100644 drivers/media/radio/wl128x/Makefile
create mode 100644 drivers/media/radio/wl128x/fmdrv.h
create mode 100644 drivers/media/radio/wl128x/fmdrv_common.c
create mode 100644 drivers/media/radio/wl128x/fmdrv_common.h
create mode 100644 drivers/media/radio/wl128x/fmdrv_rx.c
create mode 100644 drivers/media/radio/wl128x/fmdrv_rx.h
create mode 100644 drivers/media/radio/wl128x/fmdrv_tx.c
create mode 100644 drivers/media/radio/wl128x/fmdrv_tx.h
create mode 100644 drivers/media/radio/wl128x/fmdrv_v4l2.c
create mode 100644 drivers/media/radio/wl128x/fmdrv_v4l2.h
create mode 100644 drivers/media/video/isp/Makefile
create mode 100644 drivers/media/video/isp/cfa_coef_table.h
create mode 100644 drivers/media/video/isp/gamma_table.h
create mode 100644 drivers/media/video/isp/isp.c
create mode 100644 drivers/media/video/isp/isp.h
create mode 100644 drivers/media/video/isp/ispccdc.c
create mode 100644 drivers/media/video/isp/ispccdc.h
create mode 100644 drivers/media/video/isp/ispccp2.c
create mode 100644 drivers/media/video/isp/ispccp2.h
create mode 100644 drivers/media/video/isp/ispcsi2.c
create mode 100644 drivers/media/video/isp/ispcsi2.h
create mode 100644 drivers/media/video/isp/ispcsiphy.c
create mode 100644 drivers/media/video/isp/ispcsiphy.h
create mode 100644 drivers/media/video/isp/isph3a.h
create mode 100644 drivers/media/video/isp/isph3a_aewb.c
create mode 100644 drivers/media/video/isp/isph3a_af.c
create mode 100644 drivers/media/video/isp/isphist.c
create mode 100644 drivers/media/video/isp/isphist.h
create mode 100644 drivers/media/video/isp/isppreview.c
create mode 100644 drivers/media/video/isp/isppreview.h
create mode 100644 drivers/media/video/isp/ispqueue.c
create mode 100644 drivers/media/video/isp/ispqueue.h
create mode 100644 drivers/media/video/isp/ispreg.h
create mode 100644 drivers/media/video/isp/ispresizer.c
create mode 100644 drivers/media/video/isp/ispresizer.h
create mode 100644 drivers/media/video/isp/ispstat.c
create mode 100644 drivers/media/video/isp/ispstat.h
create mode 100644 drivers/media/video/isp/ispvideo.c
create mode 100644 drivers/media/video/isp/ispvideo.h
create mode 100644 drivers/media/video/isp/luma_enhance_table.h
create mode 100644 drivers/media/video/isp/noise_filter_table.h
create mode 100644 drivers/media/video/v4l2-subdev.c
create mode 100644 drivers/mfd/twl4030-madc.c
create mode 100644 drivers/video/omap2/displays/panel-lgphilips-lb035q02.c
create mode 100644 drivers/video/omap2/displays/panel-samsung-lte430wq-f0c.c
create mode 100644 include/linux/i2c/twl4030-madc.h
create mode 100644 include/linux/media.h
create mode 100644 include/linux/omap3isp.h
create mode 100644 include/linux/v4l2-mediabus.h
create mode 100644 include/linux/v4l2-subdev.h
create mode 100644 include/media/media-device.h
create mode 100644 include/media/media-devnode.h
create mode 100644 include/media/media-entity.h

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: [PATCH 2/3] beagleboard: xserver-kdrive xorg.conf installation

Koen Kooi
 

Op 18 jun 2011, om 02:35 heeft Darren Hart het volgende geschreven:

Append xserver-kdrive to allow for BSP specific xorg.conf files. This also
appears to drag in a runtime dependency on libhal, so add that to the
bbappend's RDEPENDS_${PN} as well.
Since when does kdrive use xorg.conf?

Ultimately we probably want an xserver independent xorgconf recipe that
enables installing BSP specific xorg.conf files for all the xservers. This
works for now.
Like xserver-xorg-conf in meta-oe?



Signed-off-by: Darren Hart <dvhart@...>
---
.../xserver-kdrive/beagleboard/xorg.conf | 34 ++++++++++++++++++++
.../xorg-xserver/xserver-kdrive_1.7.99.2.bbappend | 10 ++++++
2 files changed, 44 insertions(+), 0 deletions(-)
create mode 100644 meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
create mode 100644 meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend

diff --git a/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
new file mode 100644
index 0000000..0335e6a
--- /dev/null
+++ b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive/beagleboard/xorg.conf
@@ -0,0 +1,34 @@
+Section "Module"
+ Load "extmod"
+ Load "dbe"
+ Load "glx"
+ Load "freetype"
+ Load "type1"
+ Load "record"
+ Load "dri"
+EndSection
+
+Section "Monitor"
+ Identifier "Builtin Default Monitor"
+EndSection
+
+Section "Device"
+ Identifier "Builtin Default fbdev Device 0"
+ Driver "omapfb"
+EndSection
+
+Section "Screen"
+ Identifier "Builtin Default fbdev Screen 0"
+ Device "Builtin Default fbdev Device 0"
+ Monitor "Builtin Default Monitor"
+EndSection
+
+Section "ServerLayout"
+ Identifier "Builtin Default Layout"
+ Screen "Builtin Default fbdev Screen 0"
+EndSection
+
+Section "ServerFlags"
+ Option "DontZap" "0"
+ Option "AutoAddDevices" "False"
+EndSection
diff --git a/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend
new file mode 100644
index 0000000..cfa6c4f
--- /dev/null
+++ b/meta-yocto/recipes-graphics/xorg-xserver/xserver-kdrive_1.7.99.2.bbappend
@@ -0,0 +1,10 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+RDEPENDS_${PN} += "libhal"
+SRC_URI += "file://xorg.conf"
+
+do_install_append() {
+ install -d ${D}/${sysconfdir}/X11
+ install -m 0644 ${WORKDIR}/xorg.conf ${D}/${sysconfdir}/X11/
+}
+
+
--
1.7.1

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto