the assembler with generate the instructions you're asking for, or a
PC relative address instruction, or anything else it can to give the
address of dest.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev
rent
name
video=DVI-D-1:1680x1050@60
You can actually include both on the commandline and they don't
interfere with each other, which is handy if you swap between 3.10 and
current tip kernels.
--
Tixy
___
linaro-dev mailing list
linaro
On Thu, 2014-07-03 at 14:59 +0530, Amit Kucheria wrote:
> On Thu, Jul 3, 2014 at 2:22 PM, Jon Medhurst (Tixy) wrote:
> > On Thu, 2014-07-03 at 10:24 +0530, Amit Kucheria wrote:
> >> On Thu, Jul 3, 2014 at 7:37 AM, Lisa Nguyen wrote:
> > [...]
> >> > diff --
d cpu0 in $dirpath, it'll return a zero, right? So your
> above expression becomes zero and you don't end up skipping the test
> for cpu0.
But in shells, isn't zero true and non-zero false, and && behaves
accordingly?
I have another comment though, will the scri
On Tue, 2014-06-17 at 14:38 +0100, Mark Brown wrote:
> On 17 June 2014 13:16, Jon Medhurst (Tixy) wrote:
> On Tue, 2014-06-17 at 12:53 +0100, Mark Brown wrote:
>
> > I've added him.
>
> You didn't seem to have, u
ded in linux-linaro, so updates to the config will
automatically find there way into linux-linaro
> I've added him.
You didn't seem to have, unless this more of the Linaro's lists's
default behaviour of dropping people from CC who are subscribed?
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
t doesn't actually shut the model down, you will still need
to kill it by hand.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
t's a bit more than that and tells the model to emulate the
cache in a similar way to how hardware works, so if the running code
doesn't perform cache maintenance correctly it will go horribly wrong as
on real hardware.
--
Tixy
___
linaro
On Tue, 2013-08-06 at 21:12 +0800, Andy Green wrote:
> On 6 August 2013 20:47, Mark Brown wrote:
> > On Tue, Aug 06, 2013 at 08:24:52AM +0800, Andy Green wrote:
> >> 6) warning-elimination: nobody uses cci_pmu_destroy
> >
> >> Presumably coming from the CCI
On Mon, 2013-08-05 at 10:53 +0100, Mark Brown wrote:
> On 5 August 2013 10:44, Jon Medhurst (Tixy) wrote:
> On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
>
> > The whole list is good things to have I just wonder how
> ongoing
>
>
On Mon, 2013-08-05 at 17:13 +0800, Andy Green wrote:
> On 5 August 2013 16:58, Jon Medhurst (Tixy) wrote:
> >
> > tracking-armlt-cci
> > CCI driver and CCI PMU patches.
>
> We started using that the other day trying to track down a nasty bug,
> I didn'
ary.
Gator is available from ARM as a tarball and from the Linaro git
git://git.linaro.org/arm/ds5/gator.git. Linaro Android builds use that
repo so you don't need it in the kernel tree for that and it can be
installed on Linaro Ubuntu images with:
apt-get install gator-daemon gator-module-dkms
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
for vexpress.
tracking-armlt-iks-cpufreq
IKS cpufreq driver.
The latter is probably not vexpress specific, I just inherited it
because no-one else was handling it.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http:/
have the added complication thrown into the mix that
people use it a lot with QEMU ;-)
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, 2013-07-22 at 19:56 +, Yoder Stuart-B08248 wrote:
> Is there a written spec or description of how a boot program (u-boot, UEFI,
> hypervisor) boots an OS on ARM platforms?
There's some information in the Linux source in the file
Documentation/arm/Booting
On Tue, 2013-07-23 at 09:16 +0100, Jon Medhurst (Tixy) wrote:
> On Mon, 2013-07-22 at 19:56 +, Yoder Stuart-B08248 wrote:
> > Is there a written spec or description of how a boot program (u-boot, UEFI,
> > hypervisor) boots an OS on ARM platforms?
>
> There's som
On Thu, 2013-07-04 at 16:03 +0530, Vijay Kilari wrote:
> On Wed, Jul 3, 2013 at 8:48 PM, Jon Medhurst (Tixy) wrote:
> > On Wed, 2013-07-03 at 15:30 +0100, Jon Medhurst (Tixy) wrote:
> >> On Wed, 2013-07-03 at 19:03 +0530, Vijay Kilari wrote:
> >> > Hi,
> >
On Wed, 2013-07-03 at 15:30 +0100, Jon Medhurst (Tixy) wrote:
> On Wed, 2013-07-03 at 19:03 +0530, Vijay Kilari wrote:
> > Hi,
> >
> >With latest Linaro ARM kernel mentioned below fails to boot when
> > following configs are enabled
> > CONFIG_VEXPRESS_
e the version 5.0 Versatile Express CD, plus some extra patches from
ARM, plus some extra config files. All of these are needed to get a
working system.
>Also do I need to update Secure world to make it work with PSCI?
Yes. You need extra firmware that is not publicl
s a slightly larger kernel."
[1]
https://git.linaro.org/gitweb?p=kernel/configs.git;a=commit;h=46164b8909c93dc64a4fccd0cf93e5327265a50d
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
ion for offline ARMv7 PMUs
> ARM: perf: Allow multiple CPU PMUs per CPU
I dropped these in the IKS branch I feed into linux-linaro, and as of
today they are gone, i.e. in ll_20130620.0.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Mv7
> PMUs".
>
> Is there anything missing w.r.t. Arndale/Exynos to get perf to work on
> linux-linaro?
Probably not, and I now understand the patches you identified may not
work for their intended purpose anyway, so it is likely that they will
just get dropped when I next put together
t;0 98 0x4>,
> <0 99 0x4>;
> };
This isn't an area I have any knowledge in, sorry. But for what it's
worth that looks the same format as vexpress pmu nodes. IRQs are
obviously different, and the number of them match the number of CPUs.
--
Tixy
_
th cpu nodes. That's a mandatory attribute mentioned in the docs,
and also what the gator code searches for with of_find_node_by_type().
I'm still going to make gator codp with missing cpu nodes.
--
Tixy
> -Andy
>
> On 11 June 2013 22:34, Jon Medhurst (Tixy) wrote:
> >
cpu nodes itself.
I'll make gator behave one way or the other so it doesn't break on
platforms with missing cpu node or no IKS.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/170234.html
--
Tixy
___
linaro-dev mailin
nly used when
IKS is actually running.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
. From your BUG() output
below I think you're even more behind the times than you thought ;-)
[1]
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=shortlog;h=refs/tags/tracking-gator-llct-20130604.0
>thanks for the fix.
>
> -Andy
>
> On 11 June 201
ek ago...
https://bugs.launchpad.net/linaro/+bug/1184712
That fix is now in the llct.
--
Tixy
> root@localhost:~# modprobe gator
> [ 73.951009] [ cut here ]
> [ 73.955673] kernel BUG at
> /projects/linaro/linux-2.6/drivers/gator/gator_iks.c:43!
> [ 73.963260] Int
that implies regular llct updates as well.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
CONFIG_LEDS_CLASS=y
CONFIG_LEDS_GPIO=y
Does anyone know if QEMU emulates all the system register bits to
actually get the above things working? Linux drivers to use these
features were added to 3.7 so QEMU probably wouldn't have needed to
support them 9 months ago.
--
Ti
it.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=summary
>
> and couldn't find it.
It is there, as both a tag and branch named ll_20130322.0
https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=commit;h=0f66281a18ce706b4de2d4c208a852d358ecaf43
--
Tixy
__
=refs/heads/linux-linaro
>
Generally, that's the Linaro kernel tree people should use and what is
built daily and released monthly.
It's just it hasn't moved to 3.10 yet (will do in the next day or so)
but the topic branches which feed into it (that Liviu pointed o
On Wed, 2013-05-15 at 14:41 +0200, Ard Biesheuvel wrote:
> On 15 May 2013 14:38, Jon Medhurst (Tixy) wrote:
> > I see that the ARM version is following the pattern of SPARC64 and X86
> > SSSE3 in how it is configured, so for fear of opening a can of worms,
> > perhaps it&#x
On Wed, 2013-05-15 at 14:12 +0200, Ard Biesheuvel wrote:
> On 15 May 2013 14:05, Jon Medhurst (Tixy) wrote:
> > If the assembler version is always faster I would have thought that we
> > should always have it enabled and not have it as a user visible option.
> > Perh
On Wed, 2013-05-15 at 10:17 +0200, Ard Biesheuvel wrote:
> On 14 May 2013 18:49, Jon Medhurst (Tixy) wrote:
> >
> > This also enables CONFIG_CRYPTO_SHA1 which we didn't already have
> > enabled in our builds, so I assume nothing actually needs this option.
> > If t
me nothing actually needs this option.
If that's true, then it doesn't seem worth enabling an optimised version
of code which isn't going to be used. ;-)
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
;s worth, I'm happily building and booting Catalin Marinas's
> soc-armv8-model branch [1] with his latest version of the AArch64 boot-wrapper
> [2].
And this should pretty much be the same as what is in Linaro's kernel
because we just pull in Catalin's branch and reorganise/rebase patches
to fit in with our workflow.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
expect
-rc1 until May 13th and -rc3 will be in June.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Wed, 2013-04-17 at 09:14 -0400, Christopher Covington wrote:
> Hi Jon,
>
> On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
> > On Wed, 2013-04-17 at 06:21 +0200, Jonathan Aquilina wrote:
> >> Doesnt email run the risk of a patch slipping through the cracks?
>
lct'. The LT's who need to use this driver can
> have their modifications (if any) on top of it.
Each LT will have to make sure that their changes are suitably guarded
with #ifdefs to avoid stepping on each other's toes. But the
gt; #include
>
> This is still completely bogus, the __KERNEL__ symbol has no significance
> here.
> Either make the compiler define __linux__, or remove this #ifdef completely.
I don't have the full background here but thought I would point out that
a similar issue seems to h
ely on the people they pick to actually review
the patch, then rebase and resubmit the patch because the tip has moved
during the review process and then have someone with commit rights
accept it. And the web interface is horrible. You may have guessed I'm
not a fan ;-)
ly helps of all LT who want to / can harmonize their tree on
> llct basis.
>
> Tushar, do you have any opinion?
>
> Anyone who dealt with this code or at ARM (Tixy?)
I've never dealt with this code but one thing occurs to me: how would
you manage the user side binary blob? If differen
main Linaro kernel git. So this method
isn't foolproof.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
?p=kernel/linux-linaro-tracking.git;a=summary
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
ing to manually set anything. If you try this
latest UEFI, I suggest you also erase the flash as above, to make extra
sure there is no old config left over from a previous version.
[1]
https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&target=vemsd-armlt-20130225-001.zi
On Wed, 2013-02-20 at 11:28 -0500, Nicolas Pitre wrote:
> On Wed, 20 Feb 2013, Jon Medhurst (Tixy) wrote:
>
> > After some time investigating why I wasn't seeing some kernel section
> > mismatch errors that someone else was seeing, I found the cause was that
> > in L
thought I would spread this knowledge, because lack of section
mismatch warnings means we might miss some nasty bugs when developing
code.
If this is old news, then sorry for the noise.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linar
d I or someone else decided to drop the new drivers
from there tree. (Unlikely, and once the driver code if properly
consolidated I'll remove this old config option).
5. The rest of the warnings are Android options which are set but
require features (like runtime power management or USB OTG) which aren't
actually enabled on vexpress.
Cheers
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Fri, 2013-02-15 at 14:37 +, Dietmar Eggemann wrote:
> dropped linux-arm-ker...@lists.infradead.org
>
>
> On 15/02/13 12:06, Jon Medhurst (Tixy) wrote:
> > On Fri, 2013-02-15 at 10:33 +, Lorenzo Pieralisi wrote:
> >> On Fri, Feb 15, 2013 at 10:04:37AM +
On Fri, 2013-02-15 at 10:33 +, Lorenzo Pieralisi wrote:
> On Fri, Feb 15, 2013 at 10:04:37AM +, Jon Medhurst (Tixy) wrote:
> > On Thu, 2013-02-14 at 17:16 +, Will Deacon wrote:
> > > Hi Tixy,
> > >
> > > On Thu, Feb 14, 2013 at 05:07:43PM +, Jo
On Tue, 2013-02-05 at 15:13 +0800, Leo Yan wrote:
> On 01/29/2013 06:26 PM, Jon Medhurst (Tixy) wrote:
>
> >
> > What I suspect is that the configuration in SITE1/HBI0249A/board.txt
> > isn't right, particularly the value for SCC 0x700. We are currently
> >
al problem.)
The stack backtrace you see is a lockdep warning that is a bug in
mainline Linux that they are still deciding on how to fix. We have a
Linaro bug for the issue:
https://bugs.launchpad.net/linaro-landing-team-arm/+bug/1103485
--
Tixy
> I attached the boot up logs as well.
>
This is needed so the file is given executable permissions when it is
placed in the initrd. (Android doesn't use the file's attributes when
creating filesystems, instead it applies the set of rules in
system/core/include/private/android_filesystem_config.h)
This fixes bug: https://bugs.launchpad.n
On Thu, 2013-01-10 at 12:10 +, Punit Agrawal wrote:
> This patch fixes incorrect range check for the number of PMU counters. This
> caused the number of counters to be off-by-1.
>
> Signed-off-by: Punit Agrawal
> ---
> Hi Tixy,
>
> I discovered an embarassing rang
. I spoke to someone about the possible issues with IKS (the In
Kernel Switcher for big.LITTLE) and the conclusion was that this patch
would be innocuous.
After fixing some whitespace issues and adding that '.sh' into
init.arm-versatileexpress I've pushed the change
Patch 25c92a37a (arm64: Always select ARM_AMBA and GENERIC_GPIO)
expects platforms to have GPIO so we need to make sure vexpress
always has this by selecting ARCH_REQUIRE_GPIOLIB.
Without this change drivers like MMC fail to compile due to missing
gpio definitions like:
In file included from incl
s to the A7s.
>
> Lastly, it changes the makefile to include the new script in the target.
>
> Change-Id: I2fd2840acd4602d9145c7c2f2e839e5dda09ff99
> Signed-off-by: Punit Agrawal
> <mailto:punit.agra...@arm.com>
> ---
>
> Hi Tixy,
>
> I am not quite sure where to
to test the Android patches specifically
but I can confirm the interactive governor was running after boot and
the system generally seemed to work as expected.
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
wrote the patch but thought I would keep things
separate for clarity and avoid tripping up anyone modifying the code
later. We can spare 4 bytes of memory :-)
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Mon, 2013-01-07 at 13:59 +, Peter Maydell wrote:
> On 7 January 2013 13:47, Dave Martin wrote:
> > On Thu, Dec 20, 2012 at 12:23:48PM +, Jon Medhurst (Tixy) wrote:
> >> Does anyone have any further outstanding concerns or comments about my
> >> propose
On Fri, 2013-01-04 at 18:33 +0400, Andrey Konovalov wrote:
> I take it as the vexpress topic (for the ll tree) and the big.LITTLE
> topic (for the llct tree) are ready to switch to 3.8, correct?
Yes for the vexpress topic assuming big.LITTLE and Android topics move
to 3.8.
--
On Fri, 2013-01-04 at 15:14 +0530, Viresh Kumar wrote:
> On 4 January 2013 15:09, Jon Medhurst (Tixy) wrote:
> > I assume we'll be moving to Linux 3.8 for the January release cycle?
> >
> > For my part I have prepared a 3.8 branch for vexpress [1] which doesn't
>
p=landing-teams/working/arm/kernel.git;a=shortlog;h=refs/heads/integration-next
--
Tixy
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
On Fri, 2012-12-14 at 15:54 +, Jon Medhurst (Tixy) wrote:
> On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote:
> > On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy)
> > wrote:
> > > On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote:
> > >&
On Fri, 2012-12-14 at 16:00 +, Marc Zyngier wrote:
> On 14/12/12 15:54, Jon Medhurst (Tixy) wrote:
> > On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote:
> >> On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy)
> >> wrote:
> >>> On Thu, 2012
On Fri, 2012-12-14 at 10:10 -0500, Christoffer Dall wrote:
> On Fri, Dec 14, 2012 at 3:49 AM, Jon Medhurst (Tixy) wrote:
> > On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote:
> >> On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote:
> >>
> >>
On Thu, 2012-12-13 at 13:52 -0800, Christoffer Dall wrote:
> On Friday, December 7, 2012, Jon Medhurst (Tixy) wrote:
>
> > To enable CPU hotplug the need to provide some boot code at the
> reset
> > vector and which survives after the kernel has booted without being
> &
Adding some named people to the 'To' list to try and elicit review
comments... :-)
On Fri, 2012-12-07 at 11:35 +, Jon Medhurst (Tixy) wrote:
> To enable CPU hotplug the need to provide some boot code at the reset
> vector and which survives after the kernel has boot
Both the Android and Ubuntu have QA tests which expect to be able to
validate device-tree booting by looking in /proc/device-tree, so we
should enable this for all Linaro builds.
At the same time we can remove this option from ubuntu.conf as it's not
an Ubuntu specific requirement.
Signed-off-by:
To enable CPU hotplug the need to provide some boot code at the reset
vector and which survives after the kernel has booted without being
overwritten. We achieve this by the getting the linker script to place
the code in boot.S at address zero. This now means we can delete the
code that relocates t
On Tue, 2012-12-04 at 16:18 +, Peter Maydell wrote:
> On 3 December 2012 20:23, Jon Medhurst (Tixy) wrote:
> > We boot the kernel in non-secure mode and by default access to
> > the CCI device is not enabled for non-secure access, so we must
> > enable this if we wan
We boot the kernel in non-secure mode and by default access to
the CCI device is not enabled for non-secure access, so we must
enable this if we want Linux to manage CPU hotplug on big.LITTLE
models.
Signed-off-by: Jon Medhurst
---
Changes since V1:
- Add a DSB instructions
semi_loader.c |
We boot the kernel in non-secure mode and by default access to
the CCI device is not enabled for non-secure access, so we must
enable this if we want Linux to manage CPU hotplug on big.LITTLE
models.
Signed-off-by: Jon Medhurst
---
semi_loader.c |2 ++
1 file changed, 2 insertions(+)
diff -
From: Will Deacon
We need to set the flags when checking the feature register.
Signed-off-by: Will Deacon
---
I found this patch in another fork of the bootwrapper and it looks like
something we should have. On the A15 and big.LITTLE setups I've tested
it makes no difference so I guess the z f
On Fri, 2012-11-30 at 07:47 +0530, Viresh Kumar wrote:
> On 29 November 2012 21:43, Jon Medhurst (Tixy) wrote:
>
> > Linaro's kernel tree already has an interactive governor which is
> > provided by the Android topic branch, so isn't trying to integrate
> > an
LL request for master branch:
Linaro's kernel tree already has an interactive governor which is
provided by the Android topic branch, so isn't trying to integrate
another version going to cause a lot of problems for whoever maintains
the two versions and the person having to merge the
When the generic ftrace implementation modifies code for trace-points it
uses stop_machine() to call ftrace_modify_all_code() on one CPU. This
ultimately calls the ARM specific function ftrace_modify_code() which
updates the instruction and then does flush_icache_range(). As this
cache flushing onl
On Tue, 2012-11-20 at 12:39 +, Chris Redpath wrote:
> Hi Tixy,
>
> I can now reproduce it with MMC too, and the times are pretty much the same
> for me :(
>
> There is definitely some interaction with CPUFreq, the A7s stay at a low
> enough OPP
> that the busy threa
On Tue, 2012-11-20 at 11:32 +, Jon Medhurst (Tixy) wrote:
> > Tixy, could you try temporarily changing the default option to off for the
> > frequency-invariant load?
> >
> > I think it'll be at line 3631 in your fair.c
> >
> >
On Tue, 2012-11-20 at 11:31 +, Chris Redpath wrote:
> Hi Tixy,
>
> It seems that at least on my board, the presence of so many MMC timeouts
> causes the A7s to remain at the lowest frequency, presumably because the
> system load average is so low. With the frequency-invari
have the same
firmware and boot process as results from the instructions at:
http://releases.linaro.org/12.10/android/vexpress
> Tixy, could you try temporarily changing the default option to off for the
> frequency-invariant load?
>
> I thin
On Tue, 2012-11-20 at 13:00 +0530, Viresh Kumar wrote:
> On 19 November 2012 22:44, Andrey Konovalov
> wrote:
> > I won't pull the big-LITTLE-MP-master-v12 into the
> > linux-linaro-core-tracking tree today due to the issues found by Tixy.
> >
> > Tomorrow ev
On Mon, 2012-11-19 at 22:24 +0400, Andrey Konovalov wrote:
> On 11/19/2012 10:17 PM, Jon Medhurst (Tixy) wrote:
> > On Mon, 2012-11-19 at 21:14 +0400, Andrey Konovalov wrote:
> >> Viresh,
> >>
> >> I won't pull the big-LITTLE-MP-master-v12 into the
> >
On Mon, 2012-11-19 at 21:14 +0400, Andrey Konovalov wrote:
> Viresh,
>
> I won't pull the big-LITTLE-MP-master-v12 into the
> linux-linaro-core-tracking tree today due to the issues found by Tixy.
>
> Tomorrow evening I am going to pull this topic anyway - whether these
e push the kernel tree I had to my personal git area...
http://git.linaro.org/gitweb?p=people/tixy/kernel.git;a=shortlog;h=refs/heads/integration-android-vexpress
the Android userside I'm using the latest daily build:
https://android-build.linaro.org/builds/~linaro-android/vexpress-jb-gcc47-arm
rnel/sched/fair.c: In function 'update_entity_load_avg':
kernel/sched/fair.c:1469:26: error: 'struct sched_entity' has no member
named 'cfs_rq'
--
Tixy
> -x--x---
>
> The following changes sin
linaro/configs/big-LITTLE-MP.conf \
linaro/configs/vexpress-lt.conf"
Where vexpress.conf is the basic vexpress config for upstream code,
big-LITTLE-MP.conf is from PMWG, and vexpress-lt.conf if from the ARM LT
tree with the new bits.
--
Tixy
__
On Thu, 2012-11-15 at 11:37 +, Jon Medhurst (Tixy) wrote:
> On Thu, 2012-11-15 at 09:20 +0530, Tushar Behera wrote:
> > On 11/14/2012 07:41 PM, Ryan Harkin wrote:
> > > On 14 November 2012 11:38, Jon Medhurst (Tixy) wrote:
> [...]
> > >> Now that the LT bran
On Thu, 2012-11-15 at 09:20 +0530, Tushar Behera wrote:
> On 11/14/2012 07:41 PM, Ryan Harkin wrote:
> > On 14 November 2012 11:38, Jon Medhurst (Tixy) wrote:
[...]
> >> Now that the LT branches included in linux-linaro (ll) are based on
> >> llct, then they could modif
On Wed, 2012-11-14 at 20:30 +0400, Andrey Konovalov wrote:
> On 11/14/2012 08:12 PM, Jon Medhurst (Tixy) wrote:
> > On Wed, 2012-11-14 at 19:06 +0400, Andrey Konovalov wrote:
> >
> >>>> Or course, once Linaro's build and test infrastructure supports config
&g
T tree which comes from
> the big-LITTLE-MP topic.
Yes, and we don't use it, instead I cut'n'paste it into vexpress.conf
because CI jobs etc want a single config. And now I think about it, this
probably doesn't play well with the big.LITTLE In-Kernel Switcher (IKS)
proj
ve separate config fragments for
- basic board config
- new board enablement
- special features (e.g. big.LITTLE MP)
- testing or benchmarking config
and the configs could live in the tree relevant to the code they apply
to rather than having a single central board config we have to manage.
--
Tixy
__
gt; > we'd like to carry this patch as well.
>
> Hi Punit,
>
> I agree with you that many of us would be interested in using this patch,
> but i am not sure about which tree should it land into?
>
> @Andrey/Tixy: Any other better tree you can suggest for carrying th
.12).
>
> *ubuntu-sauce topic will be dropped* Anyone objects?
Definitely no objection from me :-) Ubuntu appears to work fine without
that topic and rebasing and forward porting it just seemed to add bugs.
--
Tixy
___
linaro-dev mailing list
li
anaged but, if it is possible, can the Gator version in 3.6 be replaced
by the new one from the branch '3.6-armlt-gator-5.12' in ARM LT tree
(git://git.linaro.org/landing-teams/working/arm/kernel) ?
Thanks
--
Tixy
___
linaro-dev mai
mmand-line args.
As I've started now, I may as well attach my images.txt file for TC2 and
my bootscr.txt file from the internal SD card, so you get the idea.
--
Tixy
VEMSD.tar.gz
Description: application/compressed-tar
___
linaro-dev mailing
On Wed, 2012-10-17 at 14:18 +0530, Viresh Kumar wrote:
> On 24 August 2012 16:39, Jon Medhurst (Tixy) wrote:
>
> > Sounds OK from my point of view, except that rather than fixed dates
> > each month the should probably be tied to the release dates. E.g. the
> > Monday of
@Andrey: I have applied this too. Please PULL it when you feel Tixy &
> Morten don't have any more patches to send :)
Well, I still have one more issue which _may_ be related, but if it is I
don't think I'm going to be producing any more patches before Monday
anyway. The is
On Fri, 2012-10-12 at 16:11 +0100, Morten Rasmussen wrote:
> Hi Tixy,
>
> Thanks for the patch. I think this patch is the right way to solve this
> issue.
>
> There is still a problem with the priority filter in
> hmp_down_migration() which Viresh pointed out earlier. Ther
1 - 100 of 255 matches
Mail list logo
