From: James Courtier-Dutton <James@superbug.co.uk>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: Lee Revell <rlrevell@joe-job.com>,
linux-sh <linuxsh-dev@lists.sourceforge.net>,
alsa-devel@alsa-project.org
Subject: Re: Dreamcast AICA driver
Date: Sun, 12 Mar 2006 12:02:56 +0000 [thread overview]
Message-ID: <44140DF0.1090908@superbug.co.uk> (raw)
In-Reply-To: <1142161181.9555.3.camel@localhost.localdomain>
Adrian McMenamin wrote:
> I know what these are - they can be turned into constants - they are
> either references to the ARM7 register bank or the ARM7 memory space.
>
>
>
>> It looks like many of these will be trivial to document:
>>
>> if (request_mem_region(0xa0702c00, 4, "AICA ARM control")== NULL) return -ENOMEM;
>> if (request_mem_region(0xa0800000, 0x200000, "AICA Sound RAM") == NULL)
>>
>> Lee
>>
>>
Adrian,
It was good to talk to you on IRC. Now, as you have the source code for
the ARM7 firmware as well as the SH4 driver code, it might be sensible
to highlight the dependencies between them, by maybe using the same
human readable constant name in both bits of code. It also makes things
easier to understand if the hex addresses are given as offsets from some
sort of base.
if (request_mem_region(0xa0702c00, 4, "AICA ARM control")== NULL) return -ENOMEM;
then becomes in a .h file:
#define ARM7_BASE_MEM 0xa0700000
#define ARM7_AICA_CONTROL 0x2c00
During driver init:
base_mem = ARM7_BASE_MEM
if (request_mem_region(base_mem + ARM7_AICA_CONTROL, 4, "AICA ARM control")== NULL) return -ENOMEM;
This would then allow movement of the base_mem without much modification to the driver code, if for example the ARM7 firmware required the change.
James
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-12 12:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1142124747.9496.50.camel@localhost.localdomain>
2006-03-12 1:11 ` Dreamcast AICA driver Lee Revell
2006-03-12 1:20 ` Adrian McMenamin
2006-03-12 6:14 ` Lee Revell
2006-03-12 6:28 ` Lee Revell
2006-03-12 10:59 ` Adrian McMenamin
[not found] ` <1142161181.9555.3.camel@localhost.localdomain>
2006-03-12 12:02 ` James Courtier-Dutton [this message]
2006-03-12 12:16 ` Adrian McMenamin
2006-03-12 11:00 ` Adrian McMenamin
2006-03-12 6:32 ` Lee Revell
2006-03-12 6:38 ` Lee Revell
2006-03-12 10:58 ` Adrian McMenamin
2006-03-12 20:35 ` Manuel Jander
2006-03-12 20:23 ` Adrian McMenamin
2006-03-13 11:48 ` Takashi Iwai
2006-03-12 0:52 Adrian McMenamin
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=44140DF0.1090908@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=linuxsh-dev@lists.sourceforge.net \
--cc=rlrevell@joe-job.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: 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.