linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Finn Rayment <finn@rayment.fr>
To: linux-media@vger.kernel.org
Subject: [GIT,PULL] Ressurect the atomisp staging driver
Date: Sat, 16 May 2020 15:23:57 +0200	[thread overview]
Message-ID: <7fa44621-963f-2d55-ab91-0fee483a94f5@rayment.fr> (raw)

Hello,

I've cloned HEAD from atomisp_v2 (commit bb1407f0d...), tried to compile 
it on a T100TA and have received the following error:

arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function 
__kvm_gfn_to_hva_cache_init:
arch/x86/kvm/../../../virt/kvm/kvm_main.c:2442:42: error: nr_pages_avail 
may be used uninitialized in this function [-Werror=maybe-uninitialized]

Commenting out the third line in arch/x86/kvm/Makefile has solved this 
for me. Aside from warnings, this is the only error I receive during 
compilation.

After installing the kernel and booting to Arch Linux, it gets stuck at 
"Loading initial ramdisk" with no extra information even with 
`loglevel=7` set. I will try to diagnose the issue and ensure I haven't 
incorrectly installed the kernel - will also try to compile on another 
computer.

Let me know if I can offer any other help or more information, I would 
love to contribute to the development of these drivers.

Regards,
Finn.

             reply	other threads:[~2020-05-16  5:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 13:23 Finn Rayment [this message]
     [not found] ` <20200516115459.4a24063b@coco.lan>
2020-05-16 19:53   ` [GIT,PULL] Ressurect the atomisp staging driver Finn Rayment
2020-05-19 17:37     ` Mauro Carvalho Chehab
  -- strict thread matches above, loose matches on Subject: below --
2020-05-01 19:57 [GIT PULL] " Mauro Carvalho Chehab
2020-05-02  6:03 ` Greg KH
2020-05-20  7:48   ` Mauro Carvalho Chehab
2020-05-03  9:19 ` Francescodario Cuzzocrea
2020-05-03 10:07   ` Mauro Carvalho Chehab
2020-05-03 15:32   ` Mauro Carvalho Chehab
     [not found]     ` <CADnVkj96W0QfthukTKQ0a-i2fH1buooH3BEgfy22J9H9=_PcKA@mail.gmail.com>
2020-05-03 16:07       ` Patrik Gfeller
2020-05-04  8:16         ` Patrik Gfeller
2020-05-04  8:49           ` Mauro Carvalho Chehab
2020-05-04 10:45             ` Patrik Gfeller
2020-05-04 12:08               ` Mauro Carvalho Chehab
2020-05-04 13:44                 ` Patrik Gfeller
2020-05-15  8:32                   ` Mauro Carvalho Chehab
2020-05-15  9:10                     ` Hans de Goede
2020-05-15  9:42                       ` Mauro Carvalho Chehab
2020-05-19  7:39                         ` Mauro Carvalho Chehab
2020-05-19 17:36                           ` Mauro Carvalho Chehab
2020-05-22 10:46                             ` Hans de Goede
2020-05-22 11:42                               ` Mauro Carvalho Chehab
2020-05-23  8:00                                 ` Mauro Carvalho Chehab
2020-05-27 16:23                                   ` Hans de Goede
2020-05-27 17:36                                     ` Mauro Carvalho Chehab
2020-05-06 15:10                 ` Mauro Carvalho Chehab
2020-05-03  9:23 ` bosconovic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fa44621-963f-2d55-ab91-0fee483a94f5@rayment.fr \
    --to=finn@rayment.fr \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).