From: Christoph Plattner <christoph.plattner@gmx.at>
To: Matthew Wilcox <willy@debian.org>
Cc: Ryan Bradetich <rbradetich@uswest.net>,
varenet@esiee.fr,
"MEYER,ALAN C. (HP-FtCollins,ex1)" <alan_meyer@hp.com>,
"parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: SCSI/MUX driver on E55, NDA for sorce code
Date: Mon, 16 Sep 2002 01:37:59 +0200 [thread overview]
Message-ID: <3D8519D7.55D90667@gmx.at> (raw)
In-Reply-To: 20020915192500.D10583@parcelfarce.linux.theplanet.co.uk
Thanks for that !
But I think, my Linux code dose the same !!!
info->iomem_base = (void *)(hpa + MUX_OFFSET +
(line * MUX_LINE_OFFSET));
This info->iomem_base is used by all accesses, the
registers of i/o are defined by Ryan as:
#define IO_COMMAND_REG_OFFSET 0x30
#define IO_STATUS_REG_OFFSET 0x34
#define IO_DATA_REG_OFFSET 0x3c
#define IO_DCOUNT_REG_OFFSET 0x40
#define IO_UCOUNT_REG_OFFSET 0x44
#define IO_FIFOS_REG_OFFSET 0x48
So the offset of 0x30 is inside those macros.
An example of an access:
data = __raw_readl((unsigned long)info->iomem_base
+ IO_DATA_REG_OFFSET);
... reading characters from the input buffers.
Any further idea ?
Ryan, you mentioned problems concerning missing locks, but
I cannot think about this. Those devices should be controlled
independent, am I wrong ?
I hope, we will solve this all (all means including SPIFI
SCSI driver too !).
Christoph
Matthew Wilcox wrote:
>
> On Sun, Sep 15, 2002 at 08:11:07PM +0200, Christoph Plattner wrote:
> > The status of MUX: It is not working to access to offset
> > 0x80 for the lines. The machine dies. I think this problem
> > can be solved very easy, looking in the HP-UX driver code.
>
> Not so sure...
>
> common/sio/mux2.c:
>
> for (loop = 0; loop < ports; loop++, ttyp++) {
> HW.hpa = MUX_DATA.hpa + 0x800 + (loop * 0x80);
> HW.io_reg_ptr = (io_reg_type *)(HW.hpa + 0x30);
> }
>
> --
> Revolutions do not require corporate support.
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
--
-------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
next prev parent reply other threads:[~2002-09-15 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 21:59 [parisc-linux] MUX driver on E55 Christoph Plattner
2002-09-14 0:13 ` [parisc-linux] " Ryan Bradetich
2002-09-14 0:25 ` Christoph Plattner
[not found] ` <1031964117.1043.29.camel@beavis>
2002-09-15 18:11 ` [parisc-linux] Re: SCSI/MUX driver on E55, NDA for sorce code Christoph Plattner
2002-09-15 18:25 ` Matthew Wilcox
2002-09-15 23:37 ` Christoph Plattner [this message]
2002-09-17 2:29 ` Ryan Bradetich
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=3D8519D7.55D90667@gmx.at \
--to=christoph.plattner@gmx.at \
--cc=alan_meyer@hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
--cc=varenet@esiee.fr \
--cc=willy@debian.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