From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Pb with dump driver.
Date: Fri, 15 Feb 2002 12:08:18 -0700 [thread overview]
Message-ID: <20020215190818.BB0464873@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com> of "Fri, 15 Feb 2002 13:55:49 +0100." <3C6D0555.BCDB04B6@admin.france.hp.com>
Bruno Vidal wrote:
> So I take the decision to modify now the code and create my own
> dump_iodc_write, dump_iodc_read, dump_iodc_wait, dump_iodc_open,
> dump_iodc_seek (I don't think I need other functions).
You should be able to leverage most of the code from palo.
Note that palo runs in th CPU in real-mode - not virtual mode.
You might consider doing the same for the dump code and just
be *very* careful about which functions you call.
Oh, and the dump path might want to do two other things:
1) PDC_IO_RESET_CLEAR
2) switch linux console back to PDC console
I don't know if some of those things are already happening.
If I have time, I'll look later.
palo is in CVS on the same server (cvs.parisc-linux.org) as our kernel.
(ie "cvs co palo" instead of linux)
> Thanks a lot to grant that point to the right direction,
> now let's go at work :-)
hehe..very welcome...I'm very happy to see you doing it...it's been
on my wish list for a long time.
thanks,
grant
next prev parent reply other threads:[~2002-02-15 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 17:34 [parisc-linux] Pb with dump driver Bruno Vidal
2002-02-13 17:43 ` Bruno Vidal
2002-02-15 6:43 ` Grant Grundler
2002-02-15 12:55 ` Bruno Vidal
2002-02-15 19:08 ` Grant Grundler [this message]
2002-02-15 21:01 ` Matthew Wilcox
2002-02-17 6:15 ` Grant Grundler
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=20020215190818.BB0464873@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=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 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.