+CC ARC gnu folks, Anton who maintains an internal build system
On 03/22/2017 08:02 PM, Waldemar Brodkorb wrote:
> Hi,
>
> I want to success following change:
>
> From cde74b83f9b204bf56f304224654e4993dc56efc Mon Sep 17 00:00:00 2001
> From: Waldemar Brodkorb
> Date: Tue, 21 Mar 2017 20:04:21 +0
Hi,
>
> +CC ARC gnu folks, Anton who maintains an internal build system
>
>
> On 03/22/2017 08:02 PM, Waldemar Brodkorb wrote:
> > Hi,
> >
> > I want to success following change:
> >
> > From cde74b83f9b204bf56f304224654e4993dc56efc Mon Sep 17 00:00:00
> 2001
> > From: Waldemar Brodkorb
> > Da
MotherBoard section has its "ranges" set to 0xE000_-0xF000_.
But UIO node maps 4 different areas in different memory locations
and all outside MB's ranges.
That obviously breaks UIO mappings in runtime.
Signed-off-by: Alexey Brodkin
Cc: Vineet Gupta
Cc: Ruud Derwig
Cc: sta...@vger.kern
+CC Jos !
-Vineet
On 03/23/2017 10:34 AM, Alexey Brodkin wrote:
> MotherBoard section has its "ranges" set to 0xE000_-0xF000_.
> But UIO node maps 4 different areas in different memory locations
> and all outside MB's ranges.
>
> That obviously breaks UIO mappings in runtime.
>
> Signed-o
In the next changes, we track the interrupts but we discard the timers as
that does not make sense. The next interrupt on a timer is predictable.
But, the API request_percpu_irq does not allow to pass a flag, hence specifying
if the interrupt type is a timer.
Solve this by passing a 'flags' param
On 03/23/2017 10:42 AM, Daniel Lezcano wrote:
> In the next changes, we track the interrupts but we discard the timers as
> that does not make sense. The next interrupt on a timer is predictable.
>
> But, the API request_percpu_irq does not allow to pass a flag, hence
> specifying
> if the interru
Hi Daniel,
On Thu, Mar 23, 2017 at 06:42:01PM +0100, Daniel Lezcano wrote:
> In the next changes, we track the interrupts but we discard the timers as
> that does not make sense. The next interrupt on a timer is predictable.
Sorry, but I could not parse this.
[...]
> diff --git a/drivers/perf/
Hi Mark,
On Thu, Mar 23, 2017 at 06:54:52PM +, Mark Rutland wrote:
> Hi Daniel,
>
> On Thu, Mar 23, 2017 at 06:42:01PM +0100, Daniel Lezcano wrote:
> > In the next changes, we track the interrupts but we discard the timers as
> > that does not make sense. The next interrupt on a timer is pred
Hi,
I am preparing for next release.
I want to push attached cleanup of defconfigs as discussed earlier
on the uClibc-ng mailinglist.
@Anton: so you need to use your own defconfig for your toolchain
builds. I suggest to be similar to the Buildroot config.
best regards
Waldemar
Anton Kolesov wr
