LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <firstname.lastname@example.org> To: Arnd Bergmann <email@example.com> Cc: Christoph Hellwig <firstname.lastname@example.org>, Mauro Carvalho Chehab <email@example.com>, Hans Verkuil <firstname.lastname@example.org>, Arvind Yadav <email@example.com>, firstname.lastname@example.org, Linux Media Mailing List <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, Trent Piepho <email@example.com> Subject: Re: [PATCH] media: zoran: move to dma-mapping interface Date: Wed, 25 Apr 2018 14:22:29 -0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAK8P3a0CHSC7yP3x8xDJgcg5xMzD1-sC-rmBJECtYvGFmyG4vQ@mail.gmail.com> Em Wed, 25 Apr 2018 17:58:25 +0200 Arnd Bergmann <email@example.com> escreveu: > On Wed, Apr 25, 2018 at 5:26 PM, Christoph Hellwig <firstname.lastname@example.org> wrote: > > On Wed, Apr 25, 2018 at 01:15:18PM +0200, Arnd Bergmann wrote: > >> That thought had occurred to me as well. I removed the oldest ISDN > >> drivers already some years ago, and the OSS sound drivers > >> got removed as well, and comedi got converted to the dma-mapping > >> interfaces, so there isn't much left at all now. This is what we > >> have as of v4.17-rc1: > > > > Yes, I've been looking at various grotty old bits to purge. Usually > > I've been looking for some non-tree wide patches and CCed the last > > active people to see if they care. In a few cases people do, but > > most often no one does. > > Let's start with this one (zoran) then, as Mauro is keen on having > all media drivers compile-testable on x86-64 and arm. > > Trent Piepho and Hans Verkuil both worked on this driver in the > 2008/2009 timeframe and those were the last commits from anyone > who appears to have tested their patches on actual hardware. Zoran is a driver for old hardware. I don't doubt that are people out there still using it, but who knows? I have a few those boards packed somewhere. I haven't work with PCI hardware for a while. If needed, I can try to seek for them and do some tests. I need first to unpack a machine with PCI slots... the NUCs I generally use for development don't have any :-) Anyway, except for virt_to_bus() and related stuff, I think that this driver is in good shape, as Hans did a lot of work in the past to make it to use the current media framework. > > Trent, Hans: do you have reason to believe that there might still > be users out there? > > Arnd Thanks, Mauro
next prev parent reply other threads:[~2018-04-25 17:22 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-24 20:40 [PATCH] media: zoran: move to dma-mapping interface Arnd Bergmann 2018-04-25 6:15 ` Christoph Hellwig 2018-04-25 7:08 ` Arnd Bergmann 2018-04-25 7:21 ` Christoph Hellwig 2018-04-25 11:15 ` Arnd Bergmann 2018-04-25 15:26 ` Christoph Hellwig 2018-04-25 15:58 ` Arnd Bergmann 2018-04-25 17:22 ` Mauro Carvalho Chehab [this message] 2018-04-25 17:43 ` Trent Piepho 2018-05-07 9:05 ` Hans Verkuil 2018-05-07 21:17 ` Arnd Bergmann 2018-04-25 17:27 ` [Mjpeg-users] " Bernhard Praschinger 2018-04-26 17:49 ` kbuild test robot
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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: linkBe 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).