From: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
To: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] IODC: I'm a bit fed up :-(
Date: Thu, 03 Oct 2002 17:10:35 +0200 [thread overview]
Message-ID: <3D9C5DEB.558EEAAD@admin.france.hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]
Hi
I'm loosing my nerves with iodc.....
I've found some interresting thing. For example, it is possible to obtain the HPA
of a modules directly by using a pdc call on PAT system. This one works fine:
struct device_path *dp
/* dp contain all needed informations */
memcpy(&mod,dp,sizeof(struct hardware_path));
pdc_status = mem_pdc_call( PDC_PAT_IO, PDC_PAT_IO_GET_PCI_CONFIG_FROM_HW, __pa(pdc_result), mod.num);
I've also succeded to retrive the ENTRY_INIT code. And I've double check that
this is truly an IODC code:
ret = mem_pdc_call(PDC_IODC, PDC_IODC_READ, __pa(pdc_result), hpa ,
PDC_IODC_INDEX_DATA, __pa(iodc_module_info), iodc_data_size);
and then
ret = mem_pdc_call (PDC_IODC, PDC_IODC_READ, __pa(pdc_result), hpa,
ENTRY_INIT, __pa(iodc_buffer_ptr), IODC_MAX, 0L, 0L, 0L, 0L, 0L);
-> I obtain the ENTRY_INIT iodc code in the ptr iodc_buffer_ptr.
this one has been reserved like this:
static unsigned long iodc_disk_buffer[IODC_MAX] __attribute__ ((aligned (8)));
Now I've really a problem. Each time I try to use this ENTRY_INIT code by using this call:
ret = real64_call(__pa(iodc_buffer_ptr),iodc_hpa, ENTRY_INIT_DEV,
iodc_spa, __pa(dump_iodc_layer),__pa(pdc_result));
(I've also tried with real32_call, but it is exactly the same pb.)
it fail with HPMC !!!! I've analysed the HPMC and it has a problem while doing:
LDO -64(r30),r29
LDO 20(r3),r2
LDB,O 0(r2),r17 -> HPMC
r29=ffffffffffffffff
r3=fffffffff8020000
r2=fffffffff8020014
(good news r3 is the base addr of my scsi card, sound good).
it is at offset iodc_buffer_ptr+0x1e3c
So it is inside the iodc code. It seems that it works on my
scsi card. But I don't have access to the firmware code. So if you have any idea,
clue, anything, help !!!! I really think, that if I solve this pb, the dump will
be shortly available.....
Thanks.
--
Vidal Bruno, (770-4271)
SSD-HA Team, HP-UX & LINUX Support
bruno_vidal@admin.france.hp.com
[-- Attachment #2: Card for Bruno Vidal --]
[-- Type: text/x-vcard, Size: 386 bytes --]
begin:vcard
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard
reply other threads:[~2002-10-03 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D9C5DEB.558EEAAD@admin.france.hp.com \
--to=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@lists.parisc-linux.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