From: Markus Brunner <super.firetwister@googlemail.com>
To: Ben Nizette <bn@niasdigital.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: UIO not working on ppc405 onchip registers
Date: Fri, 5 Sep 2008 08:18:58 +0200 [thread overview]
Message-ID: <200809050818.59425.super.firetwister@gmail.com> (raw)
In-Reply-To: <1216713170.4004.243.camel@moss.renham>
On Tuesday 22 July 2008, Ben Nizette wrote:
> But I'll let you get back to solving the UIO problem at hand :-D
I already surrendered and created (hacked) a read/write driver, which let me
use the old userspace drivers I'm trying to port (with some changes of
course). This was way faster than understanding all the involved APIs and
creating glue code between them. And the amount of time it needs was easy to
estimate.
However accidently I ran over the "old school" userland mmap code
with /dev/mem. I already knew mapping with /dev/mem is possible but I haven't
thought this could make a difference.
http://ozlabs.org/pipermail/linuxppc-embedded/2006-August/023811.html
Also I was wrong with my assumption that uio worked well on the peripherals.
It worked (very) well on the leds, just to fool me!!! But it returned crap on
some version registers.
With a working and a non working version of mmap it should be rather easy to
trace this bug. Unfortunately I was already short of time before running into
this (and other) problems and it didn't get any better.
So I would need some help from someone with more experience to fix this.
Any instructions?
Markus
next prev parent reply other threads:[~2008-09-05 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:52 UIO not working on ppc405 onchip registers Markus Brunner
2008-07-22 6:17 ` Uwe Kleine-König
2008-07-22 6:42 ` Ben Nizette
2008-07-22 7:48 ` super.firetwister
2008-07-22 7:52 ` Ben Nizette
2008-09-05 6:18 ` Markus Brunner [this message]
2008-07-22 7:47 ` super.firetwister
2008-07-22 16:20 ` super.firetwister
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=200809050818.59425.super.firetwister@gmail.com \
--to=super.firetwister@googlemail.com \
--cc=bn@niasdigital.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).