From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Greg KH <gregkh@suse.de>
Cc: Jean-Francois Dagenais <jeff.dagenais@gmail.com>,
hjk@hansjkoch.de, tglx@linutronix.de, linux-pci@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: extra large DMA buffer for PCI-E device under UIO
Date: Mon, 21 Nov 2011 19:17:24 +0100 [thread overview]
Message-ID: <20111121181724.GB12011@local> (raw)
In-Reply-To: <20111121173620.GA5028@suse.de>
On Mon, Nov 21, 2011 at 09:36:20AM -0800, Greg KH wrote:
> On Mon, Nov 21, 2011 at 10:31:07AM -0500, Jean-Francois Dagenais wrote:
> > Hi Greg, thanks for your answer...
> >
> > On Nov 18, 2011, at 17:08, Greg KH wrote:
> >
> > > On Fri, Nov 18, 2011 at 04:16:23PM -0500, Jean-Francois Dagenais wrote:
> > >> Hello fellow hackers.
> > >>
> > >> I am maintaining a UIO based driver for a PCI-E data acquisition device.
> > >>
> > >> I map BAR0 of the device to userspace. I also map two memory areas,
> > >> one is used to feed instructions to the acquisition device, the other
> > >> is used autonomously by the PCI device to write the acquired data.
> > >
> > > Nice, have a pointer to your driver anywhere so we can include it in the
> > > main kernel tree to make your life easier?
> > As I said in a parallel answer from "Hans J. Koch" <hjk@hansjkoch.de>,
> > the driver, although GPL'ed, is quite uninteresting except for us here at
> > Sonatest.
>
> I really doubt that,
So do I. We never had a driver allocating so much memory.
> and you should submit it anyway to allow us to
> change it when the in-kernel apis change in the future. It will save
> you time in the long run and make things easier for you (look, your
> driver is automatically included in all distros!, people fix your bugs,
> etc.)
Exactly.
>
> > About merging the driver to mainline, I guess it would only be interesting for
> > the recipe I demonstrate. Please advise.
>
> That is a recipe that I'm sure others will use, and need help on in the
> future.
They already needed it in the past, and they usually try to get it by
writing me private mail.
>
> So please submit a patch, that will make it easier to help you out.
Yes, please do. The more different drivers we have under /drivers/uio, the
better. Didn't you use one of the existing drivers as a template for yours?
Thanks,
Hans
next prev parent reply other threads:[~2011-11-21 18:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 21:16 extra large DMA buffer for PCI-E device under UIO Jean-Francois Dagenais
2011-11-18 22:08 ` Greg KH
2011-11-21 15:31 ` Jean-Francois Dagenais
2011-11-21 17:36 ` Greg KH
2011-11-21 18:17 ` Hans J. Koch [this message]
[not found] ` <4A52B447-8E21-43F6-A38E-711E36F89A34@gmail.com>
2011-11-21 19:29 ` Hans J. Koch
2011-11-22 15:24 ` Jean-Francois Dagenais
2011-11-22 15:35 ` Michael S. Tsirkin
2011-11-22 16:54 ` Jean-Francois Dagenais
2011-11-22 17:27 ` Matthew Wilcox
2011-11-22 17:40 ` Michael S. Tsirkin
2011-11-22 17:37 ` Michael S. Tsirkin
2011-11-22 17:54 ` Hans J. Koch
2011-11-22 18:40 ` Michael S. Tsirkin
2011-11-22 18:52 ` Hans J. Koch
2011-11-22 19:50 ` Jean-Francois Dagenais
2011-11-23 8:20 ` Michael S. Tsirkin
2011-11-22 16:05 ` Hans J. Koch
2011-11-22 19:57 ` Jean-Francois Dagenais
2013-01-23 2:00 ` Jean-François Dagenais
2011-11-18 22:27 ` Hans J. Koch
2011-11-21 15:10 ` Jean-Francois Dagenais
2011-11-21 15:47 ` Rolf Eike Beer
2011-11-21 16:01 ` Jean-Francois Dagenais
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=20111121181724.GB12011@local \
--to=hjk@hansjkoch.de \
--cc=gregkh@suse.de \
--cc=jeff.dagenais@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
/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