From: Ryan Bradetich <rbradetich@uswest.net>
To: Christoph Plattner <christoph.plattner@gmx.at>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Re: MUX driver on E55
Date: 13 Sep 2002 18:13:19 -0600 [thread overview]
Message-ID: <1031962399.930.17.camel@beavis> (raw)
In-Reply-To: <3D825FDF.CD6E8CE2@gmx.at>
On Fri, 2002-09-13 at 15:59, Christoph Plattner wrote:
> Hallo Ryan !
>
> Congratulation, your MUX driver on port 0 is really
> working on my machine !!
Glad to hear that!
> What do you miss to support the other lines ?
I am not sure, I've never tried to hook up additional
lines. I do have an 8-port MDP somewhere, I'll look
for it here shortly, and see if I can hook it up.
> Have you already knowledge of the data structure ?
Just what I have added into the driver. If there is
something that we are obviously missing, I can go back
and reference the HP-UX mux driver and see what is
missing.
> Can I help you here in the code ?
Please! :) I do not use multiple lines currently ...
I only use the line 0, so any testing, optimizing, etc
is greatly appreciated!
> Another point: you mentioned the skeleton of the
> SCSI SPIFI driver. Where can I find that ? I only
> found a NetBSD code, which I will use as functional
> template, but I do not know, if this would be enough.
> Can you give me a hint in this point ?
I have it on my local system. It is _very_ ugly at this
point. I have got enough to query information from the
spifi chip, register an interrupt, etc... but currently
I can not get the spifi chip to actually generate an
interrupt.
I would be happy to send you a copy when I get back next
monday (unless you catch my in the next hour or so), but
I'm not ready to check it into CVS yeah until I get rid
of the some ugly hardcoded hacks, global variables, etc.
Right now the driver is really coded to gather info from
the ESIEE E35 that I have been testing on. Once again,
I do not have any docs on the chipset, I am using both
the NetBSD and HP-UX drivers as reference. :(
The driver should be easy to modify for your specific E55,
but not sure if you are interested in that level of work,
messyness now. I promise it will get much better :)
Thanks,
- Ryan
> Christoph
>
>
> --
> -------------------------------------------------------
> private: christoph.plattner@gmx.at
> company: christoph.plattner@alcatel.at
>
next prev parent reply other threads:[~2002-09-14 0:13 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 ` Ryan Bradetich [this message]
2002-09-14 0:25 ` [parisc-linux] " 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
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=1031962399.930.17.camel@beavis \
--to=rbradetich@uswest.net \
--cc=christoph.plattner@gmx.at \
--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