From: Patrik Gfeller <patrik.gfeller@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: atomisp kernel driver(s)
Date: Sun, 3 May 2020 14:31:20 +0200 [thread overview]
Message-ID: <20200503143120.008fa7c0@ASUS> (raw)
In-Reply-To: <20200503122350.2ade79ad@coco.lan>
On Sun, 3 May 2020 12:23:50 +0200
Mauro Carvalho Chehab <mchehab@kernel.org> wrote:
> Em Sun, 3 May 2020 10:46:12 +0200
> Patrik Gfeller <patrik.gfeller@gmail.com> escreveu:
>
> > On Sat, 2 May 2020 19:08:36 +0300
> > Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> >
> > Hi Andy,
> >
> [...]
> [...]
> [...]
> >
> > Thank you for your advice, I've tried various Android distros for x86 on
> > my device. Unfortunately none of the boots. I'll investigate if I can
> > make one of them to work. I also found that a predecessor of the driver
> > seemed to have worked for E3800. At lease there is a users guide from intel
> > (for Fedora 18):
> >
> > https://cdrdv2.intel.com/v1/dl/getcontent/331329
> >
> > Unfortunately this targets the 2400, and I have 2401 rev B chip. However -
> > I'll give Fedora 18 a try, but if the HW detection works as in the
> > current driver it will not accept my device.
>
> Wow, that sounds promising! Did you find where the Kernel patches
> and userspace applications are stored?
I've downloaded the Fedora 18 .iso file, unfortunately the USB stick
created is not able to boot. According to wikipedia the kernel used in
Fedora 18 is 3.6.10. I've downloaded the source an scanned it for
"atomisp" and "ov2680" - but did not find anything. After some more
research I've found a forum post about a patched kernel from timesys:
"... I have got a copy of atomisp driver from Timesys, which named
kernel-3.8.0-1.src.rpm. The driver be written by intel. But the
driver can not be correctly work on my platfrom(E3827). So i come to
be suspicious of the compatibility. And i want to know whether the
driver can be suitable for my platfrom?
Drivers infomation as blow:
- The version of atomisp driver: BYT_LSP_3.8_ISP_2013-12-06.patch
- The version of atomisp firmware: iaisp_2400_css.bin ..."
It looks as if this src.rpm is available here:
http://repository.timesys.com/buildsources/fedora/18/x86_64/source/
I'll now figure out how to open the .rpm package to have a look if
there is something about atomisp.
>
> [...]
> >
> > I could not find information about MRD-7 CRB HW. Do you still have this
> > HW? Fedora 18 might be worth a try if it uses a 2400 chip.
> >
> [...]
> >
> > with kind regards,
> > Patrik
> >
>
>
>
> Thanks,
> Mauro
next prev parent reply other threads:[~2020-05-03 12:31 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 14:39 atomisp kernel driver(s) Patrik Gfeller
2020-04-18 15:25 ` Mauro Carvalho Chehab
2020-04-18 15:26 ` Mauro Carvalho Chehab
2020-04-18 15:37 ` Patrik Gfeller
2020-04-19 23:31 ` Mauro Carvalho Chehab
2020-04-20 17:48 ` Patrik Gfeller
2020-04-20 18:27 ` Patrik Gfeller
2020-04-20 20:47 ` Mauro Carvalho Chehab
2020-04-22 17:56 ` Patrik Gfeller
2020-04-22 19:13 ` Mauro Carvalho Chehab
2020-04-24 8:52 ` Patrik Gfeller
2020-04-24 9:10 ` Patrik Gfeller
2020-04-24 10:07 ` Patrik Gfeller
2020-04-24 13:58 ` Patrik Gfeller
2020-04-25 11:22 ` Mauro Carvalho Chehab
2020-04-26 11:38 ` Patrik Gfeller
2020-04-26 16:50 ` Mauro Carvalho Chehab
2020-04-27 18:31 ` Patrik Gfeller
2020-04-27 21:50 ` Mauro Carvalho Chehab
2020-04-28 17:59 ` Patrik Gfeller
2020-04-28 23:13 ` Mauro Carvalho Chehab
2020-04-29 17:56 ` Patrik Gfeller
2020-04-29 18:17 ` Mauro Carvalho Chehab
2020-04-30 7:56 ` Patrik Gfeller
2020-04-30 10:55 ` Mauro Carvalho Chehab
2020-04-30 15:09 ` Patrik Gfeller
2020-04-30 22:25 ` Mauro Carvalho Chehab
2020-05-01 8:54 ` Patrik Gfeller
2020-05-01 9:38 ` Mauro Carvalho Chehab
2020-05-01 17:31 ` Patrik Gfeller
2020-05-01 19:30 ` Mauro Carvalho Chehab
2020-05-02 8:15 ` Patrik Gfeller
2020-05-02 9:20 ` Patrik Gfeller
2020-05-02 10:00 ` Mauro Carvalho Chehab
2020-05-02 9:34 ` Mauro Carvalho Chehab
2020-05-02 14:29 ` Patrik Gfeller
2020-05-02 16:28 ` Mauro Carvalho Chehab
2020-05-02 18:23 ` Patrik Gfeller
2020-05-02 14:50 ` Patrik Gfeller
2020-04-18 15:29 ` Patrik Gfeller
2020-04-25 2:39 ` Laurent Pinchart
2020-04-25 10:36 ` Patrik Gfeller
2020-04-25 12:19 ` Mauro Carvalho Chehab
2020-04-26 19:07 ` Laurent Pinchart
2020-04-26 20:51 ` Mauro Carvalho Chehab
2020-04-26 19:33 ` Laurent Pinchart
2020-04-28 18:13 ` Patrik Gfeller
2020-04-26 7:44 ` Patrik Gfeller
2020-04-26 19:17 ` Laurent Pinchart
2020-04-29 17:59 ` Patrik Gfeller
2020-04-29 18:19 ` Laurent Pinchart
2020-04-30 15:28 ` Patrik Gfeller
2020-05-02 16:08 ` Andy Shevchenko
2020-05-02 17:04 ` Mauro Carvalho Chehab
2020-05-02 17:33 ` Andy Shevchenko
2020-05-03 10:18 ` Mauro Carvalho Chehab
2020-05-12 10:20 ` Mauro Carvalho Chehab
2020-05-12 11:12 ` Andy Shevchenko
2020-05-12 11:21 ` Andy Shevchenko
2020-05-12 14:56 ` Mauro Carvalho Chehab
2020-05-12 16:01 ` Andy Shevchenko
2020-05-13 18:36 ` Patrik Gfeller
2020-05-20 8:04 ` Mauro Carvalho Chehab
2020-05-13 9:56 ` Mauro Carvalho Chehab
2020-05-03 8:46 ` Patrik Gfeller
2020-05-03 10:23 ` Mauro Carvalho Chehab
2020-05-03 12:31 ` Patrik Gfeller [this message]
2020-05-03 13:36 ` Patrik Gfeller
2020-05-03 14:43 ` 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=20200503143120.008fa7c0@ASUS \
--to=patrik.gfeller@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).