All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	"Hans J. Koch" <hjk@linutronix.de>,
	linux-kernel@vger.kernel.org, gregkh@suse.de,
	linux-sh@vger.kernel.org, Katsuya MATSUBARA <matsu@igel.co.jp>
Subject: Re: [PATCH 00/03][RFC] Reusable UIO Platform Driver
Date: Wed, 21 May 2008 08:50:33 +0000	[thread overview]
Message-ID: <20080521085033.GA29607@digi.com> (raw)
In-Reply-To: <aec7e5c30805210122w5bdb8443r69bb7776e085276b@mail.gmail.com>

Hello,

Magnus Damm wrote:
> On Wed, May 21, 2008 at 5:05 PM, Uwe Kleine-König
> <Uwe.Kleine-Koenig@digi.com> wrote:
> > @Magnus: Maybe you can provide the userspace part of the driver?
> > How is that mapping used there?
> 
> [Added Matsubara-san as CC]
> 
> Sure, here is a little test program. Have a look at "uio_mem". The
> "address" member contains the physical address that can be used for
> bus mastering DMA. Compare that to "iomem" which is the pointer to the
> virtual memory area in user space.
> 
> Hope this helps!
Yes it does.  I thought the physical address is stored in internal_addr
and the virtual in addr, but it's the other way round.  Thanks.

Best regards
Uwe

-- 
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962

WARNING: multiple messages have this Message-ID (diff)
From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	"Hans J. Koch" <hjk@linutronix.de>,
	<linux-kernel@vger.kernel.org>, <gregkh@suse.de>,
	<linux-sh@vger.kernel.org>, Katsuya MATSUBARA <matsu@igel.co.jp>
Subject: Re: [PATCH 00/03][RFC] Reusable UIO Platform Driver
Date: Wed, 21 May 2008 10:50:33 +0200	[thread overview]
Message-ID: <20080521085033.GA29607@digi.com> (raw)
In-Reply-To: <aec7e5c30805210122w5bdb8443r69bb7776e085276b@mail.gmail.com>

Hello,

Magnus Damm wrote:
> On Wed, May 21, 2008 at 5:05 PM, Uwe Kleine-König
> <Uwe.Kleine-Koenig@digi.com> wrote:
> > @Magnus: Maybe you can provide the userspace part of the driver?
> > How is that mapping used there?
> 
> [Added Matsubara-san as CC]
> 
> Sure, here is a little test program. Have a look at "uio_mem". The
> "address" member contains the physical address that can be used for
> bus mastering DMA. Compare that to "iomem" which is the pointer to the
> virtual memory area in user space.
> 
> Hope this helps!
Yes it does.  I thought the physical address is stored in internal_addr
and the virtual in addr, but it's the other way round.  Thanks.

Best regards
Uwe

-- 
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962

  reply	other threads:[~2008-05-21  8:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 10:51 [PATCH 00/03][RFC] Reusable UIO Platform Driver Magnus Damm
2008-05-20 10:51 ` Magnus Damm
2008-05-20 10:51 ` [PATCH 01/03] uio: Add enable_irq() callback Magnus Damm
2008-05-20 10:51   ` Magnus Damm
2008-05-21 11:58   ` Magnus Damm
2008-05-21 11:58     ` Magnus Damm
2008-05-22 20:18     ` Hans J. Koch
2008-05-22 20:18       ` Hans J. Koch
2008-05-23  1:24       ` Magnus Damm
2008-05-23  1:24         ` Magnus Damm
2008-05-23  8:43         ` Hans J. Koch
2008-05-23  8:43           ` Hans J. Koch
2008-05-20 10:51 ` [PATCH 02/03] uio: Add uio_platform driver Magnus Damm
2008-05-20 10:51   ` Magnus Damm
2008-05-20 10:51 ` [PATCH 03/03] sh: Export sh7343/sh7722/sh7723 VPU/VEU blocks Magnus Damm
2008-05-20 10:51   ` Magnus Damm
2008-05-20 21:07 ` [PATCH 00/03][RFC] Reusable UIO Platform Driver Hans J. Koch
2008-05-20 21:07   ` Hans J. Koch
2008-05-21  3:31   ` Magnus Damm
2008-05-21  3:31     ` Magnus Damm
2008-05-21  6:49     ` Uwe Kleine-König
2008-05-21  6:49       ` Uwe Kleine-König
2008-05-21  7:49       ` Paul Mundt
2008-05-21  7:49         ` Paul Mundt
2008-05-21  8:05         ` Uwe Kleine-König
2008-05-21  8:05           ` Uwe Kleine-König
2008-05-21  8:22           ` Magnus Damm
2008-05-21  8:22             ` Magnus Damm
2008-05-21  8:50             ` Uwe Kleine-König [this message]
2008-05-21  8:50               ` Uwe Kleine-König
2008-05-21  8:09       ` Magnus Damm
2008-05-21  8:09         ` Magnus Damm
2008-05-21  9:25         ` Uwe Kleine-König
2008-05-21  9:25           ` Uwe Kleine-König
2008-05-21 10:50           ` Magnus Damm
2008-05-21 10:50             ` Magnus Damm
2008-05-21 11:04             ` Uwe Kleine-König
2008-05-21 11:04               ` Uwe Kleine-König
2008-05-21 11:56               ` Magnus Damm
2008-05-21 11:56                 ` Magnus Damm
2008-05-21 12:09                 ` Uwe Kleine-König
2008-05-21 12:09                   ` Uwe Kleine-König

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=20080521085033.GA29607@digi.com \
    --to=uwe.kleine-koenig@digi.com \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=matsu@igel.co.jp \
    /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.