[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfzUt_kgzNuXt7pYG4UWcZMF9MtnT1n1j8thOys=OJ+ZA@mail.gmail.com>
Date: Wed, 13 Jan 2021 14:02:09 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Rob Landley <rob@...dley.net>
Cc: Linus Walleij <linus.walleij@...aro.org>,
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Gerhard Pircher <gerhard_pircher@....net>,
Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Sparc kernel list <sparclinux@...r.kernel.org>,
Linux-sh list <linux-sh@...r.kernel.org>
Subject: Re: Old platforms: bring out your dead
On Wed, Jan 13, 2021 at 9:58 AM Rob Landley <rob@...dley.net> wrote:
> On 1/12/21 4:46 PM, Linus Walleij wrote:
...
> Testing that a basic superh system still builds and boots under qemu and j-core
> I can commit to doing regularly. Testing specific hardware devices on boards I
> don't regularly use is a lot harder.
In our lab we have different hardware connected (including non-x86,
mostly due to maintenance and testing drivers) and it allows us to run
more or less fresh kernels on it. Setup is pretty simple: server with
connected USB 2 serial, network, etc, power cutters, relays to emulate
power button presses for the hardware that can't be turned off and on
by cutting the main power (usual case for tablets / phones) and so on.
>From a software point of view we use a netboot image [1][2] which
allows us to kexec kernel downloaded via net.
Now to the point, perhaps organizations like LF can set up something
like this with one technician to support this and pay electricity /
internet bills?
[1]: https://github.com/andy-shev/linux/tree/netboot (just a set of
kernel configuration options on top of defaults)
[2]: https://github.com/andy-shev/buildroot/tree/intel/board/intel/common
(see README in the folder)
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists