Hello Andreas,
On Fri, Nov 30, 2018 at 10:12:47PM +0100, Andreas Schwab wrote:
> On Nov 30 2018, Andreas Schwab wrote:
>
> > [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1
> > 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018
> > [0.00] Saving 190 bytes of
On Fri, Nov 30, 2018 at 10:24 PM Michael Schmitz wrote:
> Am 01.12.2018 um 10:12 schrieb Andreas Schwab:
> > On Nov 30 2018, Andreas Schwab wrote:
> >
> >> [0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1
> >> 20180712 (GCC)) #3 Fri Nov 30 20:53:33 CET 2018
> >> [
On Sat, Dec 01, 2018 at 11:51:52AM +1300, Michael Schmitz wrote:
> Andreas,
>
> Am 01.12.2018 um 11:23 schrieb Andreas Schwab:
> >On Dez 01 2018, Michael Schmitz wrote:
> >
> >>Must be a new kind of monster kernel that wouldn't fit inside 14 MB.
> >
> >There's way more than the kernel that must
Geert,
On 3/12/18 11:57 AM, Michael Schmitz wrote:
Only a single memory chunk (ST-RAM), and kernel loaded there.
Same here.
The only memory-related option I have in my ARAnyM config is
FastRAM = 256
and that works.
Andreas: can you please share your ARAnyM config, so we can reproduce?
Geert,
On 2/12/18 10:57 PM, Geert Uytterhoeven wrote:
On Fri, Nov 30, 2018 at 10:24 PM Michael Schmitz wrote:
Am 01.12.2018 um 10:12 schrieb Andreas Schwab:
On Nov 30 2018, Andreas Schwab wrote:
[0.00] Linux version 4.19.0 (andr...@igel.home) (gcc version 8.1.1
20180712 (GCC)) #3
On 3/12/18 12:04 AM, Mike Rapoport wrote:
On Sat, Dec 01, 2018 at 11:51:52AM +1300, Michael Schmitz wrote:
Andreas,
Am 01.12.2018 um 11:23 schrieb Andreas Schwab:
On Dez 01 2018, Michael Schmitz wrote:
Must be a new kind of monster kernel that wouldn't fit inside 14 MB.
There's way more
Hi Mike,
Am 03.12.2018 um 00:04 schrieb Mike Rapoport:
I don't know what were the shortcomings of the old memory model, and why
ST-RAM and FastRAM are treated differently, so probably the simplest way
would be just inform memblock that the ST-RAM is not available to it:
diff --git
On Thu, Nov 29, 2018 at 12:04 PM Andy Shevchenko
wrote:
> Use %ptR instead of open coded variant to print content of
> struct rtc_time in human readable format.
>
> Cc: Geert Uytterhoeven
> Cc: linux-m68k
> Signed-off-by: Andy Shevchenko
Reviewed-by: Geert Uytterhoeven
Acked-by: Geert
Hi Dmitry,
On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin wrote:
> syscall_get_arch() is required to be implemented on all architectures
> in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO
> request.
>
> Signed-off-by: Dmitry V. Levin
Reviewed-by: Geert Uytterhoeven
Hi Firoz,
On Tue, Nov 13, 2018 at 7:01 AM Firoz Khan wrote:
> The system call tables are in different format in all
> architecture and it will be difficult to manually add,
> modify or delete the syscall table entries in the res-
> pective files. To make it easy by keeping a script and
> which
Hi Geert,
On Sun, Dec 02, 2018 at 11:29:10AM +0100, Geert Uytterhoeven wrote:
> Hi Dmitry,
>
> On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin wrote:
> > syscall_get_arch() is required to be implemented on all architectures
> > in order to extend the generic ptrace API with
Hi Dmitry,
On Mon, Dec 3, 2018 at 1:24 AM Dmitry V. Levin wrote:
> On Sun, Dec 02, 2018 at 11:29:10AM +0100, Geert Uytterhoeven wrote:
> > On Tue, Nov 20, 2018 at 1:15 AM Dmitry V. Levin wrote:
> > > syscall_get_arch() is required to be implemented on all architectures
> > > in order to extend
Hi Michael, Mike,
On Mon, Dec 3, 2018 at 5:53 AM Michael Schmitz wrote:
> Am 03.12.2018 um 00:04 schrieb Mike Rapoport:
> > I don't know what were the shortcomings of the old memory model, and why
> > ST-RAM and FastRAM are treated differently, so probably the simplest way
> > would be just
13 matches
Mail list logo
