From: Ingo Hornberger <ihornberger@sysgo.de>
To: linuxppc-devel list <linuxppc-dev@ozlabs.org>
Subject: immap with 8xx.
Date: Tue, 29 Nov 2005 15:39:47 +0100 [thread overview]
Message-ID: <1133275187.2664.32.camel@iho.sysgo.com> (raw)
Hi,
I'm currently porting an old 2.4 kernel driver to 2.6.14. I got some
problems with the immap and idma stuff. The driver is very special and
uses it's own dma handling, because it's too different from the default.
So it strongly depends on the underlying hardware. (In this case 8xx)
With kernel 2.4 it used the headers:
- asm/commproc.h
- asm/8xx_immap.h
But it seems that there was some generalization work done, which didn't
reach the 8xx part. Particularly this means that some parts of
'asm/commproc.h' as well as (at least) 'asm/immap_8260.h' built up a new
header 'asm/immap_cpm2.h'.
Actally I miss a file like 'asm/immap_cpm1.h'.
If it would be the right solution to create a file like this, that's no
problem. I only wanted to make sure that I don't do duplicated work this
time.
regards,
Ingo
next reply other threads:[~2005-11-29 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 14:39 Ingo Hornberger [this message]
2005-11-29 18:13 ` immap with 8xx Dan Malek
2005-11-30 7:59 ` Ingo Hornberger
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=1133275187.2664.32.camel@iho.sysgo.com \
--to=ihornberger@sysgo.de \
--cc=ihornberger@sysgo.com \
--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).