From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Patrik Gfeller <patrik.gfeller@gmail.com>
Cc: Francescodario Cuzzocrea
<francescodario.cuzzocrea@mail.polimi.it>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL] Ressurect the atomisp staging driver
Date: Wed, 6 May 2020 17:10:30 +0200 [thread overview]
Message-ID: <20200506171030.6b0a0bdc@coco.lan> (raw)
In-Reply-To: <20200504140833.11dd5622@coco.lan>
Em Mon, 4 May 2020 14:08:33 +0200
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
> Em Mon, 4 May 2020 12:45:39 +0200
> Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
>
> > On Mon, 4 May 2020 10:49:34 +0200
> > Mauro Carvalho Chehab <mchehab@kernel.org> wrote:
> >
> > > Em Mon, 4 May 2020 10:16:28 +0200
> > > Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
> > >
> > > > On Sun, 3 May 2020 18:07:51 +0200
> > > > Patrik Gfeller <patrik.gfeller@gmail.com> wrote:
> > > >
> > > [...]
> > > >
> > > > I was not able yet to compile the kernel 4.4 successfully yet.
I was able to build this tree with gcc-7:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=yocto_intel_atom
Please notice that one patch there changed the default from "gcc"
to "gcc-7", just to avoid needing to pass "make CC=gcc-7" every time.
This is not needed and can be dropped if you want to use something else.
This patch mark some drivers as BROKEN, as one of the yocto's patch
changed the way Intel mid works, removing a "regmap" field from it.
I would try to build like this, as it should probably be enough to test
the atomisp driver on an ISP2401 machine.
I this won't work, we may need to do something else.
Thanks,
Mauro
next prev parent reply other threads:[~2020-05-06 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 19:57 [GIT PULL] Ressurect the atomisp staging driver 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-15 9:37 ` Ressurect the atomisp staging driver - current progress Mauro Carvalho Chehab
2020-05-06 15:10 ` Mauro Carvalho Chehab [this message]
2020-05-03 9:23 ` [GIT PULL] Ressurect the atomisp staging driver bosconovic
2020-05-16 13:23 [GIT,PULL] " Finn Rayment
[not found] ` <20200516115459.4a24063b@coco.lan>
2020-05-16 19:53 ` Finn Rayment
2020-05-19 17:37 ` Mauro Carvalho Chehab
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=20200506171030.6b0a0bdc@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=francescodario.cuzzocrea@mail.polimi.it \
--cc=linux-media@vger.kernel.org \
--cc=patrik.gfeller@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.