Upgrade to 15.11 from 15.02 results in quota exceded message

[Martin Stein]

Hi Bob,

Am 03.12.2015 um 13:37 schrieb Bob Stewart:
> The scenario I run includes sdcard, gpio, gp timers, uarts, i2c, and PWM
> drivers and vfs is also in there. All of this, with my modified base-hw
> kernel, appears to be running as it does in 15.02 with the exception of
> the PWM driver. The log from the 15.11 implementation shows nothing
> exceptional (attached) and is practically identical to what is output on

While reading this, it came to my mind that somewhere around the
beginning of the year, interrupt semantics have changed on base-hw. In
the past, an IRQ session, once opened, directly started handling
interrupts. Today, the handling, and therefore also the reception, of
interrupts doesn't start until an initial 'Irq_session::irq_ack' call. I
know, its a shot in the dark. But just to be sure you may check whether
your drivers already send this initial ack.

> 15.02. Running my PWM driver in verbose mode shows that data received
> from sensors on the i2c bus and from a manual input controller is being
> correctly received, processed, and sent to the PWM driver. The PWM does
> some signal conditioning and writes updated duty cycle values to an IO
> register from which the SoC's pwm subsystem sends the modified pulse to
> an IO pin. That pin is attached to a motor ESC which provides the power
> to drive the motor. The motor never receives the pulse. So, presumably,

My first intention is, that this could also be a bad GPIO configuration.
However, with the information I have this can only be a vague guess. Can
you share your source code including the run script that you're using?
Most comfortable would be an on-line git branch :)

> there is an issue with IO mapping and the signal is not going to the
> correct register location. I notice in the 5.11 release notes that there
> have been changes in the area of memory mapped IO, so I'm starting to

Sorry, I'm afraid that I do not know which changes you mean. Could you
please go in more detail?

> explore that avenue. I have not touched the PWM driver code in more than
> a year so I doubt that the problem is there.

Cheers,
Martin