On 2018-12-12 8:36 p.m., Hongzhi, Song wrote:
Thanks.
So would you help to remedy the commit log while merging the patch?
I've tweaked the message and added this to my queue. It will
come out early this week.
Bruce
--Hongzhi
On 12/13/2018 02:45 AM, Bruce Ashfield wrote:
On 12/11/18 5
Signed-off-by: Bruce Ashfield
---
This goes along with the series just sent to oe-core to remove 4.14 and
introduce 4.19 as the LTS (and LSB) kernel.
Bruce
meta-poky/conf/distro/poky-lsb.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-poky/conf/distro/poky
On 12/17/18 7:25 AM, Richard Weinberger wrote:
[Resending with correct mail]
Richard,
On Mon, Dec 17, 2018 at 11:34 AM wrote:
On Mon, 2018-12-17 at 11:26 +0100, Richard Weinberger wrote:
On Wed, Nov 28, 2018 at 9:42 AM Richard Purdie
wrote:
The system can definitely do it, its just not
On 12/17/18 8:50 AM, Richard Weinberger wrote:
Bruce,
On Mon, Dec 17, 2018 at 2:47 PM Bruce Ashfield
wrote:
Yocto seems to try a different approach.
When I use qemux86-64.conf with DEFAULTTUNE being "i586" it generates a 32bit
toolchain by default.
Build Configuration:
On 2018-11-19 2:13 p.m., Sakib Sajal wrote:
Hello,
I have been trying to patch the linux kernel and add some kernel
configuration but I am failing to add kconfig fragments to be included
in the final build.
Initially I tried patching the kernel with hardcoded values in the patch.
I am
On 2019-01-07 9:00 a.m., Kristupas Savickas wrote:
Hello,
I'm porting a kernel to use yocto-style build process. The kernel
fetches fine, but there's a problem with '.config' file generation. I'd
like to supply a 'defconfig' and a configuration fragment file
'test.cfg' (which should be
merged
Bruce
On Thu, Mar 21, 2019 at 10:52 PM Zhixiong Chi
wrote:
>
> Add the default route option for the operation of adding route,
> while we set the static route and the mask setting is 0.
>
> For example:
> add_routes 32 169 254 169 254 10 209 67 4 0 10 209 67 1
>
> The first route
On Fri, Apr 5, 2019 at 7:42 PM Bruce Ashfield wrote:
>
> On Thu, Apr 4, 2019 at 5:28 PM akuster808 wrote:
> >
> > Hello,
> >
> > I noticed there are 3 kernels in Warrior. 4.18, 4.19 an 5.0. Do we
> > really need 4.18?
> > I see its the default version
On Thu, Apr 4, 2019 at 5:28 PM akuster808 wrote:
>
> Hello,
>
> I noticed there are 3 kernels in Warrior. 4.18, 4.19 an 5.0. Do we
> really need 4.18?
> I see its the default version for poky-tiny. 4.18 is EOL but maintained
> by Windriver.
4.18 needed to be around through M3 to backstop some
From: Bruce Ashfield
This is a follow on to my oe-core series that introduces the 5.0
kernel. Once that is merged (and all outstanding issues resolved),
these can be applied to make the default 5.0 for poky and the
reference BSPs.
The removal of 4.18 from master will follow once everything
From: Bruce Ashfield
The 5.0 kernel is available and 4.18 will soon be dropped,
so we updated the preferred version to 5.0.
Signed-off-by: Bruce Ashfield
---
meta-poky/conf/distro/poky.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-poky/conf/distro/poky.conf b
From: Kevin Hao
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
meta-yocto-bsp/conf/machine/edgerouter.conf | 2 +-
meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 2 +-
3 files changed, 3 insertions(+), 3
From: Kevin Hao
Boot test for all the boards.
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto_5.0.bbappend| 24 +--
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0
From: Bruce Ashfield
Although the hardware reference boards are not using the 5.x
kernel yet, we generate a baseline bbappend for future work.
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto_5.0.bbappend| 27 +++
1 file changed, 27 insertions(+)
create
On Tue, Jan 29, 2019 at 9:50 PM Chuck Wolber wrote:
>
> This question is with respect to the Yocto thud (2.6.x) branch. I have also
> reviewed section 2.3.3 and 2.3.4 of the Kernel Development document.
>
>
> My kernel configuration (cfg) seems to be overridden by KERNEL_FEATURES and
> it is
On 2019-02-02 10:16 p.m., Ken Sloat wrote:
On Sat, Feb 2, 2019 at 10:03 PM Bruce Ashfield
wrote:
On 2019-02-02 9:59 p.m., Ken Sloat wrote:
Hello,
I have an out of tree kernel module which I want autoloaded at startup
on my system. Looking at the Yocto project manual, I see that one way
I
On 2019-02-02 9:59 p.m., Ken Sloat wrote:
Hello,
I have an out of tree kernel module which I want autoloaded at startup
on my system. Looking at the Yocto project manual, I see that one way
I can do this is to add the module name to the KERNEL_MODULE_AUTOLOAD
variable within my custom module
On Sat, Apr 13, 2019 at 9:54 PM nick wrote:
>
> Greetings,
> I was trying to build a kernel with these files in a new layer for no smp to
> be enabled but have no
> idea why it doesn't work. This is after looking at the kernel manual and it's
> literally the same
> files excluding the disabling
IIRC the autobuilders
are using a sato based image (Richard could confirm more easily that I
could what image type the autobuilders are using for hello-world on target
module tests).
Bruce
>
> Thank you,
> Zoran
> ___
>
>
> On Wed, May 15, 2019 at 7:41 AM Bruce
as perhaps being selected by an
option, or a default configuration was being assumed .. you will see
some minor deltas.
Bruce
>
> Pierluigi
>
> On 06/06/19 15:47, Bruce Ashfield wrote:
> > On Thu, Jun 6, 2019 at 9:38 AM Pierluigi Greto
> > wrote:
> >> Hi,
> >>
On Thu, May 30, 2019 at 4:14 AM Belisko Marek wrote:
>
> Hi,
>
> I'm trying to add support for latest possible released kernel in
> meta-sunxi by using poky warrior and hit this QA issue:
> ERROR: linux-mainline-5.2-rc2-r0 do_package: QA Issue: linux-mainline:
> Files/directories were installed
On Thu, May 30, 2019 at 8:37 AM Belisko Marek wrote:
>
> On Thu, May 30, 2019 at 2:35 PM Bruce Ashfield
> wrote:
> >
> > On Thu, May 30, 2019 at 4:14 AM Belisko Marek
> > wrote:
> > >
> > > Hi,
> > >
> > > I'm trying to add
On Thu, Jun 6, 2019 at 9:38 AM Pierluigi Greto wrote:
>
> Hi,
>
> I have to create a custom 4.14.49 linux kernel. In my recipe I have added my
> defconfig, but yocto it's not taking in consideration the defconfig. Instead
> it's building the kernel using the default values. Also the compilation
On Thu, May 9, 2019 at 8:10 AM Kevin Hao wrote:
> Boot test for all these boards.
>
>
I do have more -stable updates coming, and you are seeing some queued 5.0.x
changes that I haven't sent yet (since I'm hung up on resolving a 4.19
conflict for one of the SoC branches), but yes, the changes
tojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/target-bbb-platform-traces.txt
>
>
While interesting .. it really isn't relevant in this context. But thanks
for sharing anyway!
Cheers,
Bruce
> Thank you,
> Zoran
> ___
>
> On Thu, May 9, 2019 at 2:53 PM Bruce Ash
On Tue, May 14, 2019 at 1:30 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello Chris, Bruce,
>
> I have some additional data to share with you both, since I have tried
> something. And here is my take on the things!
>
> > 1. Build using a bb recipe.
> > Take a look at
On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
> Hello,
>
> This might have been discussed before. I couldn't find a relevant
> thread, but if it is so, just link me to it.
>
> Since thud, more specific since
>
> commit 9af0f1a46bbb6ad9ee8b35957251f4aa826b023f
On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote:
>
> On 23/05/2019 15.39, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield
> wrote:
>
>>
>>
>> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>>
>>>
On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield
wrote:
>
>
> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>
>> Hello,
>>
>> This might have been discussed before. I couldn't find a relevant
>> thread, but if it is so, just link me to it.
&
On Thu, May 23, 2019 at 10:39 AM Andrei Gherzan wrote:
> On 23/05/2019 15.32, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>
>> Hello,
>>
>> This might have been discussed before. I couldn't find a relevant
>
g said, they are optional. I might be misreading, but what exactly
are you trying to build that requires that specific structure ? We are both
rebuilding the entire kernel and out of tree modules all the time with the
existing structure/path of the on-target installs.
kernel-devsrc itself is a
On Thu, May 23, 2019 at 12:20 PM Andrei Gherzan wrote:
>
> On 23/05/2019 17.11, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote:
>
>> On 23/05/2019 16.10, Bruce Ashfield wrote:
>>
>>
>>
>> On Thu
On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote:
> On 23/05/2019 16.10, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote:
>
>>
>> On 23/05/2019 15.39, Bruce Ashfield wrote:
>>
>>
>>
>> On
systemtap \
>> > > "
>> > >
>> > > Problem with this approach is that such a kernel makes the
>> rootfs too
>> > > big and impractical:
>> > > -rw-r--r--. 2 user vboxusers 101499952 May 17 14:32
>> > >
l.
I'm going to create two new optional packages for the fall release that are
simply captured kernel-source and kernel-headers for those uses cases where
someone really does want the entire source tree, or just the headers. The
details for that work are in bugzilla.
Bruce
>
> >
&g
On Fri, May 24, 2019 at 8:50 AM Bruce Ashfield
wrote:
>
>
> On Fri, May 24, 2019 at 7:24 AM Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
>
>> As I said, I am a man of experimental try-outs. And here is the try!
>>
>> Now, after setting
On Fri, May 24, 2019 at 12:27 PM Mauro Ziliani wrote:
>
> Hi all.
>
> How can I ask to bitbake which is the actual value of virtual/kernel?
>
Here's one way:
bitbake -e virtual/kernel | grep PREFERRED_PROVIDER_virtual\/kernel
# $PREFERRED_PROVIDER_virtual/kernel [2 operations]
not going to it first.
Hopefully I'll get some new patches out in the coming month before summer
holidays really kick in.
Bruce
> Just thinking loud...
>
> Zoran
> ___
>
> On Wed, May 15, 2019 at 4:25 PM Bruce Ashfield
> wrote:
> >
> >
> >
>
On Sun, May 12, 2019 at 6:54 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello to the YOCTO community,
>
> I am using (to build the target for Beagle Bone Black) the following
> script:
> https://github.com/ZoranStojsavljevic/bbb-yocto
>
On Sat, May 4, 2019 at 10:07 AM Emily Smith wrote:
> Hi Randy -
>
> Good point it might be. Should I ask the meta-Xilinx maintainers about
> getting it in there?
>
>
That's probably the right thing to do, and/or just ask on the xilinx
mailing list what the plans are for releasing the code in a
merged
Bruce
On Sun, Jun 30, 2019 at 10:08 PM wrote:
>
> From: Mingli Yu
>
> Since spice of meta-cloud-services depends on
> cyrus-sasl which comes from networking-layer,
> add missing layer depends back.
>
> Signed-off-by: Mingli Yu
> ---
> conf/layer.conf | 2 +-
> 1 file changed, 1
merged.
Bruce
On Sun, Jun 30, 2019 at 10:09 PM wrote:
>
> From: Mingli Yu
>
> As nss-pam-ldapd depends on libpam, it should do
> required distro feature check for pam.
>
> Signed-off-by: Mingli Yu
> ---
> recipes-support/nss-pam-ldapd/nss-pam-ldapd_0.9.8.bb | 3 ++-
> 1 file changed, 2
On Tue, Apr 23, 2019 at 6:09 AM Priyanshu Sharma <
ms.priyanshu.sha...@gmail.com> wrote:
> Hi,
>
> How can we remove inclusion of any package which comes because some other
> package RDPENDS on it?
>
> For example, rpcbind recipe RDEPENDS on shadow and libpam packages,
> because of which if
From: Bruce Ashfield
Updating poky-tiny to prefer 5.0 as the kernel version. Boot
tested against qemux86 and qemuarm. This removes the last user
of the 4.18 kernel, so we can queue it for removal from master.
Signed-off-by: Bruce Ashfield
---
meta-poky/conf/distro/poky-tiny.conf | 2 +-
1
/pipermail/linux-yocto/2019-August/007908.html
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
v2:
This is a minor tweak to the SRCREVs from Kevin's original version,
everything else is unchanged.
The meta changes are also in the latest linux-yocto 5.2 recipes.
Bruce
.../conf
merged
Bruce
On Fri, Aug 30, 2019 at 2:13 AM wrote:
>
> From: Changqing Li
>
> Signed-off-by: Changqing Li
> ---
> recipes-extended/glusterfs/glusterfs.inc | 8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-extended/glusterfs/glusterfs.inc
>
On Wed, Sep 4, 2019 at 4:53 AM vygu wrote:
>
> Hello,
>
> Just to signal there are several mistakes with the recipe "perf.bb" from poky
> on master (currently: e2bde009b325b40641407ecf50f54ed8c41726d6)
>
> - If "Python 3 is not yet supported" by "perf" sources, it causes an issue
> during the
On Wed, Jul 17, 2019 at 7:43 AM praveen vattipalli
wrote:
>
> Hi All,
> we are upgrading Yocto from Krogath to Sumo version.
> while using meta-altera kernel source as local source,
>
> if i use EXTERNALSRC_BUILD variable
> EXTERNALSRC =
>
On Thu, Sep 26, 2019 at 12:55 PM wrote:
> From: Bruce Ashfield
>
> Updating the reference BSP SRCREVs and versions to 5.2.17 to match
> the latest for qemu* and to pickup some reference board specific
> patches.
>
> Signed-off-by: Bruce Ashfield
> ---
> .../lin
From: Bruce Ashfield
Updating the reference BSP SRCREVs and versions to 5.2.17 to match
the latest for qemu* and to pickup some reference board specific
patches.
Signed-off-by: Bruce Ashfield
---
v2: make sure that genericx86 and beaglebone-yocto are updated
.../linux/linux-yocto_5.2
From: Bruce Ashfield
Updating the reference BSP SRCREVs and versions to 5.2.17 to match
the latest for qemu* and to pickup some reference board specific
patches.
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto_5.2.bbappend | 16
1 file changed, 8
e kernel-modules package is a meta-package. It is supposed to be
empty. It has RDEPENDS on all of the other modules that were built. So
if you install it, it pulls in all of the build and packaged modules.
That works for rpm/ipk, or whatever package format you are using.
Bruce
>
> Regards,
he pieces.
The "kernel-modules" package is a meta package that installs all built
modules onto the system.
So unless you are really size constrained on the device, use it, and
you'll get everything that was configured and built as a module.
Bruce
>
> -Thanks!, Wayne Li
>
> On Wed, N
On Wed, Nov 6, 2019 at 11:30 AM Wayne Li wrote:
>
> Dear Yocto Developers,
>
> I'm trying to get KVM added and working on a Yocto kernel I built up for a
> T4240 RDB (has a PowerPC CPU). KVM isn't working and the reason why it isn't
> working seems to be I'm missing the necessary kernel
On Wed, Nov 6, 2019 at 11:06 AM Dimitris Tassopoulos wrote:
>
> Hi all. I have a weird issue with the kernel modules not being installed in
> the image and also not packaged.
> I see the packages for individual "kernel-module-*.ipk" modules but the
> "kernel-modules_*.ipk" is always
> empty.
>
On Fri, Oct 4, 2019 at 11:40 AM Shravan Singh wrote:
>
> Hello,
>
> I am trying to build an out of tree service module on a yocto raspberry pi
> image(target system).
> I am using yocto version warrior
> and my machine is Raspberrypi-cm3
> Kernel version is 4.19.58
>
> I was able to get the
Hi Diego,
I didn't see your original email. I'm stepping out for a holiday
weekend now, but will write up an explanation of the history reasons
for what you are seeing when I get a few minutes over the next few
days.
Cheers,
Bruce
On Fri, Oct 11, 2019 at 1:11 PM Diego Santa Cruz
wrote:
>
>
On Fri, Oct 11, 2019 at 1:11 PM Diego Santa Cruz
wrote:
>
> Hi,
>
>
>
> I have not received any feedback on the below email and I am not sure I am
> doing the right thing.
>
>
>
> Can anyone provide some advice as to what would be the recommended way to
> apply kernel patches listed in a
On Mon, Oct 14, 2019 at 5:50 AM Diego Santa Cruz
wrote:
>
> > From: Bruce Ashfield
> >
> > On Fri, Oct 11, 2019 at 1:11 PM Diego Santa Cruz
> > wrote:
> > >
>
> > > Can anyone provide some advice as to what would be the recommended way
> >
On 12-12-03 01:50 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
Bruce,
This commit only changes .scc files. The psb patches are not removed,
as you will be handling it in your own way.
Nice and simple.
I've merged the changes and pushed the changes.
On 12-12-05 01:34 PM, Darren Hart wrote:
On 12/05/2012 10:19 AM, Bruce Ashfield wrote:
On 12-12-05 01:09 PM, Darren Hart wrote:
Some candid feedback from someone struggling with their build. They
specified a non-master branch on the SRC_URI but had not added a
KBRANCH, so bitbake fetched
On 12-12-20 7:54 PM, Lai Eddy wrote:
Hi , I'm using yocto 1.3 on jasperforest BSP, have build the USB flash
drive and boot on target h/w successfully.
after trying to add igb for intel 82580DB network controller support
in jasperforst.conf +’KERNEL_FEATURES_append = features/igb’, build
done but
On 12-12-21 6:01 PM, Lai Eddy wrote:
Thanks Bruce,
how can I check to see if the kernel options were picked up and made it
to the build by looking at the linux build directory and the .config,
are you options present in the final .config ?
have read the development manual, in chap.4.1.2.2 said
On 13-01-08 02:18 AM, Liang Li wrote:
On 2013-01-08 09:14, Darren Hart dvh...@linux.intel.com wrote:
On 01/07/2013 05:11 PM, Liang Li wrote:
On 2013-01-08 08:59, Liang Li liang...@windriver.com wrote:
On 2013-01-08 01:00, Darren Hart dvh...@linux.intel.com wrote:
Hrm, is this right with
branch of linux-yocto-3.4
and to all BSP branches in the tree.
LTSI based BSPs or features are not activated as part of this commit, they
are controlled by the meta branch of the kernel repository and are activated
in separate patches.
[YOCTO #2396]
Signed-off-by: Bruce Ashfield bruce.ashfi
linux-yocto-tiny and linux-yocto had minor differences from the rest
of the linux-yocto recipes. After this commit, all the recipes are
using bareclone=1 and repository names that end with .git.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto
Since linux-yocto based recipes have a split build and source directory,
we should export KBUILD=${B} to the devshell. This allows the kernel to
be incrementally build within the shell and not dirty the source
directory (which breaks subsequent full builds).
Signed-off-by: Bruce Ashfield
On 13-01-18 01:53 PM, Kamble, Nitin A wrote:
-Original Message-
From: Hart, Darren
Sent: Friday, January 18, 2013 10:52 AM
To: Kamble, Nitin A
Cc: bruce.ashfi...@windriver.com; Zanussi, Tom; linux-
yo...@yoctoproject.org
Subject: Re: [meta branch v3 11/12] meta: add config fragment
.
This also works for pre-uapi kernel headers, so the change is safe for
most (if not all) kernel's with properly exported headers.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-bsp/v86d/v86d_0.1.10.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Introducing the linux-yocto 3.8 kernel recipe. The tools and branch structure
of this tree are the same as the previous linux-yocto recipes, while the meta
data and content have been updated for the 3.8 kernel.
build and boot tested for qemu*.
Signed-off-by: Bruce Ashfield bruce.ashfi
On 13-02-26 3:02 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamblenitin.a.kam...@intel.com
This is a commit picked from the v3.4 repo, to support the emgd-1.16
driver in the linux-yocto-dev repo.
merged.
And FYI, it was only linux-yocto-dev that was missing this commit, I already
had
On 13-03-01 8:05 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamblenitin.a.kam...@intel.com
Hi Bruce,
I have prepared commits for enabling non-transparent-bridge and
Crystal-Beach-DMA/DCA drivers in the kernel.
This is needed to implement features in this bug:
On 13-03-05 12:00 PM, Kamble, Nitin A wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, March 05, 2013 8:41 AM
To: Kamble, Nitin A
Cc: linux-yocto@yoctoproject.org
Subject: Re: v3.8 kernel recipes in meta-intel
On 13-03-05 11:39 AM
On 13-04-16 12:31 PM, Tom Zanussi wrote:
This is a fix for Yocto Bug 4099 - Crosstap script check fails.
Please pull into linux-yocto-3.8 standard/base.
Thanks Tom, I've staged it here. Nice to see a fix that wasn't caused
by something that I did :)
Bruce
Thanks,
Tom
Tom Zanussi (1):
On 13-04-16 04:01 PM, Tom Zanussi wrote:
On Tue, 2013-04-16 at 15:54 -0400, Bruce Ashfield wrote:
On 13-04-16 03:31 PM, Tom Zanussi wrote:
On Tue, 2013-04-16 at 14:48 -0400, Bruce Ashfield wrote:
On 13-04-16 12:31 PM, Tom Zanussi wrote:
This is a fix for Yocto Bug 4099 - Crosstap script
On 13-05-06 07:12 AM, Manish Sharma wrote:
HI,
I am looking for kernel headers used in used to prepare qemux86
image. Where can I get those? I visited
http://downloads.yoctoproject.org/releases/yocto/. but could not figure
out the headers!
Kernel on my qemu (x86) is 3.2.11-yocto-standard
in your project).
Cheers,
Bruce
Regards
Manish Sharma
On Mon, May 6, 2013 at 6:18 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 13-05-06 07:12 AM, Manish Sharma wrote:
HI,
I am looking for kernel headers used in used to prepare qemux86
image. Where can I get those? I
On 13-05-18 05:47 PM, Darren Hart wrote:
The following are invalid for the 3.8 kernel:
CONFIG_MISC_DEVICES
CONFIG_USB_GADGET_DUALSPEED
CONFIG_USB_GADGET_EG20T
Good catch. I'm surprised this slipped through, but better now than
never!
Cheers,
Bruce
Signed-off-by: Darren Hart
On 13-05-18 05:47 PM, Darren Hart wrote:
The following CONFIGs are invalid, remove all references to them:
Another good catch. Thanks!
Bruce
CONFIG_VIDEO_CAPTURE_DRIVERS
CONFIG_VIDEO_V4L2_COMMON
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
On 13-05-18 05:47 PM, Darren Hart wrote:
The following adds new fragments, cleans up errors in existing fragments (but
does not change any policy), and create a new minnow BSP. Please apply to the
3.8 meta branch.
It all looks fine to me. As you noted in the fragments, some of the items
and
On 13-05-27 12:55 PM, Paul Butler wrote:
Signed-off-by: Paul Butler paul.but...@windriver.com
Why wasn't this squashed into patch 4/87 ?
Bruce
---
drivers/usb/host/ehci-ci13612.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/host/ehci-ci13612.c
On 13-05-27 12:55 PM, Paul Butler wrote:
Fix an issue that we found with the burst size on the AXI bus.
Typically we elaborate on issues .. what is the user visible symptom
that someone sees with this problem ? That should be in the commit log,
as well as an explanation of how this fixes the
On 13-05-27 12:55 PM, Paul Butler wrote:
What's a fast model ? .. yes I'm playing dumb, but patch headers should
describe the common questions about code they introduce.
Bruce
Signed-off-by: Paul Butler paul.but...@windriver.com
---
arch/arm/boot/fmboot/Makefile | 25 +
On 13-05-27 12:55 PM, Paul Butler wrote:
Signed-off-by: Paul Butler paul.but...@windriver.com
Why is this separate from the patch that introduces mach-axxia ?
Bruce
---
arch/arm/mach-axxia/axxia.c | 51 ++---
1 file changed, 39 insertions(+), 12
On 13-05-27 12:55 PM, Paul Butler wrote:
From: Jiang Lu lu.ji...@windriver.com
Signed-off-by: Paul Butler paul.but...@windriver.com
---
arch/arm/Kconfig | 23 +++
arch/arm/Makefile | 3 ++-
2 files changed, 25 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig
On 13-05-27 12:55 PM, Paul Butler wrote:
Signed-off-by: Paul Butler paul.but...@windriver.com
These are common files, and not protected by #ifdefs, are these safe for all
v7 boards ?
Bruce
---
arch/arm/mm/proc-v7-2level.S | 4 +++-
arch/arm/mm/proc-v7-3level.S | 4 +++-
2 files changed,
On 13-05-27 12:55 PM, Paul Butler wrote:
Same question. Other than tracking who did what, is there any reasn
why this isn't in the patch that introduced the driver ?
Bruced
Signed-off-by: Paul Butler paul.but...@windriver.com
---
include/linux/i2c-axxia.h | 25 +
1
On 13-05-27 12:56 PM, Paul Butler wrote:
From: David Mercado david.merc...@windriver.com
Modified arch/arm/mach-axxia/axxia-gic.c to to handle the slightly different
way in which a preempt_rt kernel manipulates the Axxia GIC API during boot.
Also updated arch/arm/configs/lsisim_defconfig to set
On 13-05-27 12:56 PM, Paul Butler wrote:
From: Jiang Lu lu.ji...@windriver.com
This is based on the cputable.c from LSI. Currently our kernel only
support ACP 3448 SoC. But all the ACP 34xx SoC are using a 476 core,
and just have minor differences. They also use the same reference
board. Adding
On 13-05-27 12:56 PM, Paul Butler wrote:
From: Jiang Lu lu.ji...@windriver.com
Extracted from lsi.patch in lsi_acp_linux_6.8.1.18 tarball.
This is typically an acceptable upstream reference, but I have to ask.
Is there a public location that we can point to for this tgz ?
Bruce
The Nuevo
On 13-05-27 12:56 PM, Paul Butler wrote:
From: Jiang Lu lu.ji...@windriver.com
The patch is base upon Jason's commit
This commit header isn't appropriate for Linux yocto. The commit
header should just introduce the change, without referencing some
other commit we don't have in our tree.
On 13-05-27 12:55 PM, Paul Butler wrote:
Creating a new branch in linux-yocto_3.4 for tracking LSI BSP changes.
Branched from standard/base at commit fff57da7886cf5e99c07adf6649610cb1cd89330
I added comments throughout the code. There are some minor cleanups
and references that are required.
On 13-05-28 04:00 PM, Paul Butler wrote:
On Mon, May 27, 2013 at 02:00:01PM -0400, Bruce Ashfield wrote:
On 13-05-27 12:55 PM, Paul Butler wrote:
Signed-off-by: Paul Butler paul.but...@windriver.com
Why wasn't this squashed into patch 4/87 ?
Multiple people were working on things
On 13-05-30 7:19 PM, Darren Hart wrote:
Aimed at developers and hackers, the Minnowboard expansion connector provides
access to SPI (and other busses). Users are likely to want to experiment with
userspace SPI drivers. Create the fragments and include them in the minnow BSP.
Looks fine. merged
On 13-05-30 7:22 PM, Darren Hart wrote:
These are no longer necessary with RC3 firmware and later.
reverted and pushed.
Bruce
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
On 13-05-31 12:41 AM, Darren Hart wrote:
Looks like 2/2 still needs reverting?
95a0b8d minnowboard: Read mac address from efi var
Aha. i didn't get 2/2 in my inbox, so I wasn't sure if the 1/2 was
a typo or not. Will revert it now.
Bruce
--
Darren
On 05/30/2013 09:33 PM, Bruce Ashfield
On 13-05-31 05:11 AM, Xufeng Zhang wrote:
commit 9839ff0dead906e85e4d17490aeff87a5859a157 upstream
I assume this is for the 3.4 tree ?
Do you know if this same commit has been submitted to the korg 3.4
stable tree ?
The change looks fine, but I'd like to be sure it is also going to
every
On 13-06-02 10:06 PM, Xufeng Zhang wrote:
On 06/01/2013 01:29 AM, Bruce Ashfield wrote:
On 13-05-31 05:11 AM, Xufeng Zhang wrote:
commit 9839ff0dead906e85e4d17490aeff87a5859a157 upstream
I assume this is for the 3.4 tree ?
Yes.
Great.
Do you know if this same commit has been
On 13-06-03 10:14 AM, Jean-François Dagenais wrote:
Hi guys, (Bruce...)
(work with Marc Ferland at Sonatest)
Heads up: I'm a linux-yocto recipe noob. We historically maintained a static
defconfig with a build ready branch on a local repo.
Now moving up to 1.3 and 1.4, we want to use the meta
On 13-06-03 10:29 PM, Jean-François Dagenais wrote:
Hi all,
I've gone through lots of doc concerning kernel development but couldn't find
the right fit.
Are you working on the yocto master branches ? I ask, because there are
different features in different branches of the project.
I like
1101 - 1200 of 2361 matches
Mail list logo
