[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfzP8-0wKmPTTKYe+fc6=r_4sVcJPyOsM8YTuH=i4rxmA@mail.gmail.com>
Date: Thu, 5 Dec 2019 19:02:21 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bgolaszewski@...libre.com>,
Kent Gibson <warthog618@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 10/11] gpiolib: add new ioctl() for monitoring changes
in line info
On Thu, Dec 5, 2019 at 3:47 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> czw., 5 gru 2019 o 11:27 Andy Shevchenko <andy.shevchenko@...il.com> napisał(a):
> > On Thu, Dec 5, 2019 at 11:42 AM Bartosz Golaszewski
> > <bgolaszewski@...libre.com> wrote:
> > > śr., 4 gru 2019 o 23:34 Andy Shevchenko <andy.shevchenko@...il.com> napisał(a):
> > > > On Wed, Dec 4, 2019 at 6:03 PM Bartosz Golaszewski <brgl@...ev.pl> wrote:
> > So, the test cases, I can imagine of, should include (k - kernel, u - user):
> > - 64k-64u: LE and BE
> > - 64k-32u: LE and BE
> > - 32k-32u: LE and BE
>
> I usually use qemu VMs built with yocto for testing but I don't see
> any way of creating a 32-bit user-space with 64-bit kernel. Any ideas
> on how to prepare a testing environment?
In my case it's very easy. I do
- compile kernel as 64-bit separately;
- compile initramfs of Buildroot distro with external kernel build provided.
That's setup in which I observed the issue.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists